[Pkg-db-devel] Db4.2 patch query

[Lesley Walker]

Thanks very much for the clarification.

If I get to the point where I can demonstrate a specific problem arising
from the unpatched packages I will indeed file a bug a report, but on the
whole I think it's probably preferable to move towards adopting db4.4 in the
long run.

While I'm here, I'd like to say thanks to all involved for the work you do
maintaining packages. I'm sure it's mostly a thankless task so although I
haven't got a clue what you actually do, I do appreciate your doing it.

> -----Original Message-----
> From: Clint Adams [mailto:schizo at debian.org] 
> Sent: Thursday, 1 March 2007 3:16 p.m.
> To: Lesley Walker
> Cc: pkg-db-devel at lists.alioth.debian.org
> Subject: Re: [Pkg-db-devel] Db4.2 patch query
> 
> > Thanks for the quick answer!
> > 
> > Are you planning to incorporate the later ones at some stage?
> 
> As far as I am aware, there are no firm plans either way.  Chances of
> them getting into sarge are infinitesimal.  For etch, there is a
> possibility, at the discretion of the release managers, assuming
> release-critical bugs are filed.  For lenny, we will either drop db4.2
> entirely or apply the patches.
> 
> Please file bugs regarding the deficiencies that would be corrected
> by the application of the missing patches, if you wish to facilitate
> this process.
> 
> If you are unfamiliar with the bug reporting process, see
> http://www.debian.org/Bugs/Reporting
> 
> If you have a use case which exposes the data loss corrected by
> the patch, list it and set the severity according to
> http://www.debian.org/Bugs/Developer#severities
> 
> Hope this helps.
>