Re: Bug#855282: debsign: support .buildinfo files

2017-02-16 Thread Guillem Jover
Hi! On Thu, 2017-02-16 at 17:23:00 +, Ximin Luo wrote: > Control: tags + patch > I've done an initial implementation here: > > https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debsign-buildinfo > > Please review! I think something like the attached patch on top of

diffoscope is marked for autoremoval from testing

2017-02-16 Thread Debian testing autoremoval watch
diffoscope 67 is marked for autoremoval from testing on 2017-03-19 It is affected by these RC bugs: 854723: diffoscope: CVE-2017-0359: writes to arbitrary locations on disk based on the contents of an untrusted archive ___ Reproducible-builds mailing

reprotest is marked for autoremoval from testing

2017-02-16 Thread Debian testing autoremoval watch
reprotest 0.6 is marked for autoremoval from testing on 2017-03-19 It (build-)depends on packages with these RC bugs: 854723: diffoscope: CVE-2017-0359: writes to arbitrary locations on disk based on the contents of an untrusted archive ___

Re: New armhf node (Pine64+)

2017-02-16 Thread Holger Levsen
On Thu, Feb 16, 2017 at 12:25:15PM -0800, Vagrant Cascadian wrote: > Just purged the un-unsed kernel packages which didn't have support for > these boards. ah! > I guess you must have installed something that triggered > an "update-initramfs" call on the older kernel versions... I wonder what

Re: New armhf node (Pine64+)

2017-02-16 Thread Vagrant Cascadian
On 2017-02-16, Holger Levsen wrote: > On Mon, Feb 06, 2017 at 01:39:47PM -0800, Vagrant Cascadian wrote: > linux-image-4.10.0-rc6-arm64-unsigned (4.10~rc6-1~exp1) wird eingerichtet ... > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-4.10.0-rc6-arm64 > DTB:

Re: Bug#855282: debsign: support .buildinfo files

2017-02-16 Thread Ximin Luo
Control: tags + patch Hi all, I've done an initial implementation here: https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debsign-buildinfo Please review! I haven't yet updated debrsign but I think that program is a bit pointless anyway, and have documented this in

Re: New armhf node (Pine64+)

2017-02-16 Thread Holger Levsen
On Thu, Feb 16, 2017 at 01:31:55PM +, Holger Levsen wrote: > E: Sub-process /usr/bin/dpkg returned an error code (1) > Can you fix this up ("somehow" on the host…), please?! "fixed" this for now by adding "exit 0" at the beginning of /etc/initramfs/post-update.d//flash-kernel … -- cheers,

Re: Another new armhf node (Pine64+)

2017-02-16 Thread Holger Levsen
On Tue, Feb 14, 2017 at 03:52:06PM -0800, Vagrant Cascadian wrote: > Yet Another arm board ready to be configured for the build farm! set up as well. (I've only configured maintenance and setup jobs so far, but no builder jobs as p64b aint setup fully yet due to the linux-image install

Re: New armhf node (Pine64+)

2017-02-16 Thread Holger Levsen
Hi Vagrant, sorry for the delay in getting these boards used…! On Mon, Feb 06, 2017 at 01:39:47PM -0800, Vagrant Cascadian wrote: > Another arm board ready to be configured for the build farm! this is now basically setup, however this is quite annoying (as we expect "apt install" to exit 0…)

Re: Bug#855282: debsign: support .buildinfo files

2017-02-16 Thread Holger Levsen
user reproducible-builds@lists.alioth.debian.org usertag 855282 toolchain thanks -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org

Bug#855282: debsign: support .buildinfo files

2017-02-16 Thread Ximin Luo
Package: devscripts Version: 2.17.1 Severity: wishlist Dear Maintainer, dpkg since version 1.18.19 has been signing buildinfo files by default. debsign at the moment will ignore these and leave them unsigned. It would be good to support them. Ximin -- Package-specific info: ---

Bug#855273: diffoscope: still fails to clean up after SIGTERM

2017-02-16 Thread Ximin Luo
Mattia Rizzolo: > Package: diffoscope > Version: 77 > Severity: important > > So, yesterday we tried to re-enable artifacts saving on jenkins, and the > disc filled again because of GBs of temporary files left around. > > In a log the only message I see is: > > |Wed Feb 15 23:28:21 UTC 2017 I:

Bug#855273: diffoscope: still fails to clean up after SIGTERM

2017-02-16 Thread Mattia Rizzolo
Package: diffoscope Version: 77 Severity: important So, yesterday we tried to re-enable artifacts saving on jenkins, and the disc filled again because of GBs of temporary files left around. In a log the only message I see is: |Wed Feb 15 23:28:21 UTC 2017 I: diffoscope 77 will be used to