Description of problem: when dnf cache is marked as expired via 'dnf clean expire-cache', 'dnf repolist' and 'dnf info' still use the expired cache (without any warning). Note: * yum behaviour in the same situation is different, after 'yum clean expire-cache' yum repolist and info subcommands refresh the yum cache * 'dnf repoquery' refreshes the dnf cache when it is marked as expired Version-Release number of selected component (if applicable): dnf-2.8.6-0.117g003e278b.fc26.noarch How reproducible: always Steps to Reproduce: 1. create a repo 2. run # dnf makecache # dnf repolist 3. change the repo content (e.g. remove a .rpm from it and run createrepo_c --update <repodir>) 4. run # dnf clean expire-cache # dnf repolist (the same steps for 'dnf info <the-removed-package>') Actual results: output of 'dnf repolist' is the same for steps 2. and 4. (for step 4. it is not up-to-date) Expected results: expired cache is not used or at least a warning is printed
I created a patch that should solve the issue (https://github.com/rpm-software-management/dnf/pull/1040).
Thanks for the patch. Now it seems that 'dnf repolist' reflects expire-cache, however, 'dnf info' still uses expired cache. Is this behaviour intended?
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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 this bug is closed as described in the policy above. 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.
To Comment 2, I think the behavior is intended.
The issue is solved by dnf-3.0.1-1 that was released into rawhide.