Where did python3-something Provides go?
Hi, for the last years, the python3 packages on my tumbleweed systems kind of nicely upgraded to newer versions of python, both for the base interpreters and some addon packages that I learned to rely on for some of my own system management rpms. I was used to use something like this in my own dependencies: Requires: python3-pycryptodome and that magically pulls in + also updates, along with major python updates, the respective addon packages (other one I'm used to use, is python3-zypp-plugin) Today I noticed that apparently, that does not work anymore. Reason being that these packages no longer contain the "Provides: python3-pycryptodome" etc entries, since python312 (also for python313). Right now with my established practice, it seems I'll be stuck with python311 packages forever, or things will break once they get removed from tumbleweed. Is there something published on this change? Anything I should do instead to express such requirements and get back to the magically working updating I'm used to? Or is python distro packaging a fatally lost cause + I should just forget about it? best regards Patrick trick:~ # rpm -q --provides python311-pycryptodome python3-pycrypto = 3.21.0 python3-pycryptodome = 3.21.0-1.2 python3.11dist(pycryptodome) = 3.21 python311-pycrypto = 3.21.0 python311-pycryptodome = 3.21.0-1.2 python311-pycryptodome(x86-64) = 3.21.0-1.2 python3dist(pycryptodome) = 3.21 trick:~ # rpm -q --provides python312-pycryptodome python3.12dist(pycryptodome) = 3.21 python312-pycrypto = 3.21.0 python312-pycryptodome = 3.21.0-1.2 python312-pycryptodome(x86-64) = 3.21.0-1.2 python3dist(pycryptodome) = 3.21
On Tue Dec 24, 2024 at 9:17 AM CET, Patrick Schaaf via openSUSE Factory wrote:
Today I noticed that apparently, that does not work anymore. Reason being that these packages no longer contain the "Provides: python3-pycryptodome" etc entries, since python312 (also for python313).
It works as it always did. There is that thing called “primary Python interpreter”, the one Python, which is used as default. When you run /usr/bin/python3 you get that, when you ask in your package for python3-pycryptodrome you get that. Currently it is Python 3.11 and hopefully soon (after the holidays) we will switch to 3.13 and break everything. Then you will get automagically python313-pycryptodrome instead. Best, Matěj -- http://matej.ceplovi.cz/blog/, @mcepl@en.osm.town GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 We have been called to form consciences, not to replace them. -- Pope Francis in Amoris Lætitia, 37
On Tue, 24 Dec 2024 at 11:12, Matěj Cepl <mcepl@cepl.eu> wrote:
Today I noticed that apparently, that does not work anymore. Reason being that these packages no longer contain the "Provides:
On Tue Dec 24, 2024 at 9:17 AM CET, Patrick Schaaf via openSUSE Factory wrote: python3-pycryptodome"
etc entries, since python312 (also for python313).
It works as it always did. There is that thing called “primary Python interpreter”, the one Python, which is used as default. When you run /usr/bin/python3 you get that, when you ask in your package for python3-pycryptodrome you get that. Currently it is Python 3.11 and hopefully soon (after the holidays) we will switch to 3.13 and break everything. Then you will get automagically python313-pycryptodrome instead.
Thank you Matěj, and also Dominuque, for the lucid explanations. That makes a lot of sense, and I'm happy that I don't need to change anything about my private packaging practise :-) Have a nice festive season! Patrick
participants (2)
-
Matěj Cepl -
Patrick Schaaf