You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Group transactions: fail on missing non-optional packages
If any default or mandatory package listed in a group does not
exist, `raise dnf.exceptions.MarkingErrors`.
This is a small change with a big impact and a lot of history.
In the early days, dnf treated both 'package doesn't exist'
and 'package exists but is not installable' as fatal errors.
Shortly after Fedora and RHEL switched from yum to dnf, this was
changed, because historically yum had not behaved this way, and
our existing comps definitions had lots of missing packages;
conditional and arch-specific comps entries also were not
properly handled by all tools, so cleaning up comps was not
possible.
dnf was switched for a while to treat neither as fatal, which
turned out to be too permissive, so eventually we gave it the
same behaviour yum used to have, in #1038.
These days, conditional and arch-specific comps entries work. I
have just cleaned up Fedora's comps file for Rawhide, so there
should be no 'missing' mandatory or default packages in any
group: https://pagure.io/fedora-comps/pull-request/767
I don't know if RHEL's or CentOS's comps have been cleaned up,
but if not, this presents an excellent opportunity to do it.
Links to the history here:
https://bugzilla.redhat.com/show_bug.cgi?id=1292892https://bugzilla.redhat.com/show_bug.cgi?id=1427365https://bugzilla.redhat.com/show_bug.cgi?id=1461539#1038
Signed-off-by: Adam Williamson <awilliam@redhat.com>
0 commit comments