* Philipp Kern ([EMAIL PROTECTED]) [080226 11:28]: > On Mon, Feb 25, 2008 at 09:39:37PM +0100, Patrick Winnertz wrote: > > Mh... I doubt that there is a chance to get this fix into stable... I've > > cc'ed Martin Zobel Helas as Stable Release manager, to get his option > > about this. > > I don't think that there is a real chance on this, at least at this > point. It does not apply to Etch only, it is still lacking a concrete > solution, having been reproduced in unstable, and as there > is no patch attached to the bug report the cause looks unknown to me, > too. > > We won't integrate a new upstream (pre-)release just for this.
Well, it basically depends on the bug fix. If there would be an obvious 1-line-patch, I think chances are pretty good to get that fixed in Etch (because it really is a quite frustrating bug). If it requires the next new upstream version, then not. So, the answer is: If there is a minimal clean low-risk patch, we can review it and make a decision. Until then, of course the default answer "no" applies. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
