On Mon, Nov 29, 2010 at 07:36:45PM +0100, Ulrich Mueller wrote:
> >>>>> On Mon, 29 Nov 2010, Graham Murray 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:
>
> > But python-2.7 is installed in a new slot and python-2.6.x is not
> > removed. So. surely python-2.6.6-r1's pkg_postrm() should not be
> > called during the installation of python-2.7.1.
>
> You are right, this cannot be the reason then.
>
> But could pkg_postrm() of python-3.1.2-r4 have caused the update?
> It essentially executed the following code:
>
> [[ "$(eselect python show)" == "python2."* ]] &&
> eselect_python_options="--python2"
> eselect python update --python3 > /dev/null
> eselect python update ${eselect_python_options}
>
> Ebuilds for 2.7.1 and 3.1.3 were committed together, and 3.1.2-r4 and
> 3.1.3 are in the same slot.
That's it. I ran those commands manually and the third one,
which evaluates to
eselect python update --python2
switched my python to 2.7.
On Mon, Nov 29, 2010 at 05:31:29PM +0100, Ulrich Mueller wrote:
> >>>>> On Mon, 29 Nov 2010, Alex Alexander wrote:
> >
> > They were working fine with 2.6 before the update.
>
> If it ain't broke, don't fix it? ;-)
I lol'd hard with this, thanks! :p
So, no updates at all? :D
--
Alex Alexander | wired
+ Gentoo Linux Developer
++ www.linuxized.com
pgpittushruqq.pgp
Description: PGP signature
