The latest stable version of dev-python/protobuf-python (4.21.12) misses support for python 3.12. protobuf-python-4.21.12.ebuild:PYTHON_COMPAT=( python3_{10..11} ) protobuf-python-4.21.9.ebuild:PYTHON_COMPAT=( python3_{10..12} ) protobuf-python-4.22.5.ebuild:PYTHON_COMPAT=( python3_{10..12} ) protobuf-python-4.23.3.ebuild:PYTHON_COMPAT=( python3_{10..12} ) protobuf-python-9999.ebuild:PYTHON_COMPAT=( python3_{10..12} ) This leads to nice blockers when trying to enable python3_12 as recommended in the last news item.
See also the comment in the stable request bug: https://bugs.gentoo.org/923809#c7
ping
The version in the summary is misleading then.
(In reply to Sam James from comment #3) > The version in the summary is misleading then. Isn't it exactly protobuf-python-4.21.12 that is buggy?
(In reply to Matthias Schwarzott from comment #4) > (In reply to Sam James from comment #3) > > The version in the summary is misleading then. > > Isn't it exactly protobuf-python-4.21.12 that is buggy? It could be read as "this version should be stabled, because the current stable has no py3.12".
what is really misleading is that all other versions including the previous one have 3.12 flag. So the only current stable ebuild is missing it. Also, why takes so long to figure it out and fix the stable tree? Back to constrictive communication: I forked it (3 months ago), added python 3.12 flag, and have not experienced any problem.
(In reply to Sam James from comment #5) > It could be read as "this version should be stabled, because the current > stable has no py3.12". Well, I didn't read it that way, but that's a "solution" to dependency issues too of course. Although it's still weird that every version of `dev-python/protobuf-python` has Py3.12 enabled, except 4.21.12. Not sure if mistake or if 4.21.12 really is incompatible with Py3.12, but it's clumsy nonetheless. Today I couldn't figure out why `sci-libs/onnx` refused to have Py3.12 enabled. Portage didn't give me any clue unfortunately, until I saw `onnx` depended on `protobuf-python`... One sync later, since 4.22.5 was stabilised yesterday, it all works again. But still I think 4.21.12 should be fixed, if there's anything to fix to begin with.
Protobuf is so insanely fragile that I don't want to try figure out why someone left it out.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea43d63d1245912a9bf8e259b70f3e2cdf51d204 commit ea43d63d1245912a9bf8e259b70f3e2cdf51d204 Author: Paul Zander <negril.nx+gentoo@gmail.com> AuthorDate: 2024-07-07 20:01:48 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-07-09 12:51:25 +0000 dev-python/protobuf-python: update 5.27.2, drop 9999 protobuf-python can no longer be build from github archives. https://github.com/protocolbuffers/protobuf/blob/main/python/README.md#building-from-setuppy Closes: https://bugs.gentoo.org/920646 Closes: https://bugs.gentoo.org/933068 Closes: https://bugs.gentoo.org/927521 Closes: https://github.com/gentoo/gentoo/pull/36885 Signed-off-by: Paul Zander <negril.nx+gentoo@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> .../protobuf-python/protobuf-python-5.27.2.ebuild | 74 ++++---------------- .../protobuf-python/protobuf-python-9999.ebuild | 79 ---------------------- 2 files changed, 13 insertions(+), 140 deletions(-)
