Hello all, Am 18.01.21 um 13:10 schrieb Dominique Leuenberger / DimStar:
On Mon, 2021-01-18 at 12:00 +0000, Dominique Leuenberger wrote:
Packages changed: python-rpm-macros (20200824.8fa42a7 -> 20210112.86f4d9d)
=== Details ===
==== python-rpm-macros ==== Version update (20200824.8fa42a7 -> 20210112.86f4d9d This change has potential for quite some headaches - it was in Staging for a long time to get things sorted out 'reasonably well', BUT:
depending on your python-* modules installed, this can be a rough weekfor you.
There is a large number of packages that did not like the change (none of the ring packages, so 'most' users probably won't feel it)
Honestly, I expected more to fail. Currently, we only have about ~400 probably Python related build failures in openSUSE:Factory standard and less than 300 unresolvables. A large part of those are python-azure-* packages for which a trivial fix has already been submitted. So most packages using python singlespec are in a good shape!
The main change is that the python-FOO spec files (when using the long established python-single-spec style, which we had already for py2/py3 in place) will produce python36-FOO and python38-FOO (the 38-FOO provides/obsoletes python3-FOO, helping for the migrationpath)
This is also potentially facing users doing a `zypper dup`. Some packages python-FOO successfully rebuilt and now require python38-BAR at runtime, but python-BAR did not build for the snapshot yet and still "only" provide python3-BAR. scipy is a prominent example for BAR (fixed today). Simply don't replace the package depending on python3-scipy just yet. The non-updated package will work with the new snapshot just fine. The file contents are the same (if python-FOO was not updated on top of it), using python 3.8.
Cheers, Dominique
Thanks Dominique, Matej and everyone else to help get this on track! Ben