3 ms·
That does not sound like package system issue. Around 2003, Yum was a Python tool which took ages just to build dependency graph to do basic things.
by thriftwy 3y ago
That does not sound like package system issue.
Around 2003, Yum was a Python tool which took ages just to build dependency graph to do basic things.
- INTPenis 3y agoYes it was Python for a long time actually. And yet it still had very useful features like rollback and history. Things large government contracts kinda required.
- jacquesm 3y agoThey don't require it at the OS level though, contracts like that require it on the state of the system as a whole and the typical way to deal with this is by using versioned backups and audit trails.
- curt15 3y ago>And yet it still had very useful features like rollback and history. yum/dnf rollback is unreliable even today because the previously installed versions of packages might no longer be present in the repos.
- dralley 3y agoOld versions are cached on your system for a few days, and most distros do keep a few old versions around just in case.
- BossingAround 3y agoI use Fedora as my daily driver for work and DNF rollback might as well not exist. It's atrocious. Even when turning on the local repo cache function (which keeps RPM packages on your system for some time in case you want to roll back), I have never been able to successfully roll back an upgrade that contained more than ~10-20 packages. I love Fedora, but DNF has atrocious UX.
- INTPenis 3y agoThat's mostly true for Fedora, because it's a fast rolling release they don't keep old packages around. It's not true for RHEL who strive to maintain backwards compatibility and stability.