gem cleanup screw up...

[Michael Guterl]

I was running `gem cleanup` today, which was long overdue when I
accidentally hit CTRL-C in the wrong window. It killed the cleanup
process and trying to run the command again results in errors about
each gem that had been cleaned up during the previous run.

Anyone know how to fix this before I attempt some hacks myself?

Thanks,
Michael Guterl

 

[Daniel Berger]

I was running `gem cleanup` today, which was long overdue when I
accidentally hit CTRL-C in the wrong window. =A0It killed the cleanup
process and trying to run the command again results in errors about
each gem that had been cleaned up during the previous run.

Anyone know how to fix this before I attempt some hacks myself?

Can you post the errors? And the output of 'gem env'?

Regards,

Dan

 

[Michael Guterl]

Can you post the errors? And the output of 'gem env'?

Absolutely, should have done this from the beginning...

michaelguterl@macbook ~$ sudo gem cleanup
Password:
Cleaning up installed gems...
Attempting to uninstall highline-1.2.9
ERROR: While executing gem ... (Gem::InstallError)
Unknown gem highline = 1.2.9

michaelguterl@macbook ~$ sudo gem install highline --version '= 1.2.9'
Successfully installed highline-1.2.9
1 gem installed
Installing ri documentation for highline-1.2.9...
Installing RDoc documentation for highline-1.2.9...

michaelguterl@macbook ~$ sudo gem cleanup
Cleaning up installed gems...
Attempting to uninstall highline-1.2.9
Successfully uninstalled highline-1.2.9
Attempting to uninstall net-ssh-1.1.2
ERROR: While executing gem ... (Gem::InstallError)
Unknown gem net-ssh = 1.1.2

These gems were removed during the original cleanup run and it goes on
and on for each gem that was removed during the initial cleanup. Also
the .gem files still reside in /Library/Ruby/Gems/1.8/cache for the
gems that were removed during the initial `gem cleanup` which I
accidentally canceled. I assume this is why they are attempting to
still be cleaned up, I just did not know if there was an easy
workaround.

Could this be a bug? I would think these .gem files should be removed
after uninstalling...

michaelguterl@macbook ~$ sudo gem env
RubyGems Environment:
- RUBYGEMS VERSION: 1.3.1
- RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
- INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
- RUBY EXECUTABLE:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
- EXECUTABLE DIRECTORY: /usr/bin
- RUBYGEMS PLATFORMS:
- ruby
- universal-darwin-9
- GEM PATHS:
- /Library/Ruby/Gems/1.8
- /Users/michaelguterl/.gem/ruby/1.8
- /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :benchmark => false
- :backtrace => false
- :bulk_threshold => 1000
- :sources => ["http://gems.rubyforge.org/", "http://gems.github.com/"]
- REMOTE SOURCES:
- http://gems.rubyforge.org/
- http://gems.github.com/

Regards,
Michael Guterl

 

[Michael Guterl]

Absolutely, should have done this from the beginning...

michaelguterl@macbook ~$ sudo gem cleanup
Password:
Cleaning up installed gems...
Attempting to uninstall highline-1.2.9
ERROR: While executing gem ... (Gem::InstallError)
Unknown gem highline = 1.2.9

michaelguterl@macbook ~$ sudo gem install highline --version '= 1.2.9'
Successfully installed highline-1.2.9
1 gem installed
Installing ri documentation for highline-1.2.9...
Installing RDoc documentation for highline-1.2.9...

michaelguterl@macbook ~$ sudo gem cleanup
Cleaning up installed gems...
Attempting to uninstall highline-1.2.9
Successfully uninstalled highline-1.2.9
Attempting to uninstall net-ssh-1.1.2
ERROR: While executing gem ... (Gem::InstallError)
Unknown gem net-ssh = 1.1.2

