Bug 1484017 - [modularity] Upgrading a module should directly install that modules dependencies
Summary: [modularity] Upgrading a module should directly install that modules dependen...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1478068
TreeView+ depends on / blocked
 
Reported: 2017-08-22 13:14 UTC by James Antill
Modified: 2018-11-22 18:27 UTC (History)
8 users (show)

Fixed In Version: dnf-4.0.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-22 18:27:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1484014 0 high CLOSED [modularity] Installing a module should directly install that modules dependencies 2021-02-22 00:41:40 UTC

Internal Links: 1484014

Description James Antill 2017-08-22 13:14:56 UTC 
When upgrading a module FOO that has _new_ dependencies on module BAR, dnf should mark the module BAR as installed.

There was some talk of this happening by having the depsolver mark rpms from module BAR to be installed, and then working back from that to mark BAR as an install (due to the rpms being installed from it). However I'm not sure this is enough for el8 (Eg. compat. repos.)
Comment 1 Daniel Mach 2018-04-16 12:08:57 UTC 
The DNF team will look into this issue probably after mid-May
where initial modularity enablements in libdnf are finished.
We'll need a proper dependency resolution to fully support this feature.
Comment 2 Martin Hatina 2018-07-25 13:02:32 UTC 
Module BAR will be enabled. Fixed in https://github.com/rpm-software-management/dnf/pull/1144
Note You need to log in before you can comment on or make changes to this bug.