The package should, as announced by mgorny, support being built with python3.12. The switch to 3.12 is scheduled to happen on 2024-06-01.
+1 Unable to update due to the following: -----------------SNIP------------------------------------ !!! Problem resolving dependencies for sys-apps/policycoreutils from @system ... done! Dependency resolution took 1.10 s (backtrack: 0/20). !!! The ebuild selected to satisfy "sys-apps/policycoreutils" has unmet requirements. - sys-apps/policycoreutils-3.6::gentoo USE="(audit) pam (split-usr)" ABI_X86="(64)" PYTHON_TARGETS="-python3_10 -python3_11" The following REQUIRED_USE flag constraints are unsatisfied: any-of ( python_targets_python3_10 python_targets_python3_11 ) (dependency required by "@system" [set]) (dependency required by "@world" [argument]) -----------------SNIP------------------------------------ I already followed the recommended way from the news: -------------------------SNIP----------------------------------------- Safer upgrade procedure ======================= A safer approach is to add Python 3.12 support to your system first, and only then remove Python 3.11. However, note that this involves two rebuilds of all the affected packages, so it will take noticeably longer. First, enable both Python 3.11 and Python 3.12, and then run the upgrade commands: */* PYTHON_TARGETS: -* python3_11 python3_12 */* PYTHON_SINGLE_TARGET: -* python3_11 Then switch PYTHON_SINGLE_TARGET and run the second batch of upgrades: */* PYTHON_TARGETS: -* python3_11 python3_12 */* PYTHON_SINGLE_TARGET: -* python3_12 Finally, switch to the final version and upgrade: */* PYTHON_TARGETS: -* python3_12 */* PYTHON_SINGLE_TARGET: -* python3_12 You may wish to remove the target overrides after the defaults switch. Alternatively, you can keep them to block the next automatic upgrade to Python 3.13, and upgrade manually then. Upgrade commands ================ The Python 3.11 cleanup requires that Python 3.11 is removed from the complete dependency trees in batch. If some of the installed packages using an older Python version are not triaged for the upgrade, the package manager will throw dependency conflicts. This makes it important that the upgrade is carried via a --deep --changed-use @world upgrade, as well as that any stray packages are removed prior to it, e.g.: emerge --depclean emerge -1vUD @world emerge --depclean --------------------------------------SNIP---------------------------
This ticket has the status RESOLVED FIXED. However, the fix has been reverted one hour later, so this ticket should be reopened. https://gitweb.gentoo.org/repo/gentoo.git/commit/sys-apps/policycoreutils/policycoreutils-3.6.ebuild?id=323439c579bb530217935cfdc9e741b0a1cff36e
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3cc6da709ad4d69b7e5e231fe3b388c8d3a8b1fc commit 3cc6da709ad4d69b7e5e231fe3b388c8d3a8b1fc Author: Kenton Groombridge <concord@gentoo.org> AuthorDate: 2024-06-06 13:32:09 +0000 Commit: Kenton Groombridge <concord@gentoo.org> CommitDate: 2024-06-06 13:44:52 +0000 sys-apps/policycoreutils: enable py3.12 Closes: https://bugs.gentoo.org/932011 Signed-off-by: Kenton Groombridge <concord@gentoo.org> sys-apps/policycoreutils/policycoreutils-3.6.ebuild | 2 +- sys-apps/policycoreutils/policycoreutils-9999.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
