Hi, Can you run "zypper refresh"? Are you using download.opensuse.org? If not, the mirrors need to catch up still. Ciao, Marcus On Mon, Mar 25, 2019 at 12:07:29PM +0100, Hans-Peter Jansen wrote:
Dear Marcus,
On Samstag, 23. März 2019 21:08:03 Marcus Meissner wrote:
Hi,
The repository has been restored (a snapshot was available Friday afternoon, and we switched back to live data just some hours ago.
It's still broken. In an attempt to upgrade my wife's 42.3 system to 15.0 yesterday evening, it revealed its full scope.
The usual way of sed'ing the repos and zypper dup'ing resulted in:
Retrieving package apparmor-docs-2.12-lp150.6.6.1.noarch (93/3093), 306.0 KiB (353.0 KiB unpacked) Retrieving: apparmor-docs-2.12-lp150.6.6.1.noarch.rpm ..............................................[done (283.8 KiB/s)]
Warning: Digest verification failed for file 'apparmor-docs-2.12- lp150.6.6.1.noarch.rpm' [/var/adm/mount/AP_0xITdps1/noarch/apparmor-docs-2.12-lp150.6.6.1.noarch.rpm]
expected 607e9527fc21811b82da32adfc70b654fe4157ae58b7a3ca6e5458c08b7fe1b8 but got 9a9f16c0db35e8936dcd087019ab9bcb5de92c3f66dec43ebfe262c60671e003
Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.
However if you made certain that the file with checksum '9a9f..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file.
Unblock or discard? [9a9f/...? shows all options] (discard):
Next, I attempted to upgrade the old, lame way (usb stick, DVD version). Again, it raised the very same issue as above. Duh.
When comparing the meta data of this package with a properly installed one, it didn't show any difference. Since I know, that rpm, as used from openSUSE, is integrity checked, the problem must be located in the update repo setup.
And because I have backups, I forced the installation anyway. I had to confirm installation of about 2/3 of all updated packages, since the "No show this again" in YaST didn't work as expected. No fun.
I would declare 15.0 not installable as such, at least not with the default settings of updating right away.
Looks, like it needs a plain createrepo run (not an update run).
Cheers, Pete
--
Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real