Description of problem: # cat /etc/yum.repos.d/bz1151154repo* [bz1151154repoA] name=My Local Repo bz1151154repoA baseurl=file:///tmp/tmp.7fxA6gpJvW/bz1151154repoA/ enabled=0 gpgcheck=0 [bz1151154repoB] name=My Local Repo bz1151154repoB baseurl=file:///tmp/tmp.7fxA6gpJvW/bz1151154repoB/ enabled=0 gpgcheck=0 # yum-config-manager --enable Updating Subscription Management repositories. Unable to read consumer identity This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Error: Trying to enable already enabled repos. # cat /etc/yum.repos.d/bz1151154repo* [bz1151154repoA] name=My Local Repo bz1151154repoA baseurl=file:///tmp/tmp.kESYbvMVMs/bz1151154repoA/ enabled=0 gpgcheck=0 [bz1151154repoB] name=My Local Repo bz1151154repoB baseurl=file:///tmp/tmp.kESYbvMVMs/bz1151154repoB/ enabled=0 gpgcheck=0 # rpm -q dnf-utils dnf-utils-4.0.2.2-3.el8.noarch
Karel, can you please clarify, what did you mean by "ambiguous" in the summary? I think the message is not ambiguous, but plainly wrong, because dnf is not trying to enable any repository. If the above is correct, I propose the following acceptance criteria: AC: "yum-config-manager --enable" without arguments outputs the same as "yum-config-manager --disable", i.e. empty stderr and stdout.
Hi, I was complaining on the message "Error: Trying to enable already enabled repos." while not having any repository enabled. How much is running "yum-config-manager --enable" correct? You AC is probably sane assuming the RFE 1706384 won't be implemented.
> I was complaining on the message "Error: Trying to enable already enabled repos." while not having any repository enabled. All right, thanks. > How much is running "yum-config-manager --enable" correct? The old yum-config-manager exited with 0 when run with "--enable" without other arguments, so I wouldn't change that.
PR: https://github.com/rpm-software-management/dnf-plugins-core/pull/377 Tests: https://github.com/rpm-software-management/ci-dnf-stack/pull/749
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1823