On Thu, 2006-02-16 at 23:27 +0100, Christian Recktenwald wrote: > On Thu, Feb 16, 2006 at 11:19:22AM -0800, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > > #352321: gzip: problem described in Bug#310329 unfixed for sarge, > > which was filed against the gzip package. > > I really do not understand which is the problem with fixing a broken > packet. "Sorry" just sounds like "none of my business" which is > clearly not what one should expect from a debian package maintainer.
The package *is* fixed, which I think you already know because you made reference to the original bug report when you filed this duplicate! A quick look at the Debian package database shows version 1.3.5-10sarge1 in stable, and 1.3.5-12 in both unstable and testing. The fix for this was implemented in 1.3.5-11. There is no way to turn the clock backwards, and the Debian definition of "stable" is that we won't change the bits after a release unless there is a security problem. Since this is clearly not a security problem, this update won't be part of 'stable' until the next stable release, which will be the etch version. I hope that clarifies the situation for you? If you want this bug fixed on your system(s), install a newer version of this package than the one that is in stable. If you want to run only stable on your systems, then you will have to live with this bug until the next stable release. That's just how Debian works. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
