[opensuse-packaging] Corruption in openSUSE update repositories, how to report?
Hi all, This is probably not quite the right place to ask, but I could find no list closer to the subject at hand. Sorry about that. I am regularly running into corruption within the openSUSE update repositories, i.e. the collections of files as downloadable from mirrors throughout the world. Every once in a while, the information listed in the metadata files (as in 'repodata/...-primary.xml' or 'repodata/...-deltainfo.xml') mismatches the characteristics of the downloadable RPMs. For some items, the metadata says the SHA1 hash of the RPM should be X, whereas the actual value of the downloadable file turns out to be Y. Everywhere, on all mirrors. To whom do I report this kind of problem? Aside from finding the root cause of the issue (which so far is occurring only with 11.2, not with 11.1 or 11.3, and most often with delta RPMs), it would be nice to have a way of getting detected occurrences 'flushed' from all mirrors. Something quicker, that is, than just waiting for the packages to get updated once more. Best regards, Remco de Vreugd. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Wednesday 29 September 2010 schrieb Remco de Vreugd:
Hi all,
This is probably not quite the right place to ask, but I could find no list closer to the subject at hand. Sorry about that.
I am regularly running into corruption within the openSUSE update repositories, i.e. the collections of files as downloadable from mirrors throughout the world. Every once in a while, the information listed in the metadata files (as in 'repodata/...-primary.xml' or 'repodata/...-deltainfo.xml') mismatches the characteristics of the downloadable RPMs. For some items, the metadata says the SHA1 hash of the RPM should be X, whereas the actual value of the downloadable file turns out to be Y. Everywhere, on all mirrors.
To whom do I report this kind of problem? Aside from finding the root cause of the issue (which so far is occurring only with 11.2, not with 11.1 or 11.3, and most often with delta RPMs), it would be nice to have a way of getting detected occurrences 'flushed' from all mirrors. Something quicker, that is, than just waiting for the packages to get updated once more.
Do you download directly from mirrors or do you use download.opensuse.org? And the best way to report it is usually bugzilla.novell.com and putting maintenance@opensuse.org in CC. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2010/09/30 at 09:40 CEST, Stephan Kulow wrote:
I am regularly running into corruption within the openSUSE update repositories, i.e. the collections of files as downloadable from mirrors throughout the world.
Do you download directly from mirrors or do you use download.opensuse.org?
I used to routinely start at download.opensuse.org, but that mostly redirects to the mirrors. Nowadays I don't even bother and pick a local mirror that I know to be reliable and fast. And if I do run into mismatches of secure hashes, I branch out to alternative mirrors. If there is way to circumvent the redirection process and download specifically from *the* source, even at (for example) a much lower speed, that would be nice to know. It would remove another step from the troubleshooting process.
And the best way to report it is usually bugzilla.novell.com and putting maintenance@opensuse.org in CC.
Ah, okay. I had expected bugzilla to be focusing on problems with(in) the product rather than its distribution. But I'll give it a try. Thanks for the pointer. Regards, Remco. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Remco de Vreugd -
Stephan Kulow