Updates from the merb source were choking with an error that it wasn't
at 1.2+, but I just removed the source, since I'm not doing much w/
merb right now.
If I look at that url with firefox, I get a text page with links to get a
yaml index, look at the gems online, and download ruby gems. If I click on
the second one, I seem to get randomly redirected to different shadow
servers most of which result in a forbidden error. A sampling:
RubyGems itself never accesses these URLs. Forbidden here is ok.
Here's what happens when I try a system update:
Macintosh:activerecord rick$ sudo gem update --system
Password:
Updating RubyGems
Bulk updating Gem source index for: http://gems.rubyforge.org/
Updating rubygems-update
ERROR: While executing gem ... (Gem::GemNotFoundException)
could not find rubygems-update locally or in a repository
Can you try again today? There was an incompatibility in trunk before RubyGems 1.2 was released, so gems released were incompatible and broke the index. They've all been cleaned up now, re-released with RubyGems 1.2.
There is one other bug with upgrading from RubyGems 1.1.1. If an older rubygems-update is not installed RubyGems may report "nothing to update". As a work-around, run `gem install rubygems-update -v 1.1.1` before `gem update --system`.
···
On Jun 23, 2008, at 13:33 PM, Rick DeNatale wrote:
If you run sudo rubygems_update now, does it install 1.2.0?
···
On Jun 25, 2008, at 21:54 PM, Une Bévue wrote:
Eric Hodel <drbrain@segment7.net> wrote:
As I responded to Rick's message, this should now be fixed. If you
get the "nothing to update" response, the workaround is to `gem
install rubygems-update -v 1.1.1` before updating RubyGems.
unfortunately, nope ))
~%> sudo gem update --system
Password:
Updating RubyGems
Updating metadata for 34 gems from http://gems.rubyforge.org/
..................................
complete
Nothing to update^
^^^^^^^^^^^^^^^^^
~%> sudo gem install rubygems-update -v 1.1.1
ERROR: could not find rubygems-update locally or in a repository
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
also, because the environment may not be the same installing something you *know* apriori has deps (LD_LIBRARY_PATH et al) compared to having gems automatically install a dep which is already there. for example i have two mysql installs - i need to be sure a gem install compiles against a particular one in some cases. if gems auto installs deps including previously installed ones it can easily surprise me be recompiling against the wrong installation (including all deps) if i'm unprepared.
RubyGems does not reinstall dependencies that already exist, so you don't need to worry about this part.
···
On Jun 23, 2008, at 10:52 AM, ara.t.howard wrote:
if gems auto installs deps including previously installed ones it can easily surprise me be recompiling against the wrong installation (including all deps) if i'm unprepared.
You have to manually remove the old gem and everything associated with it. I
tried removing gem via apt, but it didn't work. The only way I fixed it was
the old fashioned way.
···
On Tue, Jun 24, 2008 at 2:25 PM, Roger Pack <rogerpack2005@gmail.com> wrote:
It appears I am destined for poor luck with this upgrade.
Tried it in a fresh ubuntu install
sudo apt-get install ruby rubygems
# worked
sudo gem update --system
# said it worked
Now I get the infamous
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
I've kicked off a couple of groups on Launchpad to deal with the
problem of Ruby backports and Ruby packaging in general on Ubuntu.
The package archives of those groups contain a backport of 1.1.1
rubygems and Phusion passenger.
If you can help with testing the packages, or better still help us
write stuff then we can get to the nirvana where 'apt' and 'gem' play
nicely together that much sooner.
Neil Wilson
Brightbox
···
On Jun 24, 8:25 pm, Roger Pack <rogerpack2...@gmail.com> wrote:
It appears I am destined for poor luck with this upgrade.
Tried it in a fresh ubuntu install
sudo apt-get install ruby rubygems
# worked
sudo gem update --system
# said it worked
Now I get the infamous
/usr/bin/gem:23: uninitialized constant Gem::GemRunner (NameError)
Sorry, i'm lost, not at this time :
~/gems%> sudo update_rubygems
Installing RubyGems 1.2.0
setup.rb:108: undefined method `ruby_version' for Gem:Module
(NoMethodError)
~/gems%> gem env
For some reason I had a previous version of gem that was installed in
the wrong directory--like it should have been installed in
/user/rdp/home/i386/bin but instead it was in
/user/rdp/home/i386/bin/rdp/home/i386/bin or something.
Anyway, upgrading from this state,
download rubygems-1.2.0.tgz
ran ruby setup.rb on it.
now I get something similar:
/home/rdp/i386/bin/gem:14: undefined method `ruby_version' for
Gem:Module (NoMethodError)
This means that [in this one system] even installing it from scratch
again doesn't fix the problem. Not sure what to do.
Even deleting *gem*.rb from my ruby lib directory yields
/home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:29:
warning: already initialized constant OPS
/home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems/requirement.rb:32:
warning: already initialized constant OP_RE
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/specification.rb:24:
Platform is not a module (TypeError)
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb:15:in
`require'
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/package.rb:15
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb:7:in
`require'
from
/home/rdp/i386/usr/lib/ruby/site_ruby/1.8/rubygems/builder.rb:7
from /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems.rb:769:in
`require'
from /home/rdp/i386/lib/ruby/site_ruby/1.8/rubygems.rb:769
from /home/rdp/i386/bin/gem:8:in `require'
from /home/rdp/i386/bin/gem:8
Hmm. Thankfully it's on a system where I don't really NEED gems, but
they are convenient.
Thanks!
-R
that is, there is a clean way to uninstall rubygems and re-install it
afterwards ?
In my case I download rubygems.xxx.gz, unzipped it, ran sudo ruby
setup.rb [which installed gem1.8, for some reason, instead of gem], then
I renamed gem to replace my existing gem and it was good to go. That's
what I meant
Not very clean, no. I suppose I could have done an apt-get uninstall
rubygems first, but at least it seems to work this way.
-R
