From: Daniel Berger Date: 2009-01-02T13:23:34+09:00 Subject: Re: gem cleanup screw up... On Jan 1, 9:09 pm, "Michael Guterl" wrote: > On Thu, Jan 1, 2009 at 11:00 PM, Daniel Berger wrote: > > > On Jan 1, 6:52 pm, "Michael Guterl" wrote: > >> On Thu, Jan 1, 2009 at 8:40 PM, Daniel Berger wrote: > > >> > On Jan 1, 2:52 pm, "Michael Guterl" wrote: > >> >> 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? > > >> > 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. > > > 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? 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