Commits on Sep 12, 2023

1. Allow obsoletion of protected packages …

   This is the libdnf5 companion to
   rpm-software-management/libdnf#1610; if we
   change DNF 4, then we should also change DNF 5.
   
   There should be some mechanism for replacing even protected packages,
   e.g. to upgrade DNF to DNF 5. We unprotected dnf to allow this upgrade,
   but that solution isn't perfect; DNF 5 should be able to remove
   python3-dnf[1] and DNF 4 should not be able to remove DNF without
   installing DNF 5. @m-blaha proposed "implementing a hard-coded
   self-protection for each package manager", i.e. adding back the
   hardcoded protection of dnf and python3-dnf in DNF 4 and adding a
   protection of dnf5 in DNF 5. So if we want to do this, it seems we would
   need to allow obsoletion of protected packages to allow DNF 4 to
   obsolete dnf with dnf5.
   
   The running kernel is treated as a special case; obsoletes of the
   running kernel are still not allowed.

   

   evan-goode committed Sep 12, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 799cc1c
   • Browse repository at this point

   Copy the full SHA

   799cc1c View commit details

   Browse the repository at this point in the history