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

[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)

[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)

[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)

[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)

[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)

[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

[arch-dev-public] Signoff report for [testing]

[Arch Website Notification]

=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/

There are currently:
* 0 new packages in last 24 hours
* 2 known bad packages
* 0 packages not accepting signoffs
* 16 fully signed off packages
* 86 packages missing signoffs
* 64 packages older than 14 days

(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)



== Incomplete signoffs for [core] (12 total) ==

* elfutils-0.168-1 (i686)
0/1 signoffs
* gmp-6.1.2-1 (i686)
0/1 signoffs
* libgpg-error-1.26-1 (i686)
0/1 signoffs
* linux-4.9-1 (i686)
0/1 signoffs
* nano-2.7.3-1 (i686)
0/1 signoffs
* xz-5.2.3-1 (i686)
0/1 signoffs
* bzip2-1.0.6-6 (x86_64)
0/2 signoffs
* elfutils-0.168-1 (x86_64)
0/2 signoffs
* gmp-6.1.2-1 (x86_64)
1/2 signoffs
* libgpg-error-1.26-1 (x86_64)
0/2 signoffs
* nano-2.7.3-1 (x86_64)
0/2 signoffs
* xz-5.2.3-1 (x86_64)
0/2 signoffs

== Incomplete signoffs for [extra] (74 total) ==

* calligra-meta-3.0-2 (any)
0/2 signoffs
* opencl-headers-2:2.1.20161129-2 (any)
1/2 signoffs
* python-astroid-1.4.9-1 (any)
0/2 signoffs
* abiword-3.0.2-4 (i686)
0/1 signoffs
* ardour-5.4-2 (i686)
0/1 signoffs
* calligra-3.0.0-4 (i686)
0/1 signoffs
* gimp-2.8.18-4 (i686)
0/1 signoffs
* graphicsmagick-1.3.25-4 (i686)
0/1 signoffs
* imagemagick-6.9.7.0-2 (i686)
0/1 signoffs
* libbluray-0.9.3.r84.05c9fdec-1 (i686)
0/1 signoffs
* libwmf-0.2.8.4-14 (i686)
0/1 signoffs
* linux-zen-4.9-1 (i686)
0/1 signoffs
* lmdb-0.9.19-1 (i686)
0/1 signoffs
* lv2-1.14.0-2 (i686)
0/1 signoffs
* nghttp2-1.18.0-1 (i686)
0/1 signoffs
* nvidia-375.26-2 (i686)
0/1 signoffs
* nvidia-340xx-340.101-5 (i686)
0/1 signoffs
* nvidia-lts-375.20-2 (i686)
0/1 signoffs
* php-7.1.0-2 (i686)
0/1 signoffs
* php-apcu-5.1.7-2 (i686)
0/1 signoffs
* php-apcu-bc-1.0.3-2 (i686)
0/1 signoffs
* xf86-input-elographics-1.4.1-7 (i686)
0/1 signoffs
* xf86-input-evdev-2.10.4-2 (i686)
0/1 signoffs
* xf86-input-keyboard-1.9.0-2 (i686)
0/1 signoffs
* xf86-input-libinput-0.23.0-1 (i686)
0/1 signoffs
* xf86-input-mouse-1.9.2-3 (i686)
0/1 signoffs
* xf86-input-synaptics-1.9.0-1 (i686)
0/1 signoffs
* xf86-input-vmmouse-13.1.0-3 (i686)
0/1 signoffs
* xf86-input-void-1.4.1-3 (i686)
0/1 signoffs
* xf86-input-wacom-0.34.0-1 (i686)
0/1 signoffs
* xf86-video-amdgpu-1.2.0-2 (i686)
0/1 signoffs
* xf86-video-ati-1:7.8.99.r13.g404c6475-1 (i686)
0/1 signoffs
* xf86-video-dummy-0.3.8-1 (i686)
0/1 signoffs
* xf86-video-fbdev-0.4.4-6 (i686)
0/1 signoffs
* xf86-video-intel-1:2.99.917+746+g169c74f-2 (i686)
0/1 signoffs
* xf86-video-nouveau-1.0.13-2 (i686)
0/1 signoffs
* xf86-video-openchrome-0.5.0-2 (i686)
0/1 signoffs
* xf86-video-sisusb-0.9.6-8 (i686)
0/1 signoffs
* xf86-video-vesa-2.3.4-3 (i686)
0/1 signoffs
* xf86-video-vmware-13.2.1-2 (i686)
0/1 signoffs
* xf86-video-voodoo-1.2.5-8 (i686)
0/1 signoffs
* abiword-3.0.2-4 (x86_64)
0/2 signoffs
* ardour-5.4-2 (x86_64)
0/2 signoffs
* calligra-3.0.0-4 (x86_64)
0/2 signoffs
* gimp-2.8.18-4 (x86_64)
0/2 signoffs
* graphicsmagick-1.3.25-4 (x86_64)
0/2 signoffs
* imagemagick-6.9.7.0-2 (x86_64)
0/2 signoffs
* libbluray-0.9.3.r84.05c9fdec-1 (x86_64)
0/2 signoffs
* libwmf-0.2.8.4-14 (x86_64)
0/2 signoffs
* linux-zen-4.9-1 (x86_64)
1/2 signoffs
* lmdb-0.9.19-1 (x86_64)
0/2 signoffs
* lv2-1.14.0-2 (x86_64)
0/2 signoffs
* nghttp2-1.18.0-1 (x86_64)
0/2 signoffs
* nvidia-375.26-2 (x86_64)
0/2 signoffs
* nvidia-340xx-340.101-5 (x86_64)
0/2 signoffs
* nvidia-lts-375.20-2 (x86_64)
0/2 signoffs
* php-apcu-5.1.7-2 (x86_64)
1/2 signoffs
* php-apcu-bc-1.0.3-2 (x86_64)
1/2 signoffs
* xf86-input-elographics-1.4.1-7 (x86_64)
0/2 signoffs
* xf86-input-keyboard-1.9.0-2 (x86_64)
1/2 signoffs
* xf86-input-mouse-1.9.2-3 (x86_64)
1/2 signoffs
* xf86-input-synaptics-1.9.0-1 (x86_64)
1/2 signoffs
* xf86-input-vmmouse-13.1.0-3 (x86_64)
0/2 signoffs
* xf86-input-void-1.4.1-3 (x86_64)
0/2 signoffs
* xf86-input-wacom-0.34.0-1 (x86_64)
0/2 signoffs
* xf86-video-amdgpu-1.2.0-2 (x86_64)
0/2 signoffs
* xf86-video-dummy-0.3.8-1 (x86_64)
0/2 signoffs
* xf86-video-fbdev-0.4.4-6 (x86_64)
0/2 signoffs
* xf86-video-nouveau-1.0.13-2 (x86_64)
1/2 signoffs
* xf86-video-openchrome-0.5.0-2 (x86_64)
0/2 signoffs
* xf86-video-sisusb-0.9.6-8 (x86_64)
0/2 signoffs
* xf86-video-vesa-2.3.4-3 (x86_64)
1/2 signoffs
* xf86-video-vmware-13.2.1-2 (x86_64)
0/2 signoffs
* xf86-video-voodoo-1.2.5-8 (x86_64)
0/2 signoffs


== Completed signoffs (16 total) ==

* linux-firmware-20161222.4b9559f-2 (any)
* bzip2-1.0.6-6 (i686)
* dhcpcd-6.11.5-1 (i686)
* perl-5.24.0-3 (i686)
* sudo-1.8.19.p1-1 (i686)
* util-linux-2.29-1 (i686)
*