Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-17 Thread Allan McRae 
On 17/01/17 03:50, Giancarlo Razzolini wrote:
> Em janeiro 3, 2017 6:45 Giancarlo Razzolini escreveu:
>> Em janeiro 3, 2017 6:29 Allan McRae escreveu:

>>>
>>> I'm all for making declaration by lack of objection, but you should wait
>>> more than 16 hours.  Particularly at this time of year...
>>>
> 
> Can I now declare signoff reports dead, by lack of objection?
> 

Yes

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-16 Thread Giancarlo Razzolini 

Em janeiro 3, 2017 6:45 Giancarlo Razzolini escreveu:

Em janeiro 3, 2017 6:29 Allan McRae escreveu:




I'm all for making declaration by lack of objection, but you should wait
more than 16 hours.  Particularly at this time of year...



Can I now declare signoff reports dead, by lack of objection?

Cheers,
Giancarlo Razzolini


pgpgcO4vW9_E5.pgp
Description: PGP signature

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-03 Thread Giancarlo Razzolini 

Em janeiro 3, 2017 6:29 Allan McRae escreveu:




I'm all for making declaration by lack of objection, but you should wait
more than 16 hours.  Particularly at this time of year...

A



Sure. I will just not "migrate" them now.


pgptqfpj06FZ6.pgp
Description: PGP signature

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-03 Thread Lukas Jirkovsky via arch-dev-public 
On 2 January 2017 at 16:50, Giancarlo Razzolini
 wrote:
> Hi All,
>   Also, I have been pointed to this[0]. So, should we send signoff
>   reports somewhere else or, not at all?
>
> Cheers,
> Giancarlo Razzolini
>

Send them to /dev/null ;)

Lukas

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-03 Thread Allan McRae 
On 03/01/17 18:11, Giancarlo Razzolini wrote:
> Em janeiro 3, 2017 0:33 Sébastien Luttringer escreveu:
>>>
>> Please drop them.
>>
>> Cheers,
>>
> 
> By the action of inaction, they will not be sent anymore.
> 

I'm all for making declaration by lack of objection, but you should wait
more than 16 hours.  Particularly at this time of year...

A

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-03 Thread Giancarlo Razzolini 

Em janeiro 3, 2017 0:33 Sébastien Luttringer escreveu:



Please drop them.

Cheers,



By the action of inaction, they will not be sent anymore.

Cheers,
Giancarlo Razzolini

pgpIrXMPk4Otu.pgp
Description: PGP signature

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-02 Thread Sébastien Luttringer 
On Mon, 2017-01-02 at 15:50 +, Giancarlo Razzolini wrote:
> Hi All,
> 
>    With the recent archweb migration, some services stopped working.
>    We are just finishing migrating those services (and automating them
>    on ansible). One of these services is the signoff reports emails.
> 
>    For the past few days, the exact same e-mail was sent, from the old
>    setup, and nobody seem to have noticed. I guess most (all) filter
>    these emails out. Also, the service to populate the signoff's wasn't
>    running too, but this one will be kept running.
> 
>    Also, I have been pointed to this[0]. So, should we send signoff
>    reports somewhere else or, not at all?
> 
> Cheers,
> Giancarlo Razzolini
> 
Please drop them.

Cheers,

-- 
Sébastien "Seblu" Luttringer
https://seblu.net | Twitter: @seblu42
GPG: 0x2072D77A

signature.asc
Description: This is a digitally signed message part

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-02 Thread Sven-Hendrik Haase 
On Mon, Jan 2, 2017 at 4:54 PM, Angel Velásquez  wrote:
> On 2017-01-02 10:50 AM, Giancarlo Razzolini wrote:
>> Hi All,
>>
>>   With the recent archweb migration, some services stopped working.
>>   We are just finishing migrating those services (and automating them
>>   on ansible). One of these services is the signoff reports emails.
>>
>>   For the past few days, the exact same e-mail was sent, from the old
>>   setup, and nobody seem to have noticed. I guess most (all) filter
>>   these emails out. Also, the service to populate the signoff's wasn't
>>   running too, but this one will be kept running.
>>
>>   Also, I have been pointed to this[0]. So, should we send signoff
>>   reports somewhere else or, not at all?
>>
>> Cheers,
>> Giancarlo Razzolini
>>
>
> +1 to drop them

+1. Drop it.

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-02 Thread Angel Velásquez 
On 2017-01-02 10:50 AM, Giancarlo Razzolini wrote:
> Hi All,
> 
>   With the recent archweb migration, some services stopped working.
>   We are just finishing migrating those services (and automating them
>   on ansible). One of these services is the signoff reports emails.
> 
>   For the past few days, the exact same e-mail was sent, from the old
>   setup, and nobody seem to have noticed. I guess most (all) filter
>   these emails out. Also, the service to populate the signoff's wasn't
>   running too, but this one will be kept running.
> 
>   Also, I have been pointed to this[0]. So, should we send signoff
>   reports somewhere else or, not at all?
> 
> Cheers,
> Giancarlo Razzolini
> 

+1 to drop them

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-02 Thread Bartłomiej Piotrowski 
On 2017-01-02 16:51, Giancarlo Razzolini wrote:
> Em janeiro 2, 2017 13:50 Giancarlo Razzolini escreveu:
>>
>>Also, I have been pointed to this[0]. So, should we send signoff
>>reports somewhere else or, not at all?
>>
> 
> This: https://bugs.archlinux.org/task/50866?project=1=3335

+1 to dropping it. I never paid any attention to it and check archweb
instead before moving any packages from testing.

Bartłomiej



signature.asc
Description: OpenPGP digital signature

Re: [arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-02 Thread Giancarlo Razzolini 

Em janeiro 2, 2017 13:50 Giancarlo Razzolini escreveu:


   Also, I have been pointed to this[0]. So, should we send signoff
   reports somewhere else or, not at all?



This: https://bugs.archlinux.org/task/50866?project=1=3335


pgpoMI84OEjzv.pgp
Description: PGP signature

[arch-dev-public] [RFC] Send signoff reports somewhere else (or not at all)

2017-01-02 Thread Giancarlo Razzolini 

Hi All,

  With the recent archweb migration, some services stopped working.
  We are just finishing migrating those services (and automating them
  on ansible). One of these services is the signoff reports emails.

  For the past few days, the exact same e-mail was sent, from the old
  setup, and nobody seem to have noticed. I guess most (all) filter
  these emails out. Also, the service to populate the signoff's wasn't
  running too, but this one will be kept running.

  Also, I have been pointed to this[0]. So, should we send signoff
  reports somewhere else or, not at all?

Cheers,
Giancarlo Razzolini



pgp8zGj_tXmtC.pgp
Description: PGP signature