|
Bugzilla – Full Text Bug Listing |
| Summary: | problems with source repo | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | Dmitry Mittov <mittov> |
| Component: | Download Infrastructure | Assignee: | Peter Poeml <poeml> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Adrian Schröter <adrian.schroeter> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | agemen, noloader |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dmitry Mittov
2009-04-23 17:04:44 UTC
Confirmed... # rpm --rebuilddb && zypper ref && zypper ref Repository 'openSUSE-11.1-Debug' is up to date. Repository 'openSUSE-11.1-Non-Oss' is up to date. Repository 'openSUSE-11.1-Oss' is up to date. Digest verification failed for packages.DU.gz. Expected c2c47b2bea12224005074a4a1dff2abb66ec28f0, found 0e90c879133dc4ac7b63acd021c0969cc24d00e6. Continue? If I try what you made i have : zypper ref repo-source Le dépôt 'openSUSE-11.1-Source' est à jour. Les dépôts spécifiés ont été rafraîchis. It's in french, sorry ^_^ but there isn't any problem, in fact. I've noticed a zypper update I didn't make, but i don't think it could be linked. I checked the repo was really refreshed, and it's ok. And what about this test? $ wget http://download.opensuse.org/source/distribution/11.1/repo/oss/content $ wget http://download.opensuse.org/source/distribution/11.1/repo/oss/suse/setup/descr/packages.DU.gz $ sha1sum packages.DU.gz 0e90c879133dc4ac7b63acd021c0969cc24d00e6 packages.DU.gz $ grep packages.DU.gz content META SHA1 c2c47b2bea12224005074a4a1dff2abb66ec28f0 packages.DU.gz We have the same results, so i think it's a problem of mirror. I think if MirrorBrain redirects to invalid mirror it is problem of repository. Thank you for the report. The same issue was reported as bug 500388 and just fixed. I'm resolving this bug as duplicate, therefore. The mirror had a copy that was outdated; since we didn't have a good way to pull the source tree at the time, they can't even be blamed for it. Meanwhile, the mirror has been updated. You should not see similar problems anymore; if you do, please let me know! Thanks. *** This bug has been marked as a duplicate of bug 500388 *** |