Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dnf config-manager--set-enabled #1840

Open
m-blaha opened this issue Nov 6, 2024 · 1 comment
Open

dnf config-manager--set-enabled #1840

m-blaha opened this issue Nov 6, 2024 · 1 comment

Comments

@m-blaha
Copy link
Member

m-blaha commented Nov 6, 2024

The CI on one of my projects got upgraded to dnf5, which broke it because dnf config-manager --set-enabled=$repo no longer works.

For reference, here's a github search for that invocation - excluding forks there's almost 5000 references to it on Github.

I don't think it makes sense for all of them to rewrite.

(Moved from rpm-software-management/dnf-plugins-core#565 dnf-plugins-core issue)

@carlwgeorge
Copy link

It looks like the design now is for config-manager to have proper subcommands, rather than subcommands masquerading as flags. For example, dnf config-manager --add-repo is now dnf config-manager addrepo. However, there isn't a subcommand for the old --set-enabled or --set-disabled flags. I did find a workaround using the setopt subcommand.

Instead of this dnf4 command:

dnf config-manager --set-enabled updates-testing

You can do this in dnf5:

dnf config-manager setopt updates-testing.enabled=1

I do agree that it would be nice to at least have setenabled and setdisabled subcommands for consistency and to be easier to remember.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants