>>>>> On Mon, 29 Nov 2010, Markos Chandras wrote: >> > Revbump otherwise get ready for a series of bug reports from frustrated >> > users >> >> I don't think this case qualifies for a revbump. >> [...]
> The behavior of the package has changed though. Do not expect anyone > who uses ~testing to know about eselect python module. If you are > lucky enough, you will received just a few bug reports about this > from those users who updated their packages before you "fix" the > ebuilds. Also a revbump doesn't help if the bad code is in the old version's pkg_postrm(), which is installed on users' systems. Ulrich
