Bug 1696204
Summary: | dnf should enable parent-required-modules if user specify exact module version to install. Or print missing installed modules. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Andrei Stepanov <astepano> |
Component: | dnf | Assignee: | Jaroslav Mracek <jmracek> |
Status: | CLOSED ERRATA | QA Contact: | Jan Blazek <jblazek> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 8.2 | CC: | amatej, james.antill, ppisar, psabata |
Target Milestone: | rc | Keywords: | FutureFeature, Reopened, Triaged |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | dnf-4.2.17-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:47:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrei Stepanov
2019-04-04 10:35:34 UTC
I investigated the issue, and I found that the problem is caused by preferring of a context using default stream. This is more restrictive behaviorDue to latest changes that should not allow stream switch I would not recommend to change the behavior. The issue could be resolved enabling perl:5.24 manually. Jaroslav, hi. I agree that "The issue could be resolved enabling perl:5.24 manually." But, problem is users doesn't know that he needs enable perl:5.24 manually. Or Perl:5.26 or perl:6.01 DNF doesn't give any clue/hint why it fails. There should be some meaningful info from DNF. something like: this NSVC has next requires: ------------------------ | | | # DEPENDENCY | | | | Modules to be enabled: | | | | * perl:5.24 | | * perl-DBI:1.641 | | | ------------------------ Otherwise: 1. user will blame DNF. 2. user mast manually inspect md file to figure out why it fails. Now DNF fails in very unfriendly manner. Hope for your understanding. We need an opinion about required behavior from Modularity team. I agree the current behavior is a consequence of the restrictive stream switching behavior and should be kept. However, I also agree DNF should provide some more information to guide the user in the right direction; even if just by saying that the required context is available but couldn't be installed because of unment module-level dependencies. Would that be possible? I enhanced the error message (see output bellow) - https://github.com/rpm-software-management/dnf/pull/1532. Please do you agree with proposed solution? # dnf module install perl-DBI:1.641:820190116185335:082fdf2f All matches for argument 'perl-DBI:1.641:820190116185335:082fdf2f' in module 'perl-DBI:1.641' are not active Error: Problems in request: broken groups or modules: perl-DBI:1.641:820190116185335:082fdf2f Jaroslav Mracek It looks match better now. Thank you. 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 |