Hi, I’ve been using openSUSE Tumbleweed for about a year or so, and love it.
I refresh & download the packages daily with the following commands:
sudo zypper ref
sudo zypper dup -d
Then, when I want to actually install the updates a week or two later, I simply do the following:
sudo zypper dup
Recently, each time I download (dup -d), I’ve been getting the below error. I select [discard] then [ignore] for dup -d to download all the other packages. But this error isn’t going away:
Warning: Digest verification failed for file 'qemu-ipxe-1.0.0+-2.1.noarch.rpm'
[/var/tmp/AP_0x2N1Ebe/noarch/qemu-ipxe-1.0.0+-2.1.noarch.rpm]
expected 431bb3fefe4893ddc6f3425321.....
but got 7c6bafd38382bf6d8e8c35d54b.....
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 '7c6b..' 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? [7c6b/...? shows all options] (discard):
I thought these packages in question would eventually update on the server and fix itself, but it still hasn’t. It’s been 2 weeks or so.
The packages with the checksum problem include:
qemu-ipxe-1.0.0±2.1.noarch.rpm
qemu-seabios-1.16.2_3_gd478f380-2.1.noarch.rpm
qemu-vgabios-1.16.2_3_gd478f380-2.1.noarch.rpm
I had been thinking of changing mirrors, but having a quick read, it’s not appear to be that straight forwards. I believe you have to go into Yast Software Repository and manually change the url of each repo, or do it via the /etc files. So, I’d rather stay with the same mirror (I think). Thanks.
Have you tried removing the pre-downloaded file and letting it download again?
What’s the output of zypper lr -d? Sounds like you maybe have a lot of repos, so it would be useful to (a) verify what they are, and (b) determine which repo it is that these files are coming from.
Thanks, I’ve just tried the rpm rebuild and the problem persists.
I’m thinking I may have to give in and accept the new package with the different checksum, and hope my system doesn’t get compromised. But I’ll try a few more things first, before giving in…
(according to the error message, I could just give in…)
Hi Guys, this issue resolved itself. I simply waited (for a several weeks) and the mirror/server must have been eventually updated finally with the correct packages checksums.
I wonder why this even happens. Shouldn’t packages transferred to a mirror be done in a single atomic operation? If one (or more packages) fail, then rollback the entire transfer process, then try again.