On 11.05.23 at 10:05 Johannes Kastl wrote:
Should I properly rename the old package? I'll have a look how that is done with other packages...
Callum was kind enough to prepare an SR to rename files inside the python-ansible-compat-3 package, rename the package itself in the spec and add Provides/Obsoletes, and after that it worked. So my guess would be that even though there were two packages in the repository (one with 3.0.2, one with 4.0.2), OBS ignored the former and only used the latter. Just as it would ignore any older versions of packages it finds in other repositories in the build target's setup. As a working hypothesis this is good enough. Thanks Callum! Have a nice weekend everyone. 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