Online upgrade Leap 15.3
Hi, just a sidenote for those who test online-upgrade: you need to run zypper dup --allow-vendor-change as the vendor of all packages changes: openSUSE --> SUSE LLC https://www.suse.com/ (Not sure I like this....) Cheers Axel
On 04/03/2021 20.12, Axel Braun wrote:
as the vendor of all packages changes: openSUSE --> SUSE LLC https://www.suse.com/
all packages? Sure, for the core SLE packages this is the way it has to be, because we are re-using binaries. I checked https://build.opensuse.org/package/binaries/openSUSE:Backports:SLE-15-SP3/to... and it has Vendor : openSUSE Distribution: SUSE Linux Enterprise 15 SP3 A better upgrade method may be zypper dup --no-allow-vendor-change --force-resolution That should auto-allow vendor-changes only when necessary.
Hello team, yast (and I believe also zypper) migration already treats both vendors the same. With zypper Bernhards recommendation seems to be the same. If you have some recommendations let's capture them here https://en.opensuse.org/SDB:System_upgrade On Fri, 2021-03-05 at 05:36 +0100, Bernhard M. Wiedemann wrote:
On 04/03/2021 20.12, Axel Braun wrote:
as the vendor of all packages changes: openSUSE --> SUSE LLC https://www.suse.com/
all packages?
Sure, for the core SLE packages this is the way it has to be, because we are re-using binaries.
I checked https://build.opensuse.org/package/binaries/openSUSE:Backports:SLE-15-SP3/to...
and it has
Vendor : openSUSE Distribution: SUSE Linux Enterprise 15 SP3
A better upgrade method may be zypper dup --no-allow-vendor-change --force-resolution
That should auto-allow vendor-changes only when necessary.
-- Best regards 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
Am Freitag, 5. März 2021, 05:36:04 CET schrieb Bernhard M. Wiedemann:
On 04/03/2021 20.12, Axel Braun wrote:
as the vendor of all packages changes: openSUSE --> SUSE LLC https://www.suse.com/
all packages?
Nearly: 1586 out of 1831
Sure, for the core SLE packages this is the way it has to be, because we are re-using binaries.
...
A better upgrade method may be zypper dup --no-allow-vendor-change --force-resolution
That should auto-allow vendor-changes only when necessary.
It seems to give the same result as --allow-vendor-change Best, Axel
On Fri, 05 Mar 2021 12:31:20 +0100 Axel Braun wrote:
Am Freitag, 5. März 2021, 05:36:04 CET schrieb Bernhard M. Wiedemann:
On 04/03/2021 20.12, Axel Braun wrote:
as the vendor of all packages changes: openSUSE --> SUSE LLC https://www.suse.com/
...
A better upgrade method may be zypper dup --no-allow-vendor-change --force-resolution
That should auto-allow vendor-changes only when necessary.
It seems to give the same result as --allow-vendor-change
I did an upgrade beginning of February, zypper asked about vendor change for as it seemed each package, so I created an /etc/zypp/vendors.d/suse.conf $ cat /etc/zypp/vendors.d/suse.conf [main] vendors = suse,opensuse,obs://build.suse.de ###### Also there exists a bug for this behavior #1182629 in Status: RESOLVED FIXED, so maybe for the next upgrade this is not needed anymore. BTW: did you get warnings about package signatures caused by missing keys? Regards, Dieter
On Fri, 05 Mar 2021, 13:42:28 +0100, dieter wrote:
[...] BTW: did you get warnings about package signatures caused by missing keys?
Yes! First I thought they might come from SLE packages, but I'd say "mpv" is not exactly such a package: warning: /var/cache/zypp/packages/oss.obs/x86_64/mpv-0.32.0+git.20200301T004003.e7bab0025f-bp153.1.31.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 65176565: NOKEY Looking the the package itself then hoever reveals, that it actually comes from SLE, though: $ rpm -qi mpv Name : mpv Version : 0.32.0+git.20200301T004003.e7bab0025f Release : bp153.1.31 ... Distribution: SUSE Linux Enterprise 15 SP3 I *guess* the SLE based gpg-pubkeys are either not on the installation media, or they don't get installed by a "zypper dup" - which ought to be fixed!
Regards, Dieter
Cheers. l8er manfred
Am Freitag, 5. März 2021, 13:42:28 CET schrieb dieter: ....
###### Also there exists a bug for this behavior #1182629 in Status: RESOLVED FIXED, so maybe for the next upgrade this is not needed anymore.
until then I have reopened the bug
BTW: did you get warnings about package signatures caused by missing keys?
No.... Cheers Axel
Am Freitag, 5. März 2021, 14:10:19 CET schrieb Axel Braun:
###### Also there exists a bug for this behavior #1182629 in Status: RESOLVED FIXED, so maybe for the next upgrade this is not needed anymore.
until then I have reopened the bug
looks like this is fixed in libzypp-17.25.8. But current Leap has only libzypp-17.25.6, thats the problem.... So either one upgrades libzypp first, or waits for the maintenance update to arrive
participants (5)
-
Axel Braun -
Bernhard M. Wiedemann -
dieter -
Lubos Kocman -
Manfred Hollstein