On 15/08/10 at 15:11 +0200, Tobi wrote: > Hi! > > There seems to be an issue with the latest ruby1.9.1 causing a bunch auf > auto-bugs by Lucas' latest rebuild: > > While this works: > > $ touch /tmp/test.rb ; ruby1.9.1 -e "require '/tmp/test'" > > This doesn't: > > $ touch test.rb ; ruby1.9.1 -e "require 'test'"
Yes, that's a new "feature" in 1.9.2. Relative requires no longer work. > <internal:lib/rubygems/custom_require>:29:in `require': no such file to > load -- rubygems (LoadError) > from <internal:lib/rubygems/custom_require>:29:in `require' > from <internal:gem_prelude>:167:in `load_full_rubygems_library' > from <internal:gem_prelude>:217:in `try_activate' > from <internal:lib/rubygems/custom_require>:32:in `rescue in require' > from <internal:lib/rubygems/custom_require>:29:in `require' > from -e:1:in `<main>' That is caused by the "magic" in ruby 1.9.* which tries to fallback to using rubygems if a normal require fails. I'm not sure yet where we should go about that. Another known problem is that the fact that the rubygems version that we have in squeeze (which is the latest upstream version of rubygems) doesn't work with ruby 1.9.2. Again, I'm not sure yet of the solution we should use for that. We could package rubygems1.9.1 from the ruby 1.9.2 source instead of from the rubygems standalone source, but it sounds a bit dirty to have so much duplication of efforts. L. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
