Bug 721844

Summary:	Add checks for PYTHON_COMPAT status and stability
Product:	Portage Development	Reporter:	Sam James <sam>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED OBSOLETE
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=721752
Whiteboard:
Package list:		Runtime testing required:	---

Description Sam James archtester

2020-05-09 11:07:58 UTC

In bug 721752, we're tracking ebuilds requiring Python which do not have Python >= 3.7 in their stable version, but support >= 3.7 in a newer unstable version.

This is problematic when the make.defaults change to e.g. PYTHON_TARGETS="python3_7" and e.g. layman (bug 720934) stops the upgrade with a cryptic error.

I see this as equivalent to a stable ebuild depending on something unstable, but maybe others' views will differ. In any case, this situation causes confusion for users and some QA flag to notify when make.defaults conflicts with ebuilds would be useful.

I propose: flag when PYTHON_TARGETS (and similar variables?) in make.defaults "breaks" ability to install ebuilds because of their (lack of) stable keywords.

Comment 1 Sam James archtester

2020-07-31 23:00:21 UTC


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

Comment 2 Sam James archtester

2020-07-31 23:01:04 UTC

(In reply to Sam James from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 540334 ***

nevermind!

Comment 3 Sam James archtester

2022-10-20 01:53:54 UTC

We have RequiredUseDefaults in pkgcheck.