Bug#847636: Re: unblock node-cpr

2016-12-17 Thread Julien Cristau 
On Sun, Dec 11, 2016 at 17:06:50 +0530, Pirate Praveen wrote:

> On ഞായര്‍ 11 ഡിസംബര്‍ 2016 04:59 വൈകു, Pirate Praveen wrote:
> > Like my previous reply. Won't FTBFS be considered as affecting the
> > package, then it needs to be documented.
> 
> The announcement said "Should your upload to unstable include security fixes 
> or fixes for severe bugs, we file an unblock bug asking for us to lower the 
> required age." I was under the impression that all RC bugs qualify. It would 
> have been better if it said (severity grave or critical then there wouldn't 
> have been any confusion).
> 
> 
As far as testing is concerned, that upload doesn't fix a RC bug there,
since the package, and thus the bug, is not in testing.

Cheers,
Julien

Bug#847636: Re: unblock node-cpr

2016-12-11 Thread Pirate Praveen 
On ഞായര്‍ 11 ഡിസംബര്‍ 2016 04:59 വൈകു, Pirate Praveen wrote:
> Like my previous reply. Won't FTBFS be considered as affecting the
> package, then it needs to be documented.

The announcement said "Should your upload to unstable include security fixes or 
fixes for severe bugs, we file an unblock bug asking for us to lower the 
required age." I was under the impression that all RC bugs qualify. It would 
have been better if it said (severity grave or critical then there wouldn't 
have been any confusion).




signature.asc
Description: OpenPGP digital signature

Bug#847636: Re: unblock node-cpr

2016-12-11 Thread Pirate Praveen 


On 2016, ഡിസംബർ 10 10:47:01 PM IST, "Adam D. Barratt" 
 wrote:
># bcc to control@
>user release.debian@packages.debian.org
>usertags 847636 + unblock
>tags 847636 + moreinfo
>
>On Sat, 2016-12-10 at 10:45 +0530, Pirate Praveen wrote:
>> package: release-debian.org
>
>Please either use reportbug or add the correct metadata yourself (and
>preferably use package names that exist :-p).
>
>> Fixes serious bug #846010 and #847614
>
>We're not frozen yet, so what you're asking for is for the upload to
>migrate to testing more quickly than the default 10 days.
>
>There is no node-cpr package in testing currently and, even if there
>were, neither of the cited bugs would affect the usability of the
>package there, so I'm not personally convinced that they merit a
>reduction in migration time.

Like my previous reply. Won't FTBFS be considered as affecting the package, 
then it needs to be documented.

>Regards,
>
>Adam

Processed (with 5 errors): Bug#847636: Re: unblock node-cpr

2016-12-10 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # bcc to control@
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 847636 + unblock
There were no usertags set.
Usertags are now: unblock.
> tags 847636 + moreinfo
Bug #847636 [release.debian.org] unblock node-cpr
Added tag(s) moreinfo.
> On Sat, 2016-12-10 at 10:45 +0530, Pirate Praveen wrote:
Unknown command or malformed arguments to command.
> > package: release-debian.org
Unknown command or malformed arguments to command.
> Please either use reportbug or add the correct metadata yourself (and
Unknown command or malformed arguments to command.
> preferably use package names that exist :-p).
Unknown command or malformed arguments to command.
> > Fixes serious bug #846010 and #847614
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
847636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847636: Re: unblock node-cpr

2016-12-10 Thread Adam D. Barratt 
# bcc to control@
user release.debian@packages.debian.org
usertags 847636 + unblock
tags 847636 + moreinfo

On Sat, 2016-12-10 at 10:45 +0530, Pirate Praveen wrote:
> package: release-debian.org

Please either use reportbug or add the correct metadata yourself (and
preferably use package names that exist :-p).

> Fixes serious bug #846010 and #847614

We're not frozen yet, so what you're asking for is for the upload to
migrate to testing more quickly than the default 10 days.

There is no node-cpr package in testing currently and, even if there
were, neither of the cited bugs would affect the usability of the
package there, so I'm not personally convinced that they merit a
reduction in migration time.

Regards,

Adam