On 11/29/2010 08:43 AM, Sebastian Pipping wrote: > On 11/29/10 17:31, Ulrich Mueller wrote: >> I guess it is triggered from pkg_postrm() of python-2.6.6-r1 which >> until two days ago unconditionally called the following eselect >> action: >> >> eselect python update --python2 >> >> So unless you had updated your python-2.6 during the last two days, >> the installed version in your VDB would still contain the above line. > > So a working fix would be to ripp out the "update" action? > Do we still need that?
You could also cancel it out, by checking the state in pkg_preinst and saving it in an environment variable so that you can restore it in pkg_postinst. -- Thanks, Zac
