Bug 1484017

Summary:	[modularity] Upgrading a module should directly install that modules dependencies
Product:	[Fedora] Fedora	Reporter:	James Antill <james.antill>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	dmach, hpopal, igulina, jmracek, nphilipp, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dnf-4.0.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-22 18:27:36 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:
Bug Depends On:
Bug Blocks:	1478068

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