[rb-general] Bug#862073: Uploading buildinfo files to buildinfo.debian.net

[Vagrant Cascadian]

On 2019-02-16, Mattia Rizzolo wrote:
> On Fri, Feb 15, 2019 at 01:51:40PM -0800, Vagrant Cascadian wrote:
>> There are a few individual developers uploading unsigned .buildinfo
>> files, as well as a few buildds for non-release architectures
>> (e.g. hurd-i386, kfreebsd-*). To hadle those, I actually had a
>> legitimate use for the technique described in:
>> 
>>   https://xkcd.com/1181/
>
> Do you think you could provide more info about the kbsd and hurd
> buildinfo that are unsigned?

Looks like kfreebsd were fixed at some point.

I'm not sure what more information is needed ... the .buildinfo files
available on coccia are unsigned. The only current ones still failing
are hurd-i386 or the infrequent developer uploads, for example:

NOSIGNATURE: ['/srv/ftp-master.debian.org/buildinfo/2019/02/16/gcc-9_9-20190215-1_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/acl_2.2.52-5_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/attr_2.4.47-4_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/usepackage_1.13-4_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/libocas_0.97+dfsg-5_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/lxqt-metapackages_28_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/ocaml-mm_0.4.0-1_hurd-i386.buildinfo',
'/srv/ftp-master.debian.org/buildinfo/2019/02/16/postfix_3.3.2-2_amd64.buildinfo']

I've privately emailed some of the individual developer uploads when
I've noticed, but haven't done a systematic look. Maybe it's time to do that.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20190216/b3d6a59a/attachment.sig>