Debian Bug report logs - #846588
minicoredumper: please make the build reproducible

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: submit@bugs.debian.org

Subject: minicoredumper: please make the build reproducible

Date: Fri, 02 Dec 2016 12:58:30 +0100

[Message part 1 (text/plain, inline)]

Source: minicoredumper
Version: 2.0.0-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: umask
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi,

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

This is due to exluding var/crash from dh_fixperms (to keep the
subdirectories' permissions intact?) which means that the group "write"
bit is inherited from the system's umask.

Patch attached.

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


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

[minicoredumper.diff.txt (text/plain, attachment)]

Message #10 received at 846588-close@bugs.debian.org (full text, mbox, reply):

From: John Ogness <john.ogness@linutronix.de>

To: 846588-close@bugs.debian.org

Subject: Bug#846588: fixed in minicoredumper 2.0.0-2

Date: Fri, 02 Dec 2016 15:50:45 +0000

Source: minicoredumper
Source-Version: 2.0.0-2

We believe that the bug you reported is fixed in the latest version of
minicoredumper, 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 846588@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Ogness <john.ogness@linutronix.de> (supplier of updated minicoredumper 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: SHA512

Format: 1.8
Date: Fri, 02 Dec 2016 16:22:33 +0100
Source: minicoredumper
Binary: minicoredumper minicoredumper-utils libminicoredumper-dev libminicoredumper2
Architecture: source
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: John Ogness <john.ogness@linutronix.de>
Changed-By: John Ogness <john.ogness@linutronix.de>
Description:
 libminicoredumper-dev - minicoredumper library development files
 libminicoredumper2 - minicoredumper library
 minicoredumper - generate minimal and customized core dump files on Linux
 minicoredumper-utils - minicoredumper utilities
Closes: 846544 846588
Changes:
 minicoredumper (2.0.0-2) unstable; urgency=medium
 .
   * Require lsb-base >= 3.2-14 because reliance on /lib/lsb/init-functions
   * Limit packages to Linux
   * Fix build error on arch=x32 due to time_t with snprintf
   * Prevent co-installation with other core dumper handler, reported by
     Paul Wise, thanks (Closes: #846544)
   * Fix /var/crash permissions, reported and patch by Chris Lamb, thanks
     (Closes: #846588)
Checksums-Sha1:
 82f7e162e3a64e4bd617f67efe23b4f22b030bd6 2476 minicoredumper_2.0.0-2.dsc
 714e06f0696bd6097a7c634e5288eb800a20bd55 13420 minicoredumper_2.0.0-2.debian.tar.xz
Checksums-Sha256:
 cfa681d380f71e46ab7391308c03f69c0c6a138045df38df97276de2e355d8c2 2476 minicoredumper_2.0.0-2.dsc
 b9cfe9353e0a187956f26de132dd8e4f6a3b8d793b984e7477339a47c374fe67 13420 minicoredumper_2.0.0-2.debian.tar.xz
Files:
 8c529f6a3f0d98951c1fa8258a56ae07 2476 devel optional minicoredumper_2.0.0-2.dsc
 fe8bfdcd95422c3a4aa8dac4c5a7483a 13420 devel optional minicoredumper_2.0.0-2.debian.tar.xz

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

iQIzBAEBCgAdFiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAlhBlG8ACgkQe5boFiqM
9dHPYQ//YSecKh/cikp4AYzXr/neprhPdWcO7xq0qH13wsIsLW8aEDKNmYojG8Pb
3Mge7XlQcXo0g1jRqkHyowQCB6L8wUGAyAYmj0WPmpTjNRHUbuAp81ofCkF0dIgW
+Gu5BCSBca7Uwr8HFL9z2UDiq79xqhFcvBYyfTf48uoKLD3zrz2wtROSvquqqdE2
TAS6s6Wl9NTblUlSz4bX3l9x2J5xarZ+P/pgtslL/FagKtyrkxuIO2dX2UzlYDNk
yI8EgH37N3Rxn+yET5wJXUGKcW003oTKnc+N9S0gVdnLg3ciEJk9Hrr7nYIzZGTh
4yQJ9lkUT6svFCNGeA1dwFB81HxdXbUbByViFNATVU2v3RiG36cYmPhBrlnHTc1V
KQQWmJSeHrmkSTeIFFMTkHOfjiLwu6gLbvCt+e2Ee9vSuP9gFsJYfA1T4Agx3T3k
QjJRkcXqJ0gNLAHb9Z4atn+ox+xVL1OAPa+Xh3k4JiAVYWJeovaaGA3/bCPsl+S5
qysH/b9onN/T5xW4eNz/I+SZtXAjxtkAXEowJ9YqLfnJlDKPMs18s35OkLvBntIb
qieCH+86eG1TG0S62M1kfkR/EyAzHVRzAKBrSuGUSbSUdSDYRFH81W192HNFbNz1
hhMJICA3pS8ibOUV6oSj8xeNBPhFhxfQpHDEplnrY/lDjHJyUQ0=
=Fr/W
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.