Hello Daniel, I expected to hear this. And I know the policy. And I will not start discussion of the policy.
Nevertheless it's a little bit sad, as apt/aptitude is kind of debians figurehead. And a broken man page may be confusing/unsettling to debian novices. And fixing a man page error won't break stableness of etch. But as stated, I will not start discussion of policy and accept I have to wait for Lenny to get the fix (as on my servers I do not accept target mixtures). But thanks for reply. Regards Gert From: Daniel Burrows [mailto:[EMAIL PROTECTED] Sent: Freitag, 30. November 2007 06:14 To: Buchsbaum, Gert; [EMAIL PROTECTED] Subject: Re: Bug#438725: aptitude man page display garbage escape sequences On Thu, Nov 29, 2007 at 07:31:31AM +0100, [EMAIL PROTECTED] was heard to say: > Daniel Leidert <[EMAIL PROTECTED]> wrote: > > > This issue has already been reported, explained and fixed in > > testing/unstable. I don't know, if this issue can be fixed in stable > (a > > simple rebuild would do, because stable does not contain the 1.72 > > version of docbook-xsl). > > Yes, this error is known since march, 2007. And fixed, too. But not > publish as announced. It was. See the message you quote below. > See bug #415468: > ... > >From: Daniel Burrows <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Bug#415468: fixed in aptitude 0.4.4-5~1 > >Date: Wed, 16 May 2007 04:47:03 +0000 > >Source: aptitude > >Source-Version: 0.4.4-5~1 > > >We believe that the bug you reported is fixed in the latest version of > >aptitude, which is due to be installed in the Debian FTP archive: > ... The bug was fixed in 0.4.4-5~1, which was installed in the Debian FTP archive as stated. It is no longer there because it has been superceded by newer releases (the latest is 0.4.9-2). > I know this is a minor bug, but it's annoying. > > So I'm curious to learn why it is not installed in regular archives as > announced so anyone can get it using "aptitude upgrade"? Because the policy of the release managers is to only accept fixes for security holes and severe bugs into the stable release. I was going to point you at a Web page that explains this, but apparently there isn't one that's up-to-date (you can find an old version of the release policy at http://release.debian.org). Daniel
