[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#968183: marked as done (chirp: please make the build reproducible)



Your message dated Mon, 10 Aug 2020 11:48:28 +0000
with message-id <E1k56I0-000H0Z-Nw@fasolo.debian.org>
and subject line Bug#968183: fixed in chirp 1:20200227+py3+20200213-2
has caused the Debian Bug report #968183,
regarding chirp: please make the build reproducible
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
968183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968183
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: chirp
Version: 1:20200227+py3+20200213-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
chirp could not be built reproducibly.

This is because it shipped a debug.log file that contained non-
deterministic data like timestamps, etc.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-
--- a/debian/rules	2020-08-10 11:23:56.302078294 +0100
--- b/debian/rules	2020-08-10 11:27:44.805034313 +0100
@@ -5,3 +5,4 @@
 
 execute_after_dh_auto_install:
 	mv debian/chirp/usr/bin/chirpwx.py debian/chirp/usr/bin/chirpw
+	find debian/chirp/usr/lib -type f -name debug.log -delete

--- End Message ---
--- Begin Message ---
Source: chirp
Source-Version: 1:20200227+py3+20200213-2
Done: Christoph Berg <myon@debian.org>

We believe that the bug you reported is fixed in the latest version of
chirp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968183@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <myon@debian.org> (supplier of updated chirp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 10 Aug 2020 13:24:57 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 968183
Changes:
 chirp (1:20200227+py3+20200213-2) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Remove debug.log file that contained non-reproducible data.
     (Closes: #968183)
Checksums-Sha1:
 11029f8d5d7ff0b521b9760afd711168e7033858 2193 chirp_20200227+py3+20200213-2.dsc
 8d90dc9ceb856d8f56b5f84daed2293456ebf5a6 11880 chirp_20200227+py3+20200213-2.debian.tar.xz
Checksums-Sha256:
 9e25ffab64229a271c4077ffe6942bc9085a00971b7801d5b4339e9d389b4937 2193 chirp_20200227+py3+20200213-2.dsc
 e5848eb0cb1caeb9c068980d5d17f1ac0f28f657ac0c6c21322472906ba3de53 11880 chirp_20200227+py3+20200213-2.debian.tar.xz
Files:
 a4382b783d56f3d6d549390b4f833b2c 2193 hamradio optional chirp_20200227+py3+20200213-2.dsc
 e40a32d7d2d494d8e64dc43fd9d0feff 11880 hamradio optional chirp_20200227+py3+20200213-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl8xL90ACgkQTFprqxLS
p646qw/9HYqq23zfrwKXoVqpZrnLcS75ubE2rRcZ6rZAeSdtAbWwRasjdqnwOcuw
35bIHQMTSPum6G4H/HxCcw5JZHPUFUhYqB24PGkWTXnps6R3q4p7biVYobaRLoLc
IN82g479dE1lpdBAAS+wCudcTeLKuvMEgJHjO5LCInaaLV4zPstUU12M6n8u90Jg
E/BuIZNf0lF5HwZ/dnKMwz2fwyfJ1aeznqvnoJBPfPkSjau4VwW3wADk/fz+EDWo
Uq0Sgp925kpQwZodbsS6g55K5WOJhwaGEmE1ZryPfkvJ3iEh8D2wPlLmS/Y2sUlE
2UPXMLULIgRp76STU4jCB96FICO/RbCKVhsqjkUWTemCHxuDNG9oCPsessao4nIj
iPQMMBYTWxZ2zmzIMLKWWVXTJyp4p2zPyDWRswCfY7M1xXjNU3rp2eCgckbWPuxc
qKeiRo0VdcTv4mtIEV7MX6h8PNOOT8FRgusaUXdsdu9szPRU8XZi5ljSFtgXW2uo
OqudnciVT66TF6+sox488i2aBgbrA3F/PtunpSmNJsstzd5fdE+BqD3vSgGuEo3u
XzdCa4NA8fkqOgILlKDQBh1IbScL5ae2ARwLqLe0HAUzbXArM5S2pQIux4x2/3y9
2EAqMe7k/2CC+XjBqVKMFhZQoHRGKAcjbdVdYY6n10I9wJ3b3ZM=
=/XEP
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: