Learn more about these different git repos.
Other Git URLs
A proper fix is removing module builds whose modular YAML metadata contain a static_context field from the updates repository. This can be achieved in two ways:
(1) Revert the static_context changes in dist-git, rebuild the modules, push them into F33 stable repository after a week of "testing", then undo the reverts and build them for Fedora ≥ 34 only. (Fedora 34 is not affected.)
(2) Untag the modules from f33-modular-updates Koji tag and wait for a regular updates compose. (We do not plan updating the modules in Fedora 33, i.e. in next 2 months. And if there will be the need, we will do the reverts on a case-by-case basis.)
Provided it's 23 modules, I would prefer the second option (untaging).
There are few workarounds for the affected users like "dnf upgrade" before installing other packages, or disabling updates-modular repository until upgrading libmodulemd package.
I'm not sure whether this issue (cannot install until fully upgraded) is so serious to warrant this kind of action. Maybe the recommendation "upgrade first" is good enough. Opinions?
When do you need this? (YYYY/MM/DD) Before F33 EOL (2021-11?).
When is this no longer needed or useful? (YYYY/MM/DD) After F33 EOL.
If we cannot complete your request, what is the impact? Fresh F33 installation won't be able to install some packages.
Actually there is only perl and perl-bootstrap in F33. ("koji list-pkgs --tag f33-modular-updates" lies.) I can handle the two streams of the the modules myself with the first method (reverts and rebuilds).
Metadata Update from @ppisar: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.