Am 06.07.22 um 21:35 schrieb Ben Greiner:
Am 06.07.22 um 20:16 schrieb Johannes Kastl:
On 06.07.22 at 19:57 Johannes Kastl wrote:
On 06.07.22 at 18:09 Ben Greiner wrote:
Am 06.07.22 um 17:43 schrieb Johannes Kastl:
And can I somehow create all those python3* things per macro?
Obsoletes: %{python_module docker-compose < 2.0.0} would expand to all *currently active* python3 flavors in Tumbleweed, but not python2-..., or python3-..., or the formerly existing python36-... which still might exist in some upgrade path with a long gap since the last Tumbleweed update.
I'll give that a try, thanks!
That did not work in OBS, while locally it builds fine for Tumbleweed:
[ 39s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --undefine _enable_debug_packages --define 'disturl obs://build.opensuse.org/home:ojkastl_buildservice:docker_compose_etc/openSUSE_Tumbleweed/3287f6f4a59403182bded7b2ef95349c-docker-compose-switch' /home/abuild/rpmbuild/SOURCES/docker-compose-switch.spec [ 39s] error: line 39: No rich dependencies allowed for this type: Obsoletes: ( python38-docker-compose < 2.0.0 ) ( python39-docker-compose < 2.0.0 ) ( python310-docker-compose < 2.0.0 ) [ 39s] ### VM INTERACTION START ###
Dang, I did not think of that. The %python_module macro now creates rich dependencies. Sorry you have to spell it out explicitly then. (I was thinking of https://en.opensuse.org/openSUSE:Packaging_Python#%python_module_in_Provides which is apparently not correct anymore. Surprised that this regression did not come up since the introduction of boolean dependencies for %python_module.)
I retract my previous statement: This should actually be handled correctly by python-rpm-macros since python-rpm-macros-20210131: https://github.com/openSUSE/python-rpm-macros/pull/99. What's the python-rpm-macros version, you are using or do you have a special prjconf redefinition differing from Factory? - Ben