matt neuburg wrote:
7stud – email@example.com wrote:
But what I don’t get is: I’ve got gem 1.3.1 and I never had this problem
Updating version of RubyGems to 1.3.1
ERROR: While executing gem … (Errno::ENOENT)
No such file or directory -
What version of ruby do you have installed?
$ ruby -v
ruby 1.8.2 (2004-12-25) [universal-darwin8.0]
I’m no big expert, but at least we have similar systems so a comparison
might be useful in tracking this stuff down. I am using,
ruby 1.8.6 (2008-03-03 patchlevel 114) [powerpc-darwin8.9.0]
My working ruby is in /usr/local.
What install directions did you use to install 1.8.6?
I’ve left the built-in ruby in place, so I also have /usr/bin/ruby:
ruby 1.8.2 (2004-12-25) [powerpc-darwin8.0]
But I don’t use it.
But I don’t think that’s the issue. When you get an error message
warning that there is no directory rubygems-update-1.3.1, I tend to
think that this is because you are supposed to have such a directory.
Your quoted material says “Successfully installed
rubygems-update-1.0.0”; but the current version is 1.3.1. So that must
be what rubygems is looking for. I do have such a directory:
I think you need that before you can proceed. Of course mine is in a
different place because my ruby is in a different place.
Is that a directory or a file? I looked around on ruby-forge and saw
and since that matched the file the error message said was missing, I
thought I’d download it and try putting it in the directory indicated in
the error message. When I downloaded that file, it arrived as
rubygems-update-1.3.1.gem.tar and when I tried to untar it:
$ tar -xvf rubygems-update-1.3.1.gem.tar
I got this output:
tar: data.tar.gz: implausibly old time stamp 1969-12-31 17:00:00
tar: metadata.gz: implausibly old time stamp 1969-12-31 17:00:00
tar: data.tar.gz.sig: implausibly old time stamp 1969-12-31 17:00:00
tar: metadata.gz.sig: implausibly old time stamp 1969-12-31 17:00:00
which I thought was an error message, but now I realize that untaring
produced these two files:
So you could probably get things working by following this procedure
(but use sudo):
$ gem install rubygems-update
Shouldn’t the first command be:
$ gem install -r rubygems-update
-r for remote
And what does the second command do?
However, you don’t really need to do that, because, as the Google-found
ruby-forge page I cited says, there was a bug, it has been fixed, and
you can check out working code from the trunk. So your setup.rb approach
should also now work.
Do I re-download rubygems-1.3.1?