Description of problem: Same as yum is capable of. many thanks, L. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hello, could you please be more precise on your request? The options --enable/--set-enable and --disable/--set-disable for config-manager are currently implemented. If this was not what you asked please, update with more info. Thank you.
Hi. Yes, further down the cmd line args. With 'yum' we could, maybe still can, do: yum-config-manager --disable one,two,three\* (those ',' give a nice one-liner(s)) regards,L.
PR: https://github.com/rpm-software-management/dnf-plugins-core/pull/397 test: https://github.com/rpm-software-management/ci-dnf-stack/pull/828 note: it is already possible to run dnf config-manager --enable repo1 repo2 now dnf config-manager --enable repo1, repo2 works too
And I wonder when would that trickle down to what is in OSes' repos? This does not do anything: $ dnf config-manager --disablerepo PowerTools,Stream-PowerTools --save nor this: $ dnf config-manager --disablerepo PowerTools Stream-PowerTools --save and this: $ dnf config-manager --set-disabled PowerTools,Stream-PowerTools --save Error: No matching repo to modify: PowerTools,Stream-PowerTools. That is with version 4.2.17 which in that respect feels bit messy.
FEDORA-2020-b40fc174b5 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b40fc174b5
FEDORA-2020-5d9f0ce2b3 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5d9f0ce2b3
FEDORA-2020-b40fc174b5 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b40fc174b5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b40fc174b5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-5d9f0ce2b3 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-5d9f0ce2b3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5d9f0ce2b3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-5d9f0ce2b3 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
@lejeczek > And I wonder when would that trickle down to what is in OSes' repos? This bug is for Fedora. To request backporting this to CentOS Stream, please open a new bugzilla against the "CentOS Stream" version of the "Red Hat Enterprise 8" product, as described in the FAQ [0]. I agree that it would be a good feature, but it's not up to me. > This does not do anything: > > $ dnf config-manager --disablerepo PowerTools,Stream-PowerTools --save > nor this: > $ dnf config-manager --disablerepo PowerTools Stream-PowerTools --save Those commands don't do anything because `--disablerepo` is a top level dnf flag that temporarily disables a repo for the duration of the transaction [1]. Combining it with the `--save` flag has no effect. It is not the same as the config-manager plugin `--disable` flag [2]. That flag does accept a space separated list of repos, or being passed multiple times. dnf config-manager --disable PowerTools Stream-PowerTools dnf config-manager --disable PowerTools --disable Stream-PowerTools [0] https://wiki.centos.org/FAQ/CentOSStream#Where_do_I_report_bugs.3F [1] https://www.mankier.com/8/dnf#--disablerepo [2] https://www.mankier.com/8/dnf-config-manager#--disable
FEDORA-2020-b40fc174b5 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.