Packages from the epel-testing repository are unexpectedly being installed during routine upgrades on a Rocky Linux 9 production server. You must persistently disable this repository so that all future dnf transactions ignore it, but you also need to keep the .repo definition file on disk in case it has to be re-enabled later. Which single command accomplishes this task?
The command dnf config-manager --set-disabled epel-testing (provided by the dnf-plugins-core package) edits the epel-testing section of the corresponding .repo file and changes enabled=1 to enabled=0. Because the setting is written to disk, the repository remains disabled for every future dnf operation until it is explicitly re-enabled.
dnf --disablerepo=epel-testing upgrade disables the repository only for the current transaction; the next dnf command would use it again. dnf clean all --repo epel-testing merely removes cached metadata and packages but leaves the repository enabled. Deleting the file with rm /etc/yum.repos.d/epel-testing.repo would indeed stop the repository from being used, but it also removes its definition entirely, making future re-enablement harder and contravening the requirement to keep the file.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What does the `--set-disabled` option in `dnf config-manager` do?
Open an interactive chat with Bash
What is the difference between `--disablerepo` and `--set-disabled` in `dnf` commands?
Open an interactive chat with Bash
Why is it better to use `--set-disabled` instead of deleting the `.repo` file?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Services and User Management
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access