4 ms·
I've had Arch on 3 servers for 5-6 years also and only had a couple of incidents where Arch updates messed things up. But one of those was a big compatibility
by zimpenfish 5y ago
I've had Arch on 3 servers for 5-6 years also and only had a couple of incidents where Arch updates messed things up.
But one of those was a big compatibility breaking one that I hadn't done the prep for (because I'd missed the whole lead up for various reasons and was months late on the update anyway) and I still can't really explain the other.
Compared to Debian which I managed to break many times in the same time frame...
- pizza234 5y ago> Compared to Debian which I managed to break many times in the same time frame... How did you exactly break Debian multiple times? I've read about people doing crazy stuff, like replacing the default compiler entirely (rather than setting an alternative one) or forcing apt to install incompatible packages... and then complaining that the distribution is not stable. Non-rolling distros are very very conservative with package upgrades, and they don't "just break", as little changes over a given version.
- sudosysgen 5y agoGenerally Debian breaks come from a mission critical software that isn't really available and requires package updates beyond what your version does or from trying to force an update. Also twice dpkg just shat the bed for no reason, but that was 7 and 8 years ago.
- zimpenfish 5y ago> How did you exactly break Debian multiple times? Alas, I can't remember exactly what happened but it was the late 1990s/early 2000s - no crazy stuff involved, just things getting confused / crashing whilst doing updates and leaving things half-arsed and broken.
- beermonster 5y agoBack in those days it wasn’t unheard of. Good ol’ dselect!