Hi, On Sat, Apr 02, 2016 at 05:33:52AM +0200, Adam Borowski wrote: > > (Also for fixing this in stable it needs to be fixed / not be present in > > unstable first.) > Why?
because that's the usual policy for fixing issues in stable, which was
also confirmed for this particular issue by a SRM on #debian-release
today.
> [...] it looks
> like removal is more likely to happen than forking, so the problem might
> be never fixed in unstable.
Removing the package from unstable will cause the bug not be present in
unstable so that's an ok solution from the POV of getting it fixed in
stable.
> The timebomb was introduced in 5.21, oldstable has 5.15, o-o-stable 5.11, so
> neither is affected.
Thanks for the clarification. (Also for checking when it will hit 5.34!)
--
cheers,
Holger
signature.asc
Description: Digital signature
