On Wed, 29 Mar 2017 at 21:27:26 +1100, Dmitry Smirnov wrote:
> On Wednesday, 29 March 2017 8:42:38 AM AEDT Simon McVittie wrote:
> > Please ask the release team to remove it if that's the case.
>
> It is already scheduled for removal because of this bug's severity...
If you don't want it in stable, waiting for autoremoval leaves the bug
on the lists seen by people doing bug squashing (like me in this case),
whereas asking for it to be removed would take it off those lists sooner.
> > I've cancelled my delayed NMU.
>
> OK. So you've decided not to save the package for stable? Fair enough.
You said "I'd rather drop it from Stretch" which I thought meant you
specifically didn't want it to be saved, so I went along with what I
thought was your request as maintainer. Was that a misinterpretation?
I can NMU or not NMU, whichever you prefer; please let me know. You're also
welcome to apply the patch that I attached a couple of messages ago if you
want to do a MU.
I'm not going to upload a new upstream version or other larger changes,
because I don't think the release team are likely to accept an upload not
based on 3.7.2+repack during the freeze.
S
