This package does not support Python 3.12. Please test it with Python 3.12 as a matter of urgency as the default will change in early June, as per message on gentoo-dev: https://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg99104.html. Please check the information provided in the tracker. Ask in #gentoo-python on IRC if need any help.
gnome-keyring also requires gcr:0 which is also not ready for python3.12. There is a gcr:4 which is OK with python3.12, so it would need to use that as well as updating PYTHON_COMPAT.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01544d93dbf5f86044c0b09df646c18d07e716e9 commit 01544d93dbf5f86044c0b09df646c18d07e716e9 Author: Eli Schwartz <eschwartz93@gmail.com> AuthorDate: 2024-06-04 23:19:26 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-06-06 00:44:40 +0000 gnome-base/gnome-keyring: enable py3.12 Only needed for tests, tests pass. Closes: https://bugs.gentoo.org/929601 Signed-off-by: Eli Schwartz <eschwartz93@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> gnome-base/gnome-keyring/gnome-keyring-42.1-r2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Unfortunately that is not enough. The ebuild still requires gcr:0 which still requires python3.11. Should I open a separate bug for that?
No, that was already tracked by bug 929290 which I fixed in the same push. Also, since gnome-keyring doesn't depend on a python 3.12 interface of gcr -- rather, gcr internally uses python as part of its src_compile / src_install -- both bugs could be fixed independently.
The lack of version bump threw me off, but now I see if it's only the deps that are changing, it gets fixed even without a re-emerge. Thanks and sorry for the extra noise.