These gems were removed during the original cleanup run and it goes on
and on for each gem that was removed during the initial cleanup. Also
the .gem files still reside in /Library/Ruby/Gems/1.8/cache for the
gems that were removed during the initial `gem cleanup` which I
accidentally canceled. I assume this is why they are attempting to
still be cleaned up, I just did not know if there was an easy
workaround.

I need to retract my statement about the .gem files still existing in
the /Library/Ruby/Gems/1.8/cache directory. That does not appear to
be the case. I must have been hallucinating earlier..

 

[Daniel Berger]

Absolutely, should have done this from the beginning...

michaelguterl@macbook ~$ sudo gem cleanup
Password:
Cleaning up installed gems...
Attempting to uninstall highline-1.2.9
ERROR: =A0While executing gem ... (Gem::InstallError)
=A0 =A0 Unknown gem highline =3D 1.2.9

michaelguterl@macbook ~$ sudo gem install highline --version '=3D 1.2.9'
Successfully installed highline-1.2.9
1 gem installed
Installing ri documentation for highline-1.2.9...
Installing RDoc documentation for highline-1.2.9...

michaelguterl@macbook ~$ sudo gem cleanup
Cleaning up installed gems...
Attempting to uninstall highline-1.2.9
Successfully uninstalled highline-1.2.9
Attempting to uninstall net-ssh-1.1.2
ERROR: =A0While executing gem ... (Gem::InstallError)
=A0 =A0 Unknown gem net-ssh =3D 1.1.2

These gems were removed during the original cleanup run and it goes on
and on for each gem that was removed during the initial cleanup. =A0Also
the .gem files still reside in /Library/Ruby/Gems/1.8/cache for the
gems that were removed during the initial `gem cleanup` which I
accidentally canceled. =A0I assume this is why they are attempting to
still be cleaned up, I just did not know if there was an easy
workaround.

Ah, so they're still listed in the cache directory, but don't actually
exist under the gems directory.

Sounds like a bug to me.

I'll file a bug report on the RF tracker (and reference this post).

Regards,

Dan

 

[Michael Guterl]

Ah, so they're still listed in the cache directory, but don't actually
exist under the gems directory.

Sounds like a bug to me.

I'll file a bug report on the RF tracker (and reference this post).

I wish that were the case, see my follow-up post:

I need to retract my statement about the .gem files still existing in
the /Library/Ruby/Gems/1.8/cache directory. That does not appear to
be the case. I must have been hallucinating earlier..

Did it not make it to the list?

 

[Daniel Berger]

I wish that were the case, see my follow-up post:

I need to retract my statement about the .gem files still existing in
the =A0/Library/Ruby/Gems/1.8/cache directory. =A0That does not appear to
be the case. =A0I must have been hallucinating earlier..

Did it not make it to the list?

Oh, I misunderstood. Hm, well, I've already filed a bug report, but
that's ok. It's still _some_ kind of bug. We'll see if we can track it
down.

Regards,

Dan

 

[Jeremy Hinegardner]

I was running `gem cleanup` today, which was long overdue when I
accidentally hit CTRL-C in the wrong window. It killed the cleanup
process and trying to run the command again results in errors about
each gem that had been cleaned up during the previous run.

Anyone know how to fix this before I attempt some hacks myself?

Just an idea, and I have no idea if this will work or not:

sudo gem pristine --all
sudo gem cleanup

enjoy,

-jeremy

 

[Michael Guterl]

Just an idea, and I have no idea if this will work or not:

sudo gem pristine --all
sudo gem cleanup

enjoy,

-jeremy

For what it's worth this does not work. Thanks though.

Michael Guterl

 

[Michael Guterl]

Oh, I misunderstood. Hm, well, I've already filed a bug report, but
that's ok. It's still _some_ kind of bug. We'll see if we can track it
down.

I just checked the bug tracker. I believe this bug is related to
http://rubyforge.org/tracker/index.php?func=detail&aid=22770&group_id=126&atid=575