Bug#994976: xtermcontrol: please make the build reproducible

On 2021-09-24, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0] we noticed that > xtermcontrol could not be built reproducibly. ... > --- a/debian/rules2021-09-24 09:20:53.800313098 +0100 > --- b/debian/rules2021-09-24 09:35:32.356026521 +0100 > @@ -5,9 +5,15 @@ >

Bug#1008569: unar: diff for NMU version 1.10.1-3

Hi all, 在 2022-04-29星期五的 08:20 +0200，Paul Gevers写道： > Dear Boyuan, > > On 25-04-2022 20:44, Sudip Mukherjee wrote: > > > +unar (1.10.1-3) unstable; urgency=medium > > > + > > > +  * QA upload. > > > +  * Orphan the package (take over package maintenance) via > > > +    ITS process. (Closes: #1008

snacc_1.3.1-9_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Apr 2022 18:33:59 -0700 Source: snacc Architecture: source Version: 1.3.1-9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1010379 Changes: snacc (1.

Processing of snacc_1.3.1-9_source.changes

snacc_1.3.1-9_source.changes uploaded successfully to localhost along with the files: snacc_1.3.1-9.dsc snacc_1.3.1-9.debian.tar.xz snacc_1.3.1-9_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1010379: marked as done (snacc: reproducible builds: timestamp embedded in header files)

Your message dated Sat, 30 Apr 2022 01:48:44 + with message-id and subject line Bug#1010379: fixed in snacc 1.3.1-9 has caused the Debian Bug report #1010379, regarding snacc: reproducible builds: timestamp embedded in header files to be marked as done. This means that you claim that the prob

Bug#1010379: snacc: reproducible builds: timestamp embedded in header files

Source: snacc Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Various header files embed the timestamp when it was generated in comments: https://tests.reproducible-builds.org/debian/rb-

leds-alix_0.0.1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Apr 2022 15:28:19 -0700 Source: leds-alix Architecture: source Version: 0.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Vagrant Cascadian Closes: 1010378 Changes: leds-

Processing of leds-alix_0.0.1-3_source.changes

leds-alix_0.0.1-3_source.changes uploaded successfully to localhost along with the files: leds-alix_0.0.1-3.dsc leds-alix_0.0.1-3.debian.tar.xz leds-alix_0.0.1-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1010378: marked as done (leds-alix: reproducible builds: source tarball embeds timestamps and umask)

Your message dated Fri, 29 Apr 2022 22:49:49 + with message-id and subject line Bug#1010378: fixed in leds-alix 0.0.1-3 has caused the Debian Bug report #1010378, regarding leds-alix: reproducible builds: source tarball embeds timestamps and umask to be marked as done. This means that you cl

Bug#1010378: leds-alix: reproducible builds: source tarball embeds timestamps and umask

Source: leds-alix Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps umask X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org leds-alix-source embeds the timestamp and file permissions determined by umask in the leds-alix source tarball: ht