Stefan Held wrote:
but it is the most
obvious and adding a simple mechanism to yum to report the latest update
timestamp or some repo transaction id(s) that could be fed to another
instance to ensure it ignored subsequent changes to the repo(s) to
perform an update to the same packages would be useful in its own right
and appreciated when inherited by the enterprise versions.
What about an Dialog:
Dude, you try to run updates-testing, should we make a new lvm-snapshot
for /?
If then later something breaks one could easily reboot into a former
snapshot
</dream mode off>
I'm not sure how practical that would be unless you could still mount
and access the updated version after reverting. Suppose you've done
several days work before you trip over the showstopper bug that makes
you want to revert. Or the update makes format changes that aren't
backwards compatible in files on other partitions?
I'd go for an option to install a spare matching partition for the
system and have updates always rsync the previous to it before changing
anything (both partitions always mounted, no lvm magic) but even that
doesn't cover everything that can go wrong.
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
