Hi Eloy,
On 01/07/2007, at 00:59, Eloy Duran wrote:
Also, is it just me or is rubygems in macports broken?
$ gem
/opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no such file to load -- sources (LoadError)
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
custom_require.rb:27:in
`require'
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
source_info_cache.rb:6
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
custom_require.rb:27:in
`gem_original_require'
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
custom_require.rb:27:in
`require'
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
remote_installer.rb:12
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
custom_require.rb:27:in
`gem_original_require'
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/
custom_require.rb:27:in
`require'
from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems.rb:112:in
`manage_gems'
from /opt/local/bin/gem:10
This is a known problem that is proving rather difficult to track
down. I sent an email to the macports-users list a couple of days
ago, though, to ask people to test a possible workaround, and I was
wondering if you could do the same: try force-upgrading rb-rubygems
using "port -ufn upgrade rb-rubygems" and see if it works then. I
didn't have the problem until I recently did a clean install, but
then it went away after I upgraded from 0.9.2 to 0.9.4, so I want to
see if a forced upgrade to the same version has the same effect.
Kind regards,
Maun Suang
--
Boey Maun Suang (Boey is my surname)
Email: boeyms at macports dot org
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
