Re: [opensuse-support] Re: openSUSE Tumbleweed installation blocked by "Wrong Digest" error
Warning: Digest verification failed for file 'susedata.xml.gz' [/var/tmp/AP_0xlApxLV/repodata/susedata.xml.gz]
And this is the problem, the file is bad
Yes, this appears to be the real problem. I checked that they haven't changed their repo signing key, as I have a backup copy of it and I checked it against the current one. Could it be that they signed `susedata.xml.gz` with the wrong key? I don't really understand PGP all that well... But the repo contents are indeed still downloadable if you know the exact path/name. For example: https://download.nvidia.com/opensuse/tumbleweed/repodata/susedata.xml.gz The problem is that Zypper won't accept it and it throws those scary errors.
and there is nothing we can do about it but report in bugzilla and wait.
Did anybody already file a bug? This started late last week, I believe on Friday. It feels like they made a late Friday mistake and then took the weekend off and haven't noticed the problem yet. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 01/09/2020 07.05, S. wrote:
Warning: Digest verification failed for file 'susedata.xml.gz' [/var/tmp/AP_0xlApxLV/repodata/susedata.xml.gz]
And this is the problem, the file is bad
Yes, this appears to be the real problem. I checked that they haven't changed their repo signing key, as I have a backup copy of it and I checked it against the current one. Could it be that they signed `susedata.xml.gz` with the wrong key? I don't really understand PGP all that well... But the repo contents are indeed still downloadable if you know the exact path/name. For example: https://download.nvidia.com/opensuse/tumbleweed/repodata/susedata.xml.gz The problem is that Zypper won't accept it and it throws those scary errors.
Maybe you can tell it to ignore, but if the world stops spinning don't look at me ;-)
and there is nothing we can do about it but report in bugzilla and wait.
Did anybody already file a bug? This started late last week, I believe on Friday. It feels like they made a late Friday mistake and then took the weekend off and haven't noticed the problem yet.
Just go ahead and report it. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
participants (2)
-
Carlos E. R. -
S.