[opensuse-factory] Leap 42 can be used as a base, Leap 15 can not
Does anyone happen to know what changed in Leap 15 to cause all packages to go into unresolvable like that? openSUSE_Leap_15.0 x86_64 unresolvable: nothing provides rpm-build nothing provides gcc-PIE It is not obvious from the 'meta prj' output from the involved prjs why the first one works and the second does not: <repository name="openSUSE_Leap_42.3"> <path project="openSUSE.org:openSUSE:Leap:42.3:Update" repository="standard"/> <path project="openSUSE.org:openSUSE:Leap:42.3:Update" repository="ports"/> <arch>aarch64</arch> <arch>armv7l</arch> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.0"> <path project="openSUSE.org:openSUSE:Leap:15.0:Update" repository="standard"/> <path project="openSUSE.org:openSUSE:Leap:15.0:Update" repository="ports"/> <arch>aarch64</arch> <arch>i586</arch> <arch>x86_64</arch> </repository> I think the removal of "ports" would be a workaround. It seems :Ports got fixed, the included home:* prj is gone. Still, non-arm fails. Olaf
On Tuesday, 15 May 2018 08:49:50 CEST Olaf Hering wrote:
Does anyone happen to know what changed in Leap 15 to cause all packages to go into unresolvable like that?
openSUSE_Leap_15.0 x86_64 unresolvable: nothing provides rpm-build nothing provides gcc-PIE
It is not obvious from the 'meta prj' output from the involved prjs why the first one works and the second does not:
<repository name="openSUSE_Leap_42.3"> <path project="openSUSE.org:openSUSE:Leap:42.3:Update" repository="standard"/> <path project="openSUSE.org:openSUSE:Leap:42.3:Update" repository="ports"/> <arch>aarch64</arch> <arch>armv7l</arch> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.0"> <path project="openSUSE.org:openSUSE:Leap:15.0:Update" repository="standard"/> <path project="openSUSE.org:openSUSE:Leap:15.0:Update" repository="ports"/> <arch>aarch64</arch> <arch>i586</arch> <arch>x86_64</arch> </repository>
I think the removal of "ports" would be a workaround. It seems :Ports got fixed, the included home:* prj is gone. Still, non-arm fails.
Olaf
I also tried to sent an email to opensuse-buildservice but it did not come through (as I am not on the list). It seems a project config like ``` <repository name="openSUSE_Leap_15.0_update+ports"> <path project="openSUSE:Leap:15.0:Update" repository="standard"/> <path project="openSUSE:Leap:15.0:Update" repository="ports"/> <arch>x86_64</arch> <arch>ppc64le</arch> </repository> ``` causes a problem that no package dependencies for the x86_64 build can be found. Please see the example project https://build.opensuse.org/package/show/home:okurz:test-leap15-update/test-d... showing this problem. It also shows all other combinations that work, e.g. using only the GM repositories, using :Update for x86_64 only without ports, using Leap 42.3, etc. Is this a generic OBS problem or Leap 15.0 specific? Is there a best practice how to handle? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mai 15 2018, Olaf Hering <olaf@aepfle.de> wrote:
Does anyone happen to know what changed in Leap 15 to cause all packages to go into unresolvable like that?
openSUSE_Leap_15.0 x86_64 unresolvable: nothing provides rpm-build nothing provides gcc-PIE
That's because openSUSE:Leap:15.0:Ports/ports is pointing to openSUSE:Leap:15.0/ports (which has no route to the standard repository), instead of openSUSE:Leap:15.0/standard. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 15 May 2018 09:33:38 CEST Andreas Schwab wrote:
On Mai 15 2018, Olaf Hering <olaf@aepfle.de> wrote:
Does anyone happen to know what changed in Leap 15 to cause all packages to go into unresolvable like that?
openSUSE_Leap_15.0 x86_64 unresolvable: nothing provides rpm-build
nothing provides gcc-PIE
That's because openSUSE:Leap:15.0:Ports/ports is pointing to openSUSE:Leap:15.0/ports (which has no route to the standard repository), instead of openSUSE:Leap:15.0/standard.
I don't understand. Who should change what then? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mai 15 2018, Oliver Kurz <okurz@suse.de> wrote:
On Tuesday, 15 May 2018 09:33:38 CEST Andreas Schwab wrote:
On Mai 15 2018, Olaf Hering <olaf@aepfle.de> wrote:
Does anyone happen to know what changed in Leap 15 to cause all packages to go into unresolvable like that?
openSUSE_Leap_15.0 x86_64 unresolvable: nothing provides rpm-build
nothing provides gcc-PIE
That's because openSUSE:Leap:15.0:Ports/ports is pointing to openSUSE:Leap:15.0/ports (which has no route to the standard repository), instead of openSUSE:Leap:15.0/standard.
I don't understand. Who should change what then?
The project maintainer. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi there, On Tue, 15 May 2018, 10:01:59 +0200, Andreas Schwab wrote:
On Mai 15 2018, Oliver Kurz <okurz@suse.de> wrote:
On Tuesday, 15 May 2018 09:33:38 CEST Andreas Schwab wrote:
On Mai 15 2018, Olaf Hering <olaf@aepfle.de> wrote:
Does anyone happen to know what changed in Leap 15 to cause all packages to go into unresolvable like that?
openSUSE_Leap_15.0 x86_64 unresolvable: nothing provides rpm-build
nothing provides gcc-PIE
That's because openSUSE:Leap:15.0:Ports/ports is pointing to openSUSE:Leap:15.0/ports (which has no route to the standard repository), instead of openSUSE:Leap:15.0/standard.
I don't understand. Who should change what then?
The project maintainer.
can the _project maintainer_ please do that? Packman no longer builds as a result; all packages in the Essential and Multimedia projects with architecture x86_64 are in state "unresolvable". Thx, cheers. l8er manfred
participants (4)
-
Andreas Schwab -
Manfred Hollstein -
Olaf Hering -
Oliver Kurz