I see this is tagged wontfix. Isn't this actually fixed by libgems-ruby/1.3.2-1 which includes a rubygems package without any maintainer scripts to do the purging? (So upgrading from old rubygems to rubygems 1.3.2-1 will change the destructive postrm to a no-op postrm, which will transfer ownership of the gems to rubygems1.8? (So any future package renames that create a transition package should also have the same semantics for change of ownership.)
-- Chanoch (Ken) Bloom. PhD candidate. Linguistic Cognition Laboratory. Department of Computer Science. Illinois Institute of Technology. http://www.iit.edu/~kbloom1/
signature.asc
Description: Digital signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
