Bug 347541

Summary:	python-updater can't start due to /usr/bin/python3 is not valid symlink
Product:	Gentoo Linux	Reporter:	Lars Langhans <lars.langhans>
Component:	[OLD] Core system	Assignee:	Python Gentoo Team <python>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Lars Langhans 2010-12-02 10:41:02 UTC

I try to update my machine, from a more than a year old gentoo system to a current system.

Lot of packages can't build because python3 has replaced by python3.1.

Also I can not start python-updater any more. Result is
'/usr/bin/python3' is not valid symlink

What a pitty!
# eselect python list
[1] python2.6 *
[2] python3.1

Why python-updater will take python3?
I've emerged python-updater also, but the same result.

Is there a simple way to force python-updater to use the right?

My way was to create a new /usr/bin/python3 symlink to python3.1 but I think this could be done automatically by python-updater.



Reproducible: Always

Comment 1 Matteo Contri 2010-12-03 08:27:35 UTC

> Also I can not start python-updater any more. Result is
> '/usr/bin/python3' is not valid symlink

I'm building a stage1+2+3 64bit gentoo system and this problem occurs also in:

dev-libs/libxml2
sys-apps/file

i also did the same workaround, but i think this should be fixed somewhere in eselect python or python3.1 installation. (probably because both of us never installed python3.0 but only python3.1)

Comment 2 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2011-01-01 18:35:06 UTC


*** This bug has been marked as a duplicate of bug 347639 ***