Leap 15.3 - Python status
Hi, since some time the status of python in 15.3 is questionable. Currently all builds fail with nothing provides python3-base = 3.6.10 needed by python3, (got version 3.6.12-10.1) before that it had trouble finding python-relatorio.... Is there a rebuild or something triggered? Thanks Axel
Hi, Am 04.01.21 um 16:16 schrieb Axel Braun:
Hi,
since some time the status of python in 15.3 is questionable. Currently all builds fail with Which project/repo are you talking about exactly?
nothing provides python3-base = 3.6.10 needed by python3, (got version 3.6.12-10.1)
before that it had trouble finding python-relatorio....
Is there a rebuild or something triggered?
Thanks Axel
python3 and python3-base are themeselves not in d:l:p:backports, the packages are pulled from openSUSE:Leap15.3:Update. python3-base in openSUSE:Leap15.3:Update inherits from SUSE:SLE-15:Update while python3 inherits from SUSE:SLE-15-SP3:GA. Both are version 3.6.12. python3 probably just needs a rebuild trigger (if that is the way to do it on Leap, idk). AFAIK, there has been some internal discussion within SUSE about renaming to python36 in Leap (which was rejected) and keeping stuff in sync with d:l:p:Factory. Something is stuck in the middle here, but might need to wait until the responsible Leap or Python maintainer is back from vacation. Ben
Hello Ben, Am Montag, 4. Januar 2021, 17:36:05 CET schrieb Ben Greiner:
Am 04.01.21 um 16:16 schrieb Axel Braun:
since some time the status of python in 15.3 is questionable. Currently all builds fail with
Which project/repo are you talking about exactly?
https://build.opensuse.org/project/show/Application:ERP:GNUHealth:Factory
nothing provides python3-base = 3.6.10 needed by python3, (got version 3.6.12-10.1)
before that it had trouble finding python-relatorio....
Is there a rebuild or something triggered?
python3 and python3-base are themeselves not in d:l:p:backports, the packages are pulled from openSUSE:Leap15.3:Update.
python3-base in openSUSE:Leap15.3:Update inherits from SUSE:SLE-15:Update while python3 inherits from SUSE:SLE-15-SP3:GA. Both are version 3.6.12. python3 probably just needs a rebuild trigger (if that is the way to do it on Leap, idk).
Hm, sounds confusing....
AFAIK, there has been some internal discussion within SUSE about renaming to python36 in Leap (which was rejected) and keeping stuff in sync with d:l:p:Factory. Something is stuck in the middle here, but might need to wait until the responsible Leap or Python maintainer is back from vacation.
I forgot that Wednesday is a vacation in Nürnberg if I'm not mistaken, so I guess some people are still on vacation. Thanks for the hint Axel
Hi Axel, Am 04.01.21 um 17:52 schrieb Axel Braun:
Hello Ben,
Am Montag, 4. Januar 2021, 17:36:05 CET schrieb Ben Greiner:
Am 04.01.21 um 16:16 schrieb Axel Braun:
since some time the status of python in 15.3 is questionable. Currently all builds fail with Which project/repo are you talking about exactly? https://build.opensuse.org/project/show/Application:ERP:GNUHealth:Factory
The openSUSE_Leap_15.3 repo in that project has openSUSE:Leap:15.3 as path directly, so my comment about d:l:p:backports and :Update does not apply. The inheritance discrepancy is the same though, and so are the resulting version numbers (both 3.6.12, but apparently not rebuilt yet).
nothing provides python3-base = 3.6.10 needed by python3, (got version 3.6.12-10.1)
before that it had trouble finding python-relatorio....
It should be coming from path openSUSE:Backports:SLE-15-SP3 but that one is unresolvable because it can't find python-python-magic which is "scheduled" in the same repo right now. The whole project is in a rebuild phase. python-python-magic has never been built successfully though. So maybe it needs to be fixed for Leap 15.3. It has built in d:l:p openSUSE_Leap_15.3 though (currently scheduled, too).
Is there a rebuild or something triggered? python3 and python3-base are themeselves not in d:l:p:backports, the packages are pulled from openSUSE:Leap15.3:Update.
python3-base in openSUSE:Leap15.3:Update inherits from SUSE:SLE-15:Update while python3 inherits from SUSE:SLE-15-SP3:GA. Both are version 3.6.12. python3 probably just needs a rebuild trigger (if that is the way to do it on Leap, idk). Hm, sounds confusing....
AFAIK, there has been some internal discussion within SUSE about renaming to python36 in Leap (which was rejected) and keeping stuff in sync with d:l:p:Factory. Something is stuck in the middle here, but might need to wait until the responsible Leap or Python maintainer is back from vacation. I forgot that Wednesday is a vacation in Nürnberg if I'm not mistaken, so I guess some people are still on vacation.
Thanks for the hint Axel
HTHBen
Hi Ben, Am Montag, 4. Januar 2021, 18:20:05 CET schrieb Ben Greiner:
Am 04.01.21 um 17:52 schrieb Axel Braun:
Am Montag, 4. Januar 2021, 17:36:05 CET schrieb Ben Greiner:
Am 04.01.21 um 16:16 schrieb Axel Braun:
since some time the status of python in 15.3 is questionable. Currently all builds fail with
Which project/repo are you talking about exactly?
https://build.opensuse.org/project/show/Application:ERP:GNUHealth:Factory
The openSUSE_Leap_15.3 repo in that project has openSUSE:Leap:15.3 as path directly, so my comment about d:l:p:backports and :Update does not apply. The inheritance discrepancy is the same though, and so are the resulting version numbers (both 3.6.12, but apparently not rebuilt yet).
nothing provides python3-base = 3.6.10 needed by python3, (got version 3.6.12-10.1)
before that it had trouble finding python-relatorio....
It should be coming from path openSUSE:Backports:SLE-15-SP3 but that one is unresolvable because it can't find python-python-magic which is "scheduled" in the same repo right now.
Hm? Looking at https://build.opensuse.org/package/show/ openSUSE:Backports:SLE-15-SP3/python-python-magic it builds since November 27. Regarding relatorio, that was bumped from Leap 15.2 into the SLE-15-SP3 repo. I had the understanding, that if a package is build in the same repository, it is used preferrably. Obviously that does not work in this case.
The whole project is in a rebuild phase. python-python-magic has never been built successfully though. So maybe it needs to be fixed for Leap 15.3. It has built in d:l:p openSUSE_Leap_15.3 though (currently scheduled, too).
Looks like the setup 'what comes from where' for python needs some fine- tuning. I guess this is a side-effect from the CTLG activity.... Cheers Axel
Am 04.01.21 um 21:58 schrieb Axel Braun:
It should be coming from path openSUSE:Backports:SLE-15-SP3 but that one
is unresolvable because it can't find python-python-magic which is "scheduled" in the same repo right now. Hm? Looking at https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3/python... it builds since November 27.
But all four build targets only contain the src rpms not the actual python3-python-magic package! Very strange.
Regarding relatorio, that was bumped from Leap 15.2 into the SLE-15-SP3 repo. I had the understanding, that if a package is build in the same repository, it is used preferrably. Obviously that does not work in this case. It cannot build because of the lack of python[23]-python-magic.
Looks like the setup 'what comes from where' for python needs some fine- tuning. I guess this is a side-effect from the CTLG activity....
I am not familiar with that acronym.
Cheers Axel
Ben
Am 04.01.21 um 21:58 schrieb Axel Braun:
It should be coming from path openSUSE:Backports:SLE-15-SP3 but that one
is unresolvable because it can't find python-python-magic which is "scheduled" in the same repo right now. Hm? Looking at https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3/python... it builds since November 27.
But all four build targets only contain the src rpms not the actual python3-python-magic package! Very strange.
Regarding relatorio, that was bumped from Leap 15.2 into the SLE-15-SP3 repo. I had the understanding, that if a package is build in the same repository, it is used preferrably. Obviously that does not work in this case. It cannot build because of the lack of python[23]-python-magic.
Looks like the setup 'what comes from where' for python needs some fine- tuning. I guess this is a side-effect from the CTLG activity....
I am not familiar with that acronym.
Cheers Axel
Ben
Good morning Ben, Am Montag, 4. Januar 2021, 22:42:57 CET schrieb Ben Greiner:
It should be coming from path openSUSE:Backports:SLE-15-SP3 but that one
is unresolvable because it can't find python-python-magic which is "scheduled" in the same repo right now.
Hm? Looking at https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3/pyt hon-python-magic it builds since November 27. But all four build targets only contain the src rpms not the actual
Am 04.01.21 um 21:58 schrieb Axel Braun: python3-python-magic package! Very strange.
Regarding relatorio, that was bumped from Leap 15.2 into the SLE-15-SP3 repo. I had the understanding, that if a package is build in the same repository, it is used preferrably. Obviously that does not work in this case.
It cannot build because of the lack of python[23]-python-magic.
Yes, if it builds but only creates a source pacakge...thats obvious
Looks like the setup 'what comes from where' for python needs some fine- tuning. I guess this is a side-effect from the CTLG activity....
I am not familiar with that acronym.
Ah, sorry, Closing the Leap Gap - The merge of Leap and SLE in Leap 15.3 Lets see if the resolution of the bug in Matěj's answer fixes things... Cheers Axel
Good morning, Am Montag, 4. Januar 2021, 22:42:57 CET schrieb Ben Greiner:
Regarding relatorio, that was bumped from Leap 15.2 into the SLE-15-SP3 repo. I had the understanding, that if a package is build in the same repository, it is used preferrably. Obviously that does not work in this case.
It cannot build because of the lack of python[23]-python-magic.
While in general the mismatch in the baselibs is resolved, this issues with relatorio / magic remains. Can I do anything to help resolving it? Cheers Axel
Ben Greiner píše v Po 04. 01. 2021 v 18:20 +0100:
Am Montag, 4. Januar 2021, 17:36:05 CET schrieb Ben Greiner:
Am 04.01.21 um 16:16 schrieb Axel Braun:
since some time the status of python in 15.3 is questionable. Currently all builds fail with Which project/repo are you talking about exactly? https://build.opensuse.org/project/show/Application:ERP:GNUHealth:Factory
Probably another fallout from https://bugzilla.suse.com/show_bug.cgi?id=1180377 Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 See, when the GOVERNMENT spends money, it creates jobs; whereas when the money is left in the hands of TAXPAYERS, God only knows what they do with it. Bake it into pies, probably. Anything to avoid creating jobs. -- Dave Barry
FYI: Please be aware of the parallel python39 support that landed in December. On Mon, 2021-01-04 at 23:23 +0100, Matěj Cepl wrote:
Ben Greiner píše v Po 04. 01. 2021 v 18:20 +0100:
Am Montag, 4. Januar 2021, 17:36:05 CET schrieb Ben Greiner:
Am 04.01.21 um 16:16 schrieb Axel Braun:
since some time the status of python in 15.3 is questionable. Currently all builds fail with Which project/repo are you talking about exactly? https://build.opensuse.org/project/show/Application:ERP:GNUHealth:Factory
Probably another fallout from https://bugzilla.suse.com/show_bug.cgi?id=1180377
Matěj
-- Lubos Kocman, Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg - Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
Axel Braun píše v Po 04. 01. 2021 v 16:16 +0100:
nothing provides python3-base = 3.6.10 needed by python3, (got version 3.6.12-10.1)
Most of the failures are fallout from https://bugzilla.suse.com/1180377 (which should be fixed in SLE- 15 by https://build.suse.de/request/show/233247 ). Then I see many failures of python2&3-packages (e.g. https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3/python... ) depending on python3-only ones (https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3/python...), which should be resolved by making former python3-only as well. Python 2 support in SLE-15 is legacy-only (and time-limited as well, IIRC). Anybody suggesting such changes both to Factory and to Leap 15.3 is more than welcome to do so. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Data matures like wine, applications like fish. -- James Governor http://redmonk.com/jgovernor/2007/04/05\ /why-applications-are-like-fish-and-data-is-like-wine/
participants (5)
-
Axel Braun -
Ben Greiner -
Benjamin Greiner -
Lubos Kocman -
Matěj Cepl