On Thu, Aug 24, 2006 at 11:11:30AM +0200, Peter Palfrader wrote: > mtr in sarge eats 100% CPU when called with -n (don't resolve IP > addresses to hostnames). It turns out there is a small bug in > select.c's select_loop() that causes select to always be called with a > timeout of 0. > > Is this something that should and could be fixed for the next stable > point release?
Quoting from http://release.debian.org/stable/3.1/3.1r2/: ---------------- The regulations for updates to the stable Debian release are quite conservative. The requirements for packages to get updated in stable are: 1. The package fixes a security problem. An advisory by our own Security Team is required. Updates need to be approved by the Security Team. 2. The package fixes a critical bug which can lead to data loss, data corruption, or an overly broken system, or the package is broken or not usable (anymore). 3. The stable version of the package is not installable at all due to broken or unmet dependencies or broken installation scripts. 4. All released architectures have to be in sync. 5. The package gets all released architectures back in sync. It is (or (and (or 1 2 3) 4) 5) Regular bugs and upgrade problems don't get fixed in new revisions for the stable distribution. They should instead be documented in the Release Notes which are maintained by Rob Bradford <mailto:[EMAIL PROTECTED]> and are found at http://www.debian.org/releases/sarge/releasenotes ---------------- Would you prefer the security advisory approach or the release notes approach? -- Robert Woodcock - [EMAIL PROTECTED] "That's nice, honey. Can you pick up some milk on your way home?" -- Diane Brown to Mike Brown, upon hearing that 2003 UB313, an object Mike discovered, is bigger than Pluto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
