Bug 916498

Summary:	update of python-exec yields to system "breakage"
Product:	Gentoo Linux	Reporter:	Enrique Domínguez <enrique_pinos>
Component:	Eclasses	Assignee:	Python Gentoo Team <python>
Status:	UNCONFIRMED ---
Severity:	major	CC:	gentoo, k4be+gentoo, sam
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=918659
Whiteboard:
Package list:		Runtime testing required:	---

Description Enrique Domínguez 2023-10-29 19:00:28 UTC

When updating my system from python3_9 to python3_10 portage firstly updated python-exec pkg and then other pkgs begin to fail with missing python dependencies (system update fails). Solved problem editing /usr/portage/eclass/python-utils-r1.eclass (2nd order inherited from python-exec) and added my old python3_9 version to _PYTHON_ALL_IMPLS array and reemerged python-exec.
Maybe _PYTHON_ALL_IMPLS could take its value from PYTHON_COMPAT array from python-exec ebuild, no idea if this could break other things.
Information could be a little inexact because i'm reporting without system at hand.

Reproducible: Always




Possibly related BUG reports: #770421, #830273

Comment 1 Sam James archtester

2023-10-29 19:40:46 UTC

I've been thinking about this for a while.

Obviously, the case you hit "shouldn't" happen because it either implies a Portage bug (misordering for the merge list) or bad luck/fragility (because some package in the list failed between python-exec being re-emerged and Portage being re-emerged with new Python). But that's little comfort and not very helpful practically.

Maybe we could use the list of historical implementations and have python-exec fall back to that (possibly with some warning on stderr?) if it must.

Comment 2 Enrique Domínguez 2023-11-18 02:37:40 UTC

(In reply to Sam James from comment #1)
> I've been thinking about this for a while.
> 
> Obviously, the case you hit "shouldn't" happen because it either implies a
> Portage bug (misordering for the merge list) or bad luck/fragility (because
> some package in the list failed between python-exec being re-emerged and
> Portage being re-emerged with new Python). But that's little comfort and not
> very helpful practically.
> 
> Maybe we could use the list of historical implementations and have
> python-exec fall back to that (possibly with some warning on stderr?) if it
> must.

Thanks for your reply. Not so frequently updated systems finds trouble each time (same with archlinux)

Comment 3 Sam James archtester

2023-12-09 23:17:23 UTC

*** Bug 919384 has been marked as a duplicate of this bug. ***