> The only exception to this rule is Abrowser, which is the only package in
Trisquel with a rolling release cycle.
Indeed, Abrowser now appears to be the main source of unexpected changes. The
default start page configuration keeps changing with new versions, usually at
the very moment
Thanks for the suggestion, this is certainly what I would do back in the
times when I used to install parallel beta versions of all the stuff you
mention, play with it, break it, restore it or fail to restore it, report
bugs, break the MBR, restore it, bring the laptop back to its owner and
Couldn't you do a full backup of the machine, then later restore from said
backup? Ideally backing up just before you 'sudo apt upgrade'
Personally 90+ percent of files that I wish to save, such as video or
pictures, I back up separately. Since those files have nothing to do with the
I see. Thank you very much for the detailed explanation.
I think I started keeping the security updates as the only enabled repository
when I noticed some unwanted changes on Gnome Video (Totem). Nothing major at
the time, I must admit, but still a useful option* which was removed. This
I think you are making this more complicated than it needs to be. Package
managers like Guix and Pacman have robust rollback capabilities because they
are designed for rolling distributions, in which a routine update is likely
to cause a regression. For a stable distribution you should be
Thanks, this confirms my doubts: there is no way to save the state of the
system and to unroll back to that state after upgrading. Thank you also for
hinting to the log files.
I am now a bit confused about the proper terminology, though. As mentioned
abobe, I was referring to the operation
I mean the state of the system as defined by the package versions, which is
what gets modified by an upgrade, I suppose.
What do you mean by "configuration"? An upgrade will never override user
configuration files in your home directory, and should only override
system-wide configuration files in /etc after asking you for confirmation.
Are you referring to something else?
I usually turn off non-security upgrades as soon as the current OS version
has reached its maturity, both in terms of how stable it has got and how used
to it I have grown, because unstable or unwanted behavior is most often not
easy to trace to individual upgrades.
Is there a way to store
