Bug#847726: unblock node-normalize-path 2.0.1-2
On Sun, 2016-12-11 at 16:55 +0530, Pirate Praveen wrote:
>
> On 2016, ഡിസംബർ 11 4:05:41 PM IST, "Adam D. Barratt" <adam@adam-barratt.org.uk> wrote:
> >On Sun, 2016-12-11 at 10:24 +0530, Pirate Praveen wrote:
> >> package: release.debian.org
> >
> >*Please* use the correct metadata here.
> >
> >> Fixes RC bug #846743 (causes gitlab to be marked for autoremoval)
> >
> >While this is true, the auto-removal date is in over a month from now.
> >On that basis, and given that the bug in node-normalize-path doesn't
> >affect use of the package in stretch, why should it not wait its full
> >10
> >days for migration?
>
> If FTBFS is not considered to be affecting the package, can I reduce the severity of that bug to normal?
Sigh. :-(
I didn't say it doesn't affect the package, and of course it's still RC.
What I said is it doesn't affect _use_ of the package. You're asking for
the migration time to be reduced, I'm asking for the rationale for that.
The fix for the FTBFS needs to be in stretch, we both agree on that. My
question is why it needs to be in stretch today rather than in two days
time when the 10 day counter is up.
Regards,
Adam
Reply to: