Comments by "Gilad Barlev" (@GSBarlev) on "The Rise Of Auto Updating Package Managers" video.

Kind of a feature not a bug, IMO, as I'm of the belief that wipe-and-reloads are good for the soul. They also breed good practices like putting your OS files in a separate partition from your user configs, which should go in a separate partition from your actual data. Learned the hard way that borked upgrades happen, and they should never prevent you from getting access to your data.
6
Do you hold down the power button to turn it off? From my experiences (with VMs) it's usually on shutdown that Windows springs those automatic updates on me.
2
Maybe don't uninstall the old kernel until you've rebooted with the new one? That way you can still boot using the old kernel via GRUB. With Debian-based systems, it always keeps the old kernel around (and the old kernels in the GRUB menu) unless you run autoremove.
2
Isn't this why the needrestart package exists?
2
@bigpod You realize they already do, by and large, right? A package's installer isn't going to just call `sudo service sshd restart` because what if the system manages daemons directly using systemctl? Instead, there's going to be a section of the package manifest that says: "Post install, flag these services for restart: [list]"
2
lol, Arch doesn't even ship with networking by default—the chance of them ever shipping unattended upgrades pre-configured is precisely zero.
2
Have you considered Timeshift? Makes rollbacks a cinch. When I had a catastrophic upgrade, I grabbed my rescue ISO, chrooted into my system to grab the pacman log (to see what I installed last), then once I found the culprit, I restored my last backup and then excluded the bad package from my yay -Syu.
1
@JessicaFEREM Okay, cool, we're on the same page. I just mean that the problem with update-on-shutdown is that you don't find out if the update broke your setup until you start the system back up.
1
I have no problem with things breaking when I update—I chose to use Arch over Ubuntu—but things breaking because the system decided to update without asking me first is an entirely different matter, and it's one of the big reasons I haven't dailied Windows in 17 years.
1
@zvoidzy I have. But it led to me posting a bug report on the package's GitHub and getting some cool peeks behind the curtain at their development process, so I'm not complaining. It was also happy days when I got the notification that the bug was resolved and could celebrate by immediately -Syu'ing with no exclusions.
1
@bigpod Depending on the packaging system, the post-scripts are still semi-structured, though.
1
I have a Hugo-based blog that gets rebuilt through a GitHub Action. It always uses the latest versions of everything, and that's very much by choice. It's also nice, though, that a failed build will keep the content stale instead of taking down the site completely.
1