Dirk Mueller píše v Pá 05. 07. 2019 v 18:32 +0200:
On Thursday, July 4, 2019 4:29:45 PM CEST Tomas Chvatal wrote:
All the macros were synced by me to the latest python-rpm-macros and were released properly in IBS. You can use them all quite fine if you build against the :Update and not against :GA.
just look at dlp:backports yourself. example package python-mox3.
only makes problems doesn't solve any (most recent breaking everything example is the rename of python-Sphinx to python-Sphinx1 ).
So your CI is picking just selective packages or what is the issue?
by renaming the package to python-sphinx1, python2-sphinx was disappearing and instead we got the stone old python2-sphinx from SLE15:GA, which was obviously missing the fixes for python 3.x enablement, so no package on SLE15:SLE15 etc was building anymore.
I really didn't understand this, so I reverted this rename, which fixes the problem.
The Sphinx1 i didn't call as python2-Sphinx because I expected you guys to enable the python3 again because you would still need it, as last upgrade of Sphinx it was reverted few times to get you to migrate).
did you tell anyone of "us" what the issue is? :-) if so, what is the issue ?
Do they need all 1000+ packages as pypy versions? How likely is it that they all work with pypy? I would be curious to see an experiement on this.
Quite big load of them really work (some need minor tweaks in build commands), we just didn't have time to enable it. When singlespec was created it was with this in mind actually, because we knew that the python2 will hopefully die quickly.
I really can't imagine how this would work with how singlespec works at the moment (building yes, working no).
Because we are not dropping any stuff when we do the skip python, with the naming I always add another package that provides the older version that still provides python2 and everything stays resolvable on TW.
I think keeping the old package as python2-$foo would generally work if it is needed by anything.
Should we email somewhere to notify you guys about new deps? Or can we tag it somewhere?
Yes, some coordination before things break would be really great, how about just starting a mail discussion here?
So in order to make it happily work we need to have some safeguards to not explode your stuff.
1) announce all new added compat packages here on the mailinglist in a form of 'python2-whatever was added to d:l:py:numeric' as a headsup.
2) we need to regen the :backports repo from TW not cron-based but more like release based. Thus whenever new snapshot from TW is added we should regen the :backports. Any idea how to do this?
The point 1 takes care of at least some form of notification, but in the end TW integration/stagings might take different time until it propagates completely inside...