Description of problem: Old version of dnf (as well as yum) used to support: dnf --disablerepo=* --enablerepo=somerepo clean all To clean a single repository's files/caches, etc. Current version ignores these options a wipe everything. Version-Release number of selected component (if applicable): dnf-1.1.8-1 How reproducible: Always Steps to Reproduce: 1. dnf --disablerepo=* --enablerepo=updates clean all 2. dnf update Actual results: Fedora 23 - x86_64 203 kB/s | 43 MB 03:36 Fedora 23 - x86_64 - Updates 775 kB/s | 21 MB 00:28 (the fedora repository is reloaded: 3m30 and 43Mb lost) Expected results: Fedora 23 - x86_64 - Updates 775 kB/s | 21 MB 00:28 (only the update repository gets refreshed).
Yep, it's the new feature. See bug 1278225.
Thanks for the reply. Although I understand the bug 1278225 is a reason for change, I rather consider this as a "lack of feature". Can't we imagine to revert to the previous behavior if --disablerepo and/or --enablerepo are specified as command argument ? This will be a precious feature back. Thanks for considering it.
Maybe there's something to be said for it when "clean all", but it seems hard to justify this for "clean metadata" and other more specific forms of clean, the ones that explicitly aren't "all".
*** Bug 1423399 has been marked as a duplicate of this bug. ***
Michael, please describe how this is related to bug 1278225, thanks. This is serious regression; I used this feature on daily basis (unless I did it a bad way). Also, do we have a work-around for use-case described in duplicate bug 1423399? Can I adjust somehow 'metadata_expire' argument for one repository only (without touching the yum config file)? Thanks.
(In reply to Pavel Raiskup from comment #5) > Michael, please describe how this is related to bug 1278225, thanks. This > is serious regression; I used this feature on daily basis (unless I did it > a bad way). In bug 1278225 we intentionally changed clean command to erase cache for all repos. This bug complains about new behaviour. So its related. > Also, do we have a work-around for use-case described in duplicate bug > 1423399? Can I adjust somehow 'metadata_expire' argument for one > repository only (without touching the yum config file)? Thanks. dnf --setopt=myreponame.metadata_expire=1
Sounds like working way around, so it works for me, thanks! Using together with --enable/disable-repo should be almost equivalent. I.e., is this really doing 'clean all' for 'myreponame'?
We might consider adding another option to trigger theold "clean all" behavior.
> We might consider adding another option to trigger theold "clean all" behavior. +1 In addition, this should not be limited to "all".
PR: https://github.com/rpm-software-management/dnf/pull/921
This bug is currently reported against a Fedora version which is already unsuported. I am changing the version to '27', the latest supported release. Please check whether this bug is still an issue on the '27' release. If you find this bug not being applicable on this release, please close it.
IF you are going to ignore --{enable,disable}-repo, there should at least be a warning to that effect...
The best would be to have something like: dnf clean metadata --only-repo=myrepo
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.