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.
https://build.opensuse.org/package/view_file/home:ojkastl_buildservice:docke...
... Requires: docker # Docker Compose V2 is a major version bump release of Docker Compose. # It has been completely rewritten from scratch in Golang (V1 was in Python). Obsoletes: python2-docker-compose < 2.0.0 Obsoletes: python3-docker-compose < 2.0.0 Obsoletes: python38-docker-compose < 2.0.0 Obsoletes: python39-docker-compose < 2.0.0 Obsoletes: python310-docker-compose < 2.0.0 Provides: python2-docker-compose = %{version} Provides: python3-docker-compose = %{version} Provides: python38-docker-compose = %{version} Provides: python39-docker-compose = %{version} Provides: python310-docker-compose = %{version}
You don't really provide any python*- module, so you should not state in the specfile that you do. IMHO this is a case where the obsolete-not-provided rpmlintrc warning is justifiable to be ignored. (https://github.com/rpm-software-management/rpmlint/blob/main/rpmlint/descrip...)
# docker-compose-switch is intended to ease the transition from v1 to v2 # as it provides the docker-compose binary that was dropped in v2 # As Recommends are not working on many systems, use Requires to make sure # we do not break existing setups Requires: docker-compose-switch ...
IMHO it would be much more logical to put the obsoletes tag into that package instead of the docker-compose package.