On Mittwoch, 4. Juli 2018 19:11:49 686f6c6d wrote:
Greetings,
I was under the naive impression that after the py2/3 split, the packages from the devel:languages:python OBS project are released into the devel:languages:python/python3 repos based on their name (everything /^python3-/ goes into d:l:python3); in other words, I wanted to configure my python3-only servers to only use the python3 repo. But apparently this simple logic is not what is happening, there are many python3-* packages in d:l:python.
In fact, it's the other way around... There's a single repo d:l:python, that serves our needs (and a couple of subrepos that tries to reduce the sheer number of packages in a single repo). Most packages in d:l:py generate python2- and python3- packages from a single spec nowadays. This paves the way to generate pypy2 and/or pypy3 versions as well without touching the spec, all controlled with rpm macros.
Can someone explain what is really happening? Is this a temporary state or will I have to keep enabling both python{,3} repos on my python3 servers?
Just don't use the d:l:python3 repos anymore. If you depend on a package, that isn't in d:l:py (nor in d:l:py:{aws,azure,flask,...}, but in d:l:py3, you might want to help by converting it to single spec specification with the help of https://en.opensuse.org/openSUSE:Packaging_Python_Singlespec or just ask. If you want to limit your systems to python3, don't install python2{,-base} nor any dependencies and add zypper locks. 15.0 and TW tend to prefer python3, but I never tried that, though. Cheers, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org