3 ms·
Debian, interestingly, has recently had a push exactly in the opposite direction, mainly for the "fixing bugs once fixes them everywhere" reason. Over the years
by _delirium 16y ago
Debian, interestingly, has recently had a push exactly in the opposite direction, mainly for the "fixing bugs once fixes them everywhere" reason. Over the years a lot of packages have for various reasons statically linked in private copies of a library (sometimes on purpose, sometimes just because upstream did so), which causes the Debian security team no end of headaches, because they have to track down all of these and fix them if there's a security-relevant bug. Since Debian Stable tries not to push too many updates unless absolutely necessary, it also screws things up there, because instead of updating one package for one library's bug, they have to update all N packages that made private copies of the library, so sysadmins expecting rare, infrequent security fixes instead get presented with a big pile of packages that want to be updated.
- angusgr 16y agoThis idea scares me a bit. Mostly for the rare awful occasions when people either rely on buggy behaviour, or patch around it on the caller side in some unexpected way. I can see it making perfect sense for security updates, but if you have it then you have it for all library updates - security or not.
- _delirium 16y agoYeah, though I think it's mitigated a little bit with a managed-as-a-whole system like Debian, at least if there's communication. Sometimes things break, but sometimes things do actually work, and the maintainers will talk to each other to coordinate updates, inform each other when a change is likely to break other things, etc.