Christoph,
am Tue, Sep 01, 2009 at 09:38:18PM +0200 hast du folgendes geschrieben:
> However it's not a security problem and I don't believe it qualifies for
> a stable ("Lenny") update as specified in
> http://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
> as it's not a security-related issue nor makes pdns uninstallable on any
> architecture nor is "a truly critical functionality problem". I
> understand that it's annoying. But I'd rather say it's a "normal"
> problem as it doesn't destroy data and affects just part of pdns's
> functionality. If the release team can be convinced to accept an updated
> version for Lenny then I'll happily provide one though.
it looks to me that handing out false data to clients qualifies as breaking
functionality, although no private data is leaked.
> > The bug is a regression from etch and should be pushed to lenny updates.
> IMHO the bug is a problem in the 2.9.21 upstream release and not exactly
> the fault of the Debian package.
>
> What is the release team's opinion on that? Do we have a chance to get
> this into Lenny?
If the patch is accepted upstream (which you indicated), please backport
that fix to Lenny, yes. The dpatch I saw looked fairly small and
selfcontained.
Kind regards,
Philipp Kern
--
.''`. Philipp Kern Debian Developer
: :' : http://philkern.de Stable Release Manager
`. `' xmpp:phil@0x539.de Wanna-Build Admin
`- finger pkern/key@db.debian.org
Attachment:
signature.asc
Description: Digital signature