On Jan 1, 6:52   
> On Thu, Jan 1, 2009 at 8:40 PM, Daniel Berger <djber... / gmail.com> wrote:
>
> > On Jan 1, 2:52 pm, "Michael Guterl" <mgut... / gmail.com> wrote:
> >> I was running `gem cleanup` today, which was long overdue when I
> >> accidentally hit CTRL-C in the wrong window.   > >> 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:  > 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:  > 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.  > 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.        
> 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