Hi Ben, 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!
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...)
I have added a rpmlintrc to ignore that error for now, let's see.
# 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.
That was my first try, but I got the obsolete-not-provided warning, so I tried to do it in docker-compose. As it does not fully work on Tumbleweed, I could of course change that again. I'll give it a try. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537