574140 – sys-apps/portage: Fails hard if /usr/bin/python becomes broken

Bug 574140 - sys-apps/portage: Fails hard if /usr/bin/python becomes broken

Summary: sys-apps/portage: Fails hard if /usr/bin/python becomes broken

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All Linux

Importance:	Normal critical
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-02-07 22:58 UTC by Michał Górny
Modified:	2016-02-07 23:02 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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.