Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1666871 - libmodulemd should ignore defaults for modules with defaults conflicts
Summary: libmodulemd should ignore defaults for modules with defaults conflicts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libmodulemd
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Stephen Gallagher
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1656019
TreeView+ depends on / blocked
 
Reported: 2019-01-16 19:59 UTC by Petr Šabata
Modified: 2019-06-14 00:47 UTC (History)
3 users (show)

Fixed In Version: libmodulemd-2.0.0-5.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 00:47:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Šabata 2019-01-16 19:59:52 UTC 
Today libmodulemd throws an error when it encounters a module defaults conflict it cannot resolve, for instance if two repositories with the same priority contain modulemd-defaults with identical version yet different content.

This results in a DNF error the user cannot effectively do anything about besides disabling one of the repositories.  We decided to change the behavior to ignore the conflict instead, and report a warning.

This affects the available package set but has no impact on users already consuming the content and having a stream enabled.  Users can also still pick a stream manually.

Extra notes:

* QE tests might need to be updated.

* Since this changes the available package set, ursine packages that depend on packages provided by the affected module will not be installable until the situation is resolved.
Note You need to log in before you can comment on or make changes to this bug.