stickler error under Windows Server 2008
Kintar opened this issue · 4 comments
When attempting to initialize a stickler repository on a machine running Windows Server 2008 R2 Standard and Ruby 1.9.2, the following error occurs:
C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra/base.rb:753:in `read': Invalid argument - <internal:lib/rubygems/custom_require> (Errno::EINVAL)
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra/base.rb:753:in `inline_templates='
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra/base.rb:706:in `set'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra/base.rb:715:in `block in enable'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra/base.rb:715:in `each'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra/base.rb:715:in `enable'
from (__DELEGATE__):2:in `enable'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/sinatra-1.0/lib/sinatra.rb:7:in `<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/stickler-2.0.2/lib/stickler/middleware/local.rb:1:in `<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/stickler-2.0.2/lib/stickler/middleware/gemcutter.rb:3:in `<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/stickler-2.0.2/lib/stickler/server.rb:3:in `<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/stickler-2.0.2/lib/stickler.rb:10:in `<top (required)>'
from <internal:lib/rubygems/custom_require>:29:in `require'
from <internal:lib/rubygems/custom_require>:29:in `require'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/stickler-2.0.2/bin/stickler:3:in `<top (required)>'
from C:/Ruby192/bin/stickler:19:in `load'
from C:/Ruby192/bin/stickler:19:in `<main>'
Reproduce with:
gem install stickler
cd c:\
mkdir stickler
Then:
stickler
or
stickler help
Or any other stickler command, actually. :)
[EDIT: Realized everything was bombing, not just repository setup.]
Thanks, I'll take a look and see if I can figure out what is going on.
Apologies for not responding to this issue in a timely manner. Do you still see this behavior? I released a new version of stickler this week, if you can please test and see if the above still happens with you I would appreciate it.
Hello, a bit more of information on this, that might help. Sinatra 1.0 was not compatible with Ruby 1.9.2 and had issues parsing paths of internal RubyGems.
If Stickler uses older versions of Sinatra, this should not be a problem anymore.
The latest stickler requires Sinatra 1.2.1 at a minimum, so I think its probably good now. So if Sinatra 1.2.1 is good with ruby 1.9.2 then stickler should be good with 1.9.2.
I'll close this issue then. Let me know if you have any other problems.