Bug 967885
Summary: | yum load-transaction gives rpmdb ver mismatch loading saved transaction | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Sullivan <jsrhbz> |
Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | admiller, ffesti, firas.alkafri, jzeleny, packaging-team-maint, tim.lauridsen |
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: | 2014-02-05 21:34:45 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
John Sullivan
2013-05-28 13:36:15 UTC
# head -1 /tmp/yum_save_tx.2013-05-28.13-19.vw37ZA.yumtx 4780:5cb6f321e48eedf4001cf3e121a7cdaa762e74cd That string comes from ...site_packages/yum/__init__.py, via save_ts/load_ts: $ python Python 2.7.3 (default, Aug 9 2012, 17:23:57) [GCC 4.7.1 20120720 (Red Hat 4.7.1-5)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import yum >>> i = yum.YumBase() >>> j = i.rpmdb.simpleVersion(main_only=True) Loaded plugins: auto-update-debuginfo, fastestmirror, presto, priorities, : refresh-packagekit >>> print j ['4780:39e2d558f43a947cec2004d8a706d492358a51d8', {}] >>> load_ts requires that the current value of simpleVersion[0] matches the value retrieved when save_ts was called. What is that hash value and when does it change? On any rpm operation? If so, it seems that fixing a dep problem (usually by removing conflicting packages, as in this case) must *guarantee* that the load check will fail, which doesn't sound too useful. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |