Bug 986237
Summary: | downloading the updates repo hangs and errors out recently | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ales Kozumplik <akozumpl> |
Component: | librepo | Assignee: | Tomas Mlcoch <tmlcoch> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | gbcox, jzeleny, tmlcoch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-17 09:46:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ales Kozumplik
2013-07-19 09:50:17 UTC
*** Bug 986419 has been marked as a duplicate of this bug. *** Hi, I cannot reproduce the issue. I've tried: * librepo v0.0.4 from f19 * librepo v0.0.5 from rawhide * librepo HEAD from the git No success. I suspect that the cause could be a badly synchronized mirror and the "Bad checksum" error was legitimate. What do to if this happens next time: In current released versions of Librepo, there is no easy way to get detailed (debug) output. So the best what you can do is the report the issue to me (add comment to this bug, open the new one, ping me on irc, email, etc). In the next version of librepo (probably the 0.0.6) there will be a detailed error messages + simple way to set a own debug handler to catch all librepo debug messages. Closing this bug, because it was related to an ancient version of librepo. Currently there is librepo 1.5.0 in f20 and 1.0.0 in f19. This new versions have a much better error reporting capabilities and fixed a lot of, most likely, related bugs. |