[Rpm-maint] [rpm-software-management/rpm] [RFE] Make RPM transaction more robust (Discussion #2193)

[Jaroslav Mracek]

Time to time we get reports related to the broken system. There is a wide range of reasons why it happens - power outage, packaging, issue in DNF or RPM, restarting critical processes and killing rpm (scriptlets, logout, ...), broken scriptlets and so on. The problem is that there is not an easy way how to restore the system into the original state.

People are supposed to do snapshots before (each?) transaction but it cost something or run system in console and not in desktop terminal but it is not the default behavior of the deployed system or something that is recommended by guidelines. May be it is a time to move the current status to provide a support of automation that will help to resolve such a problem automatically. Specially desktop users know such a functionality from Windows.

>From DNF side we can detect unfinished transaction and propose to redo of such a transaction. We can remove all artifacts, finish unfinished steps and redo all finished steps to ensure all scriptlets were correctly performed, but it will not help with any transaction performed outside of DNF or performed directly by RPM. If recovery support will be somehow supported directly in RPM it would be better for more player.

May by it would be good to ask a question what is required to allow transactional behavior for operation with RPMs (keep changes only when all requested operation succeed).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2193
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/2193 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220916/e0d6168d/attachment.html>