image description:
two soyjaks superimposed on a terminal screen, pointing towards the terminal output that reads the following:
91 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
N: Repository ‘http://deb.debian.org/debian bookworm InRelease’ changed its ‘Version’ value from ‘12.4’ to ‘12.5’
Eh, updates still break things on Debian just like on Arch. It may happen less often but when you do run into problems, you’re completely screwed. I updated to Debian 12 like a year ago and still haven’t fixed all the issues because it’s a server and reinstalling the entire OS is completely out of the question and a beyond reasonable amount of work. On Arch, stuff breaks more often but the saving grace is that everything breaks often enough that you can count on there being an up to date wiki page for whatever problems you run into. On Debian if something semi obscure breaks, that feature is gone for good if you hate format and reinstalls.
Tbf, I did eventually get everything except zoneminder (and the ability to automatically reconnect to wifi when it loses connection WITHOUT HUMAN INTERVENTION) working again on my Debian server but the fact is it 100% worked before the update.
https://wiki.debian.org/DontBreakDebian
Hmm there doesn’t seem to be a section for “how do I prevent zoneminder from getting fucked and when I spend a month fucking with source code, databases, permissions, config files and everything else I can possibly think of, I can finally get it to work except the android app can’t playback events but it works through browser and no one on the forums knows shit” but thanks.
I run two Debian servers since Debian 11, with unattended upgrades, never had anything break from that.
An update and a dist upgrade are two very different beasts. If anyone is advocating for unattended distribution upgrades they’re mad. Especially on a production server. That is something that needs planning and testing.