-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem "Digest verification failed" #473
Comments
I request a package from 'https://download.opensuse.org/tumbleweed/repo/oss/x86_64/libldap2-2.6.3-3.1.x86_64.rpm',
But these URLs are assigned, but their package signatures are incorrect
Why does "https://download.opensuse.org/tumbleweed/repo/oss/x86_64/libldap2-2.6.3-3.1.x86_64.rpm" redirect me to these 5 URLs with incorrect package signatures? Is SUSE still worthy of trust? |
It should be the problem.
|
You also hijacked bsc#120135, I tried to explain it there. In case of libldap2 (in the zypper.log snippnet) opensuse.koyanet.lv returned no_error but an empty file. Maybe you can provide the full zypper.log, so we can check the other checksum failures too. Might be some broken mirror. For some of the files above (checksum e3b0...b855; the sha256sum of an empty file) it appears the same has happened. A mirror delivered an empty file without an error. The other issues may be partial content, the mirror delivered without an error. Almost looks like the mirror is advertised and delivers files although his sync is not complete. |
|
Thanks for the log. I forward the result to our mirrorcache maintainer. All the broken checksum incidents in the log are caused by Strange is just that by now, you seem to be the only one with this kind of issue. As a workaround you can try and add those 2 lines to your /etc/hosts:
This should redirect requests to opensuse.koyanet.lv to your local host (where they should fail correctly). |
I'll check whether we can work around this in libzypp after vacation (Jan.9.) |
Every time I use "sudo zypper dup", I encounter the problem of "Warning: Digest verification failed"; Very annoying; How should I handle this problem?
The text was updated successfully, but these errors were encountered: