Re: Patches that break stuff
On Fri, 2004-07-09 at 10:55 -0400, Noah Meyerhans wrote: > On Fri, Jul 09, 2004 at 10:53:01AM -0400, Robert Brockway wrote: > > Are any hard stats available on how many Debian package upgrades have had > > to be replaced because they broke something? I'm thinking the total number of > > broken updates in 2.2 and 3.0 is 0 plus or minus 1 :) > > It's definitely greater than 0. In recent memory (earlier this year), > we released a kernel image package that didn't contain any modules. > Naturally it was fixed quickly, but I'm sure it lead to at least a > couple of unbootable systems. Check through the DSA advisories for revisions like -2/-3 etc. Some of the updates did not fix the bug in the initial release, eg: DSA 460-2. I have never had a problem with a broken DSA update though. The problem with 479-1 would have been a problem for some people however. -- David Stanaway <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Patches that break stuff
On Fri, Jul 09, 2004 at 10:53:01AM -0400, Robert Brockway wrote: > Are any hard stats available on how many Debian package upgrades have had > to be replaced because they broke something? I'm thinking the total number of > broken updates in 2.2 and 3.0 is 0 plus or minus 1 :) It's definitely greater than 0. In recent memory (earlier this year), we released a kernel image package that didn't contain any modules. Naturally it was fixed quickly, but I'm sure it lead to at least a couple of unbootable systems. I think there were probably a couple other issues, but I don't know off the top of my head. noah pgpwnJakjRnun.pgp Description: PGP signature
Patches that break stuff
Hi all. I think this is on-topic for the security list since all Stable package updates I see are security related. On Bugtraq the issue of patches breaking various parts of an OS has been raised (under the thread "Microsoft and Security"). It has been noted by one participant that his company assessed how often patches had to be replaced because their were broken in some way. They came to the figure of 1 in 6 patches needed replacing. In a private email the poster reported: 1. All vendors were within 3% of this figure. He advises they did lump all Linux distros together. 2. Cisco was lowest and Microsoft was average. I've found Debian puts all other "vendors" to shame when it comes to stability of updates to the Stable branch. Are any hard stats available on how many Debian package upgrades have had to be replaced because they broke something? I'm thinking the total number of broken updates in 2.2 and 3.0 is 0 plus or minus 1 :) Rob -- Robert Brockway B.Sc. email: [EMAIL PROTECTED], [EMAIL PROTECTED] Linux counter project ID #16440 (http://counter.li.org) "The earth is but one country and mankind its citizens" -Baha'u'llah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]