835146 – emerge fails after pypy3 subslot update if pypy3 is a system interpreter

Bug 835146 - emerge fails after pypy3 subslot update if pypy3 is a system interpreter

Summary: emerge fails after pypy3 subslot update if pypy3 is a system interpreter

Status:	UNCONFIRMED

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2022-03-14 15:32 UTC by Anna Vyalkova
Modified:	2022-03-14 15:39 UTC (History)
CC List:	0 users

See Also:	782889 770421
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 Anna Vyalkova 2022-03-14 15:32:30 UTC

postrm/postinst phases fail with this error:

ModuleNotFoundError: No module named 'encodings'
debug: OperationError:
debug:  operror-type: ModuleNotFoundError
debug:  operror-value: No module named 'encodings'


Reproducible: Always

Steps to Reproduce:
1. Set pypy3 as system interpreter
2. Upgrade dev-python/pypy3 from 0/pypy38-pp73 to 0/pypy39-pp73

Comment 1 Sam James archtester

2022-03-14 15:34:03 UTC

I think this is quite well known but not sure we can do much about it.

mgorny referenced it in his pypy post to the gentoo-dev ML a while ago: https://marc.info/?l=gentoo-dev&m=161469756208830&w=2.