[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#847726: marked as done (unblock node-normalize-path 2.0.1-2)

Your message dated Sun, 11 Dec 2016 17:17:54 +0530
with message-id <78d8db43-aed8-2504-06fd-5d7f6d8c7938@debian.org>
and subject line Re: Bug#847726: unblock node-normalize-path 2.0.1-2
has caused the Debian Bug report #847726,
regarding unblock node-normalize-path 2.0.1-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
847726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847726
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
package: release.debian.org

Fixes RC bug #846743 (causes gitlab to be marked for autoremoval)

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
On ഞായര്‍ 11 ഡിസംബര്‍ 2016 05:09 വൈകു, Adam D. Barratt wrote:
> 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.

Like I said before, I was under the impression that all RC bugs qualify
for unblock requests. Since FTBFS is not severe, withdrawing unblock request

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: