15 Feb
2018
15 Feb
'18
08:09
Am Wed, 14 Feb 2018 13:04:14 +0100
schrieb Olaf Hering
How is Leap 15.0 supposed to replace packages that existed in previous Leap versions?
Even openQA fails, according to bug#1069773. I can not reach the referenced openQA host with the logfile, but I'm sure that bug is also about the fact that python-lockfile-0.10.2 from Leap 42 is newer than the variant from Leap 15. I'm sure the individual pkg maintainers can not do anything about bugs in python-rpm-macros. Would a valid fix for all python packages be like "Obsoletes: python-pkg < version-release;Obsoletes python-pkg > version-release"? Since python2-pkg and python3-pkg come from the very same build that should fix the upgrade path. Olaf