Bug 1278225
| Summary: | erase all the cache regardless --releasever specified | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John C. Beima <jbeima> |
| Component: | dnf | Assignee: | rpm-software-management |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 24 | CC: | jbeima, jmracek, mluscon, packaging-team-maint, ttomecek, vmukhame |
| Target Milestone: | --- | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-31 15:59:12 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 C. Beima
2015-11-05 01:05:00 UTC
In my case, in order to get the dnf system-upgrade to work, I had to do the following to clear the package dependency error out: 1. cd /var/cache/dnf 2. rm -rf * 3. dnf update 4. dnf system-upgrade download --releasever=23 --best 5. dnf system-upgrade reboot After cleaning out the cache manually/forcefully the upgrade performed. The "clean all" parameter simply needs to be aware of the repositories the plugins create. tip: you can use these steps for upgrade where the new metadata are requested: * dnf upgrade * dnf system-upgrade download --releasever=23 --refresh * dnf system-upgrade reboot Jan: I did not try the "--refresh", since I was unaware that it existed. However a "clean all" should clean all no matter what. :) Just my humble opinion. Jan the problem was also in the Fedora 23 cache not the update cache. Since once I physically erased the contents of the dnf cache directory the upgrade proceeded. I know it was Fedora, since when I was checking dnf was re-downloading the upgrade repo, and keeping the orginal Fedora repo. If that helps at all. I think we have 2 seperate bugs here. First clean all does not clean all when repos are created by system-upgrade. Second system-upgrade should erase all caches when the --releasever is used. Two seperate issues... *** Bug 1253806 has been marked as a duplicate of this bug. *** This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. Not sure why this was closed, since it exists in all versions of Fedora, it is simply being ignored as opposed to being addressed. :) Leaving it for over a year, because it has a lower priority doesn't fix it. :) I cannot reproduce the problem with dnf-2.2.0_1-3g33c95a8.fc25.noarch. Please can you try to reproduce your problem with dnf-2.0? It was released for fc26 and rawhide, but we provide the test repository for Fedora 24 and later versions. |