sys-libs/libblockdev should have python3_12 at PYTHON_SINGLE_TARGET
When you say "should", do you mean you have actually confirmed it to work with py3.12?
Created attachment 874368 [details, diff] Whatever... Well. I cannot test exhaustively every package before filing a bug report about a python version upgrade. I reported all the installed packages not currently supporting python3_12 at PYTHON_SINGLE_TARGET. Ideally there should be some automated way to test that but there isn't. That being said, after editing some ebuilds (diff attached), I managed to run succesfully the following command at x86. I am also pasting the output. Stalingrad /usr/src # FEATURES="collision-protect ipc-sandbox network-sandbox sandbox split-log split-elog strict test userfetch userpriv usersandbox -parallel-install" USE=test emerge -va1 libblockdev These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 5.13 s (backtrack: 0/20). [ebuild R ] sys-libs/libblockdev-3.0.4:0/3::gentoo USE="cryptsetup nvme test* tools -device-mapper -escrow -gtk-doc -introspection -lvm" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-libs/libblockdev-3.0.4::gentoo >>> Installing (1 of 1) sys-libs/libblockdev-3.0.4::gentoo >>> Completed (1 of 1) sys-libs/libblockdev-3.0.4::gentoo >>> Jobs: 1 of 1 complete Load avg: 2.60, 1.83, 4.30 * GNU info directory index is up-to-date.
(In reply to marios4 from comment #2) > Created attachment 874368 [details, diff] [details, diff] > Whatever... > > Well. I cannot test exhaustively every package before filing a bug report > about a python version upgrade. I reported all the installed packages not > currently supporting python3_12 at PYTHON_SINGLE_TARGET. Ideally there > should be some automated way to test that but there isn't. > The question was to clarify if you've tested it and it works, or if you know of breakage. It is fine to file the bug asking for support to be added. But the point was "should support" is ambiguous. > That being said, after editing some ebuilds (diff attached), I managed to > run succesfully the following command at x86. I am also pasting the output. > Did you run the test suite for each modified package? > Stalingrad /usr/src # FEATURES="collision-protect ipc-sandbox > network-sandbox sandbox split-log split-elog strict test userfetch userpriv > usersandbox -parallel-install" USE=test emerge -va1 libblockdev > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > Dependency resolution took 5.13 s (backtrack: 0/20). > > [ebuild R ] sys-libs/libblockdev-3.0.4:0/3::gentoo USE="cryptsetup > nvme test* tools -device-mapper -escrow -gtk-doc -introspection -lvm" > PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11" 0 KiB > > Total: 1 package (1 reinstall), Size of downloads: 0 KiB > > Would you like to merge these packages? [Yes/No] > >>> Verifying ebuild manifests > >>> Emerging (1 of 1) sys-libs/libblockdev-3.0.4::gentoo > >>> Installing (1 of 1) sys-libs/libblockdev-3.0.4::gentoo > >>> Completed (1 of 1) sys-libs/libblockdev-3.0.4::gentoo > >>> Jobs: 1 of 1 complete Load avg: 2.60, 1.83, 4.30 > > * GNU info directory index is up-to-date.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=62283303d6d8b7e2c037230fad3b1f2bbf792973 commit 62283303d6d8b7e2c037230fad3b1f2bbf792973 Author: Alfred Wingate <parona@protonmail.com> AuthorDate: 2023-11-24 16:14:44 +0000 Commit: Marek Szuba <marecki@gentoo.org> CommitDate: 2023-11-28 09:38:36 +0000 sys-libs/libblockdev: enable py3.12 Closes: https://bugs.gentoo.org/917028 Closes: https://github.com/gentoo/gentoo/pull/33790 Signed-off-by: Alfred Wingate <parona@protonmail.com> Signed-off-by: Marek Szuba <marecki@gentoo.org> sys-libs/libblockdev/libblockdev-3.0.4.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
