Dumping modulemd-defaults documents produces invalid data, using 'name' where 'module' should be instead. This results in broken defaults in the repodata in F28: # dnf update Last metadata expiration check: 0:21:03 ago on Mon 16 Apr 2018 02:15:28 PM CEST. ** Message: 14:36:31.667: Module name not specified ** Message: 14:36:31.667: Invalid [ModulemdDefaults] document [Module name not specified]. ** Message: 14:36:31.667: Invalid document [Module name not specified]. Skipping it. ** Message: 14:36:31.667: Module name not specified ** Message: 14:36:31.668: Invalid [ModulemdDefaults] document [Module name not specified]. ** Message: 14:36:31.668: Invalid document [Module name not specified]. Skipping it. ** Message: 14:36:31.668: Module name not specified ** Message: 14:36:31.668: Invalid [ModulemdDefaults] document [Module name not specified]. ** Message: 14:36:31.668: Invalid document [Module name not specified]. Skipping it. Dependencies resolved. (...) Reproducible with both 1.2.0 and 1.3.0. The fixed version will need to be deployed on Fedora composers to truly resolve this issue.
Proposed as a Blocker for 28-final by Fedora user sgallagh using the blocker tracking app because: This *loosely* violates "The installed system must be able to download and install updates with the default console package manager." What happens is that libmodulemd (in use by DNF) will ignore the offending defaults metadata and as a result, packages that should appear as available by default to DNF will instead be treated as only available as optional modules. Given that default enablement is a critical feature of Modularity (previously agreed by FESCo to be blocking for F28), I am proposing this for the same. Note that the bug has already been located and fixed upstream in libmodulemd and that an update is forthcoming.
libmodulemd-1.3.0-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-59d7f7af7d
libmodulemd-1.3.0-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-764f270b0e
libmodulemd-1.3.0-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0f04084368
libmodulemd-1.3.0-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-727698a797
Discussed during the 2018-04-16 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made as it violates the following blocker criteria: "accepted as a clear violation of the requirements for Modularity specified in https://bugzilla.redhat.com/show_bug.cgi?id=1537253#c6 , as FESCo has declared modularity blocking F28" [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2018-04-16/f28-blocker-review.2018-04-16-16.00.log.txt
libmodulemd-1.3.0-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1568277 has been marked as a duplicate of this bug. ***
libmodulemd-1.3.0-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
libmodulemd-1.3.0-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
libmodulemd-1.3.0-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.