Bug 574140

Summary:	sys-apps/portage: Fails hard if /usr/bin/python becomes broken
Product:	Portage Development	Reporter:	Michał Górny <mgorny>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	critical
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Michał Górny archtester

2016-02-07 22:58:11 UTC

I'm pretty sure some of the magical logic in Portage was supposed to make sure it calls the currently used interpreter directly rather than relying on /usr/bin/python working. However, I just got an issue where broken /usr/bin/python has caused internal portage helpers to fail hard and brick Portage for me. I'm going to investigate more.

Comment 1 Michał Górny archtester

2016-02-07 23:02:47 UTC

Oh, nevermind. Just noticed it was due to python executable rename from python3.4m to python3.4.