On Fri, Apr 01, 2016 at 11:04:28PM -0400, Holger Levsen wrote: > On Sat, Apr 02, 2016 at 02:53:30AM +0000, Daniel Shahaf wrote: > > Control: notfound -1 5.34-1 > > the bug is present in that version. The timebomb just hasn't been triggered > yet.
For the record, the timebomb for 5.34 will go off on 2017-04-01, ie, shortly after stretch's expected release date. > (Also for fixing this in stable it needs to be fixed / not be present in > unstable first.) Why? The fix is a trivial technical matter (Daniel's one-line patch in the very first mail) and no one questions what to do for stable. It's the political issue in unstable what needs deliberation. And it looks like removal is more likely to happen than forking, so the problem might be never fixed in unstable. > and oldstable The timebomb was introduced in 5.21, oldstable has 5.15, o-o-stable 5.11, so neither is affected. -- A tit a day keeps the vet away.
