Description of problem: I'm throwing this out here as another thing that could be improved if modularity is to become a thing. I personally don't care, I just encountered this while testing for #1800528. $ podman run -ti fedora:32 /usr/bin/bash # dnf module enable --repo=fedora,updates-modular,fedora-modular maven Cannot enable more streams from module 'maven' at the same time Unable to resolve argument maven Error: Problems in request: broken groups or modules: maven # dnf module enable --repo=fedora,updates-modular,fedora-modular maven:3.5 (works) Version-Release number of selected component (if applicable): dnf-4.2.19-1.fc32.noarch Expected results: Something like "The maven module has more than one stream and no default stream. Specify a specific stream to enable as 'maven:3.5' or 'maven:3.5'." (IIUC, the world "default" is used to mean that the stream is default (i.e. enabled by default), the default stream (i.e. the one to be preferred if no stream is specified), and the default profile (in the stream). This overload makes it hard to form unambiguous sentences...)
Well the request will get more tricky, because dnf also accepts globs. It means that you can use maven:3* or m*:3*. But I will try to improve it. The problem is that dnf sees only arguments but don't know what user want, therefore more specific hints could be misleading.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
I created PR (https://github.com/rpm-software-management/dnf/pull/1700) that improve the message. I will be happy to for any feedback. It also requires test changes: https://github.com/rpm-software-management/ci-dnf-stack/pull/923 sudo dnf module enable maven Last metadata expiration check: 0:00:10 ago on Wed 09 Dec 2020 07:44:56 AM CET. Argument 'maven' matches 2 streams ('3.5', '3.6') of module 'maven', but non of streams is enabled or default Unable to resolve argument maven Error: Problems in request: broken groups or modules: maven
Looks reasonable... I made some comments on the PR.
FEDORA-2021-4935120076 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4935120076
FEDORA-2021-be78216a31 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-be78216a31
FEDORA-2021-be78216a31 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-be78216a31` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-be78216a31 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-4935120076 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4935120076` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4935120076 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-4935120076 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-be78216a31 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.