Bugs item #28286, was opened at 2010-06-09 13:11
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28286&group_id=126
Category: None
Group: None
>Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Sakuro OZAWA (sakuro)
Assigned to: Ryan Davis (zenspider)
Summary: Removal of wrappers should occur *after* successful uninstallation
Initial Comment:
When one terminates uninstallation of a gem, he/she would expect wrapper
scripts remain.
$ ruby --version
ruby 1.9.3dev (2010-06-08 trunk 28202) [i386-darwin9.8.0]
$ gem --version
1.3.7
$ gem uninstall nokogiri
Remove executables:
nokogiri
in addition to the gem? [Yn] y
Removing nokogiri
You have requested to uninstall the gem:
nokogiri-1.4.2
cucumber-0.8.0 depends on [nokogiri (>= 1.4.2)]
mime-types-1.16 depends on [nokogiri (~> 1.2)]
webrat-0.7.1 depends on [nokogiri (>= 1.2.0)]
If you remove this gems, one or more dependencies will not be met.
Continue with Uninstall? [Yn] n
ERROR: While executing gem ... (Gem::DependencyRemovalException)
Uninstallation aborted due to dependent gem(s)
$ which nokogiri
nokogiri not found
----------------------------------------------------------------------
>Comment By: Sakuro OZAWA (sakuro)
Date: 2011-06-08 19:25
Message:
Appears to be resolved in github issue #35. (
https://github.com/rubygems/rubygems/pull/35 )
----------------------------------------------------------------------
Comment By: Ryan Davis (zenspider)
Date: 2011-06-08 08:50
Message:
Hi!
Believe it or not, we're moving to github's issue tracker! The
pressure to move has been loud and clear, but for the longest time
it didn't support the way we worked. Now that it has freeform
labels it can support our workflow adequately. There is just one
problem: Your bug is here and we don't want to lose you!
What we'd like you to do is fairly painless and should only take a
few minutes:
Please file the _exact_ same ticket on github and provide a link
back to this crufty old ticket so we can refer to any previous
discussion that occurred. Once the new ticket is made, put a
forwarding link to it here and close this ticket out. In a couple
weeks, we'll track down the old tickets that are still open and
decide what to do with them.
We could have done this fairly automatically, but we really want
you to do it so you're attached to the ticket and we can still
communicate with you and keep a record of it.
https://github.com/rubygems/rubygems/issues
Thanks,
The RubyGems Team
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=575&aid=28286&group_id=126
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
