Updating and rolling back changes
Package-based systems, regardless of the package system (RPM, DNF, APT, Zypper, etc.) can have issues and artifacts when either moving to a newer version of their operating system or during an attempt to roll back installations that produce unintended consequences. If you have ever experienced this, you know exactly what I mean and I offer my condolences. For those of you who have been blessed or simply lucky enough to not have suffered a failed package update process, here’s the difference.
Package-based systems are forced to do their dependency checks in real time when they process their updates. What this process amounts to is some packages may be added or deprecated that you might not even be aware of during the process. Not only can it be clunky and obtuse, but it consumes significant time. Hopefully, you tested this process for each release ad nauseum before presenting updates to your customers. Sometimes, oftentimes, multiple reboots...
