In 26 years, I’ve seen this happen in two occasions with enterprise Linux. One of them was my own damned fault for using a marginal config. The other was an update that added a new dependency in the code but not the package.
Never had an unbootable system after an update, all not checking news has ever done to me is having a package fail to install (and then I check the news to see how to fix it), I’ve seen plenty of kernel regressions or other software, but that’s a thing with upstream and getting not-as-tested software, not with arch itself
Really? It happens this often?
In 26 years, I’ve seen this happen in two occasions with enterprise Linux. One of them was my own damned fault for using a marginal config. The other was an update that added a new dependency in the code but not the package.
That’s it. Twice.
Never had an unbootable system after an update, all not checking news has ever done to me is having a package fail to install (and then I check the news to see how to fix it), I’ve seen plenty of kernel regressions or other software, but that’s a thing with upstream and getting not-as-tested software, not with arch itself