I’m reluctant to add more than a final line, to the effect “reverting to stable requires intervention at CLI”
From a tactical perspective, the wiki states that testing is for power users and such people are likely to have more than one IPFire installation, but it would be prudent to keep at least one at stable branch, resulting in infrequent need to revert.
From a technical perspective, 100% reverstion might not be possible, if an unstable branch has changed config files or added/replaced files and/or procedures. Some other Linux distributions can successfully revert, but only by maintaining complete snapshots of previous versions.
This continues showing until you run pakfire to re-upgrade the system to stable.
Hmm. I’m just trying to get this straight in my head.
So if I am on Testing (or Unstable) how do I get to the new Core Update? If Unstable is moved to Testing (and is released on the blog), and then is promoted from Testing to Stable, will I see an update on the Pakfire page?
Maybe instead of seeing Pakfire is working … when moving branches backwards there should be a screen that states “Unable to …”.
Yes, to reinstall an update, this is the way to go. It is not elegant and I have a ticket to create a simple command for that, but I am just too busy with many other things and did not think of this as the biggest priority.