Help needed with lots of python related build failures in openSUSE:Backports:SLE-15-SP3
Hello team, Leap 15.3 Beta is getting closer and closer and we're facing a lot of python build issues in Leap 15.3. *Checkin Deadline for Beta is on 12th Feb. Where to find build failures? I'm using following filter with "py" in the filter box. That gives me 95 at this very moment. https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP3?defaults=0&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&disabled=1&excluded=1&locked=1&deleting=1&unknown=1&arch_x86_64=1&repo_standard=1 Could you please look at the build failures and help us to reduce the build fails? Max has reached out to me as this is currently too much for openSUSE Release Team. Just to note openSUSE:Backports is where Leap 15.3+ packages will live from now on, that's a project structure change compared to Closing the Leap Gap. *Submit requests should bedone against openSUSE:Leap:15.3, which has auto-redirect with exception of new packages. New packages unfortunatelly have to be submitted to a specific project, in Leap 15.3 case openSUSE:Backports:SLE-15-SP3 ) [0] https://en.opensuse.org/openSUSE:Roadmap [1] https://en.opensuse.org/Portal:Jump/Policy/SubmitRequests#So_where_do_I_subm... Thank you very much in advance -- Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic
Hello, Am 20.01.21 um 16:29 schrieb Lubos Kocman:
Hello team,
Leap 15.3 Beta is getting closer and closer and we're facing a lot of python build issues in Leap 15.3. *Checkin Deadline for Beta is on 12th Feb.
Referring to your other thread starter from two days ago "python refresh in Leap", it is still unclear to me what "updating python" is meant to be in Leap 15.3. On a recently revoked SR to Leap for astropy, which requires Python >= 3.7, I received multiple comments from you and others that Leap now has the python 3.9 interpreter. But nothing has been mentioned about packages. If you don't have any packages populating sitelib, starting at setuptools, you can't do much on the distro level. You can probably use pip, but that does not concern any packaging from the openSUSE side then. So it seems all the python packages for Leap 15.3 /SLE-15-SP3 are stuck on python 3.6. Note that Numpy and related packages are currently dropping support for Python 3.6 by specification of NEP 29.
Where to find build failures? I'm using following filter with "py" in the filter box. That gives me 95 at this very moment. https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP3?defaults=0&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&disabled=1&excluded=1&locked=1&deleting=1&unknown=1&arch_x86_64=1&repo_standard=1
Could you please look at the build failures and help us to reduce the build fails? Max has reached out to me as this is currently too much for openSUSE Release Team.
You might tremendously benefit from the recent switch to python36 and python38 flavors in Tumbleweed. Many packages in Factory ring0 and ring1 already have been fixed to build on python 3.6 (again) by adding package requirements such as backported importlib-metadata, dataclasses and so on. Many packages not in ring1 are being fixed right now. As a consequence, if it builds in Factory for python36, you have a good chance, that it will build in openSUSE:Backports:SLE-15-SP3 for python3 as well. (Unless the packager forgot to address a possible python3 = 3.6 when fixing stuff for python36 [1, 2]). devel:languages:python:backports is automatically populated from Factory. I suggest to adjust the openSUSE_Leap_15.3 repository in that project to have a path to openSUSE:Backports:SLE-15-SP3 and you will quickly see what you can submit and what needs fixing. Cheers, Ben [1] https://build.opensuse.org/request/show/865083 [2] https://build.opensuse.org/request/show/865084
Hello Ben, let's not mix threads these are two separate requests. And build failures is what currently blocks possible transition to Beta. So I consider that a higher priority. I will look into astropy and will reach out to you back. Lubos On Wed, 2021-01-20 at 22:33 +0100, Ben Greiner wrote:
Hello,
Am 20.01.21 um 16:29 schrieb Lubos Kocman:
Hello team,
Leap 15.3 Beta is getting closer and closer and we're facing a lot of python build issues in Leap 15.3. *Checkin Deadline for Beta is on 12th Feb.
Referring to your other thread starter from two days ago "python refresh in Leap", it is still unclear to me what "updating python" is meant to be in Leap 15.3. On a recently revoked SR to Leap for astropy, which requires Python >= 3.7, I received multiple comments from you and others that Leap now has the python 3.9 interpreter. But nothing has been mentioned about packages. If you don't have any packages populating sitelib, starting at setuptools, you can't do much on the distro level. You can probably use pip, but that does not concern any packaging from the openSUSE side then.
So it seems all the python packages for Leap 15.3 /SLE-15-SP3 are stuck on python 3.6. Note that Numpy and related packages are currently dropping support for Python 3.6 by specification of NEP 29.
Where to find build failures? I'm using following filter with "py" in the filter box. That gives me 95 at this very moment. https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP3?defaults=0&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&disabled=1&excluded=1&locked=1&deleting=1&unknown=1&arch_x86_64=1&repo_standard=1
Could you please look at the build failures and help us to reduce the build fails? Max has reached out to me as this is currently too much for openSUSE Release Team.
You might tremendously benefit from the recent switch to python36 and python38 flavors in Tumbleweed. Many packages in Factory ring0 and ring1 already have been fixed to build on python 3.6 (again) by adding package requirements such as backported importlib-metadata, dataclasses and so on. Many packages not in ring1 are being fixed right now. As a consequence, if it builds in Factory for python36, you have a good chance, that it will build in openSUSE:Backports:SLE-15-SP3 for python3 as well. (Unless the packager forgot to address a possible python3 = 3.6 when fixing stuff for python36 [1, 2]).
devel:languages:python:backports is automatically populated from Factory. I suggest to adjust the openSUSE_Leap_15.3 repository in that project to have a path to openSUSE:Backports:SLE-15-SP3 and you will quickly see what you can submit and what needs fixing.
Cheers, Ben
-- Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic
I noticed two which were not in Factory, and submitted requests to get
them into d-l-py
https://build.opensuse.org/request/show/865046
https://build.opensuse.org/request/show/865048
The diffs could be applies to SLE also to fix them
https://build.opensuse.org/package/rdiff/home:jayvdb:py-new/python-anymarkup-core?opackage=python-anymarkup-core&oproject=openSUSE%3ABackports%3ASLE-15-SP3&rev=6
https://build.opensuse.org/package/rdiff/home:jayvdb:py-new/python-anymarkup?opackage=python-anymarkup&oproject=openSUSE%3ABackports%3ASLE-15-SP3&rev=12
Is there a list of Python packages in SLE which are not in Factory, or
way to easily determine that?
I'd be keen to try getting them into Factory.
On Wed, Jan 20, 2021 at 11:30 PM Lubos Kocman
Hello team,
Leap 15.3 Beta is getting closer and closer and we're facing a lot of python build issues in Leap 15.3. *Checkin Deadline for Beta is on 12th Feb.
Where to find build failures? I'm using following filter with "py" in the filter box. That gives me 95 at this very moment. https://build.opensuse.org/project/monitor/openSUSE:Backports:SLE-15-SP3?defaults=0&failed=1&unresolvable=1&broken=1&blocked=1&dispatching=1&scheduled=1&building=1&finished=1&signing=1&disabled=1&excluded=1&locked=1&deleting=1&unknown=1&arch_x86_64=1&repo_standard=1
Could you please look at the build failures and help us to reduce the build fails? Max has reached out to me as this is currently too much for openSUSE Release Team.
Just to note openSUSE:Backports is where Leap 15.3+ packages will live from now on, that's a project structure change compared to Closing the Leap Gap. *Submit requests should bedone against openSUSE:Leap:15.3, which has auto-redirect with exception of new packages.
New packages unfortunatelly have to be submitted to a specific project, in Leap 15.3 case openSUSE:Backports:SLE-15-SP3 )
[0] https://en.opensuse.org/openSUSE:Roadmap [1] https://en.opensuse.org/Portal:Jump/Policy/SubmitRequests#So_where_do_I_subm...
Thank you very much in advance
-- Lubos Kocman Release Manager openSUSE Leap
SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic
-- John Vandenberg
On 1/21/21 7:52 PM, jayvdb@gmail.com wrote:
I noticed two which were not in Factory, and submitted requests to get them into d-l-py
https://build.opensuse.org/request/show/865046 https://build.opensuse.org/request/show/865048
The diffs could be applies to SLE also to fix them https://build.opensuse.org/package/rdiff/home:jayvdb:py-new/python-anymarkup-core?opackage=python-anymarkup-core&oproject=openSUSE%3ABackports%3ASLE-15-SP3&rev=6 https://build.opensuse.org/package/rdiff/home:jayvdb:py-new/python-anymarkup?opackage=python-anymarkup&oproject=openSUSE%3ABackports%3ASLE-15-SP3&rev=12
Is there a list of Python packages in SLE which are not in Factory, or way to easily determine that? I'd be keen to try getting them into Factory.
The most likely case for packages in this state is that they were in Factory and were then dropped for some reason, you can normally see the reason with the following command osc log -D openSUSE:Factory package-name These too packages seem to be an exception to that rule, but hopefully there shouldn't be many. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (4)
-
Ben Greiner -
jayvdb＠gmail.com -
Lubos Kocman -
Simon Lees