Debian Bug report logs - #965362
numpydoc: 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: numpydoc: please make the build reproducible

Date: Mon, 20 Jul 2020 11:22:16 +0100

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

Source: numpydoc
Version: 1.1.0-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi,

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

This is because it includes a junit-results.xml and .coverage file
from the test run. (The latter file should have been detected by the
package-contains-python-coverage-file Lintian tag FYI.)

Patch attached.

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


Regards,

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

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

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

From: Andreas Beckmann <anbe@debian.org>

To: Debian Bug Tracking System <965362@bugs.debian.org>

Subject: Re: numpydoc: please make the build reproducible

Date: Wed, 22 Jul 2020 22:33:17 +0200

Followup-For: Bug #965362
Control: severity -1 serious

Since numpydoc is not the only package shipping .coverage, this causes file
conflicts with unrelated packages.


Andreas

Message #15 received at 965362-submitter@bugs.debian.org (full text, mbox, reply):

From: Christian Kastner <noreply@salsa.debian.org>

To: 965362-submitter@bugs.debian.org

Subject: Bug#965362 marked as pending in numpydoc

Date: Wed, 26 Aug 2020 22:21:56 +0000

Control: tag -1 pending

Hello,

Bug #965362 in numpydoc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/numpydoc/-/commit/627063a3a5c88b74b9bc8a7b6ac587ca8e508221

------------------------------------------------------------------------
Remove .coverage and junit-results.xml from build result

Closes: #965362
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/965362

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

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 965362-close@bugs.debian.org

Subject: Bug#965362: fixed in numpydoc 1.1.0-3

Date: Wed, 26 Aug 2020 22:35:48 +0000

Source: numpydoc
Source-Version: 1.1.0-3
Done: Christian Kastner <ckk@debian.org>

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

Debian distribution maintenance software
pp.
Christian Kastner <ckk@debian.org> (supplier of updated numpydoc 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: Thu, 27 Aug 2020 00:18:59 +0200
Source: numpydoc
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Changed-By: Christian Kastner <ckk@debian.org>
Closes: 965362
Changes:
 numpydoc (1.1.0-3) unstable; urgency=medium
 .
   * Team upload
 .
   * Remove .coverage and junit-results.xml from build result (Closes: #965362)
Checksums-Sha1:
 d9e7f761e09e79f4fbcc07b3b6d4530a68ec83e1 2329 numpydoc_1.1.0-3.dsc
 6810642c4f22eec280eaa1d6c113df45746ea946 4432 numpydoc_1.1.0-3.debian.tar.xz
 7d6599ab91c9f052a4fda0085798680125403817 7664 numpydoc_1.1.0-3_source.buildinfo
Checksums-Sha256:
 5b698591c32252dfb78f96d328d2af6e163c4a92d16d0c59421b58d21c818bd0 2329 numpydoc_1.1.0-3.dsc
 3b2a0496d6d46f833a7094b19b0f274e8664aecec920ebff3ea0d783a9554b0e 4432 numpydoc_1.1.0-3.debian.tar.xz
 4388f69c01202414d8e901517fc597c7a4fd37e65d8112cf01b25587846c14a1 7664 numpydoc_1.1.0-3_source.buildinfo
Files:
 0a943f01aff59be306de807661bdd8f0 2329 python optional numpydoc_1.1.0-3.dsc
 ba218d94f9bbad8d3bad064c21c58ec9 4432 python optional numpydoc_1.1.0-3.debian.tar.xz
 c3329f8f6161573ecf358e016b9eec62 7664 python optional numpydoc_1.1.0-3_source.buildinfo

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

iQIzBAEBCgAdFiEEQZ9+mkfDq5UZ8bCjOZU6N95Os2sFAl9G4I8ACgkQOZU6N95O
s2sqKxAAniGECEGd0wH2G6dpxXL5sRJ9Psc8Te4Od53sjhWbm01OobkMnfrXkN5e
W4hIfWZ16hEHn19rMG77P7kn0KzJOQ6MBNT/Z7PA68sJ3t6QxuAXi/p1fKWfuhj4
A58fxRpkYY5o6fb8y7jp8DOHCIIWMX5VTmeX5Xhq26G89U4djiaDdfJT0lOtkV2n
lphjQ9O2I5quo79uf5p+lA/QJW/xOGajN4gJ7C1IoGXMJuVdLHEN2giik43KVqoW
EmVJy7Af8VfSbWRgFNCvhexMCPiBeR6ttu8b9MbzDb41jYv6LvmkXCW9T8jQQahe
GrUmxnKRlBM0Ci+pHOpRkpSb1vhns1QnxgWe2ZuPgkBq+3YjoeYpssFCUIRH9buf
/1/urZqrOLCZSoA4AZU//uOWUQtpKtXCqiGiFDdKJHOj9icrkjsvxXcpVlRXchs4
qoR+FuXIDY1h6FWU5KW37/+Ls0rVDrWOKlAwsEUXH4Osn1eosYN3AuBDvbOYxYfU
YcvpFEtvBs1zk/ctqGp7zHGepApXXCSrHfpjE6xVXPrKLSs4cIFTcUwhcmeZsaFp
3JnYSujZsqJtvrTcLnALok9B4b2KV8gDLoe2KYlPOhcUJcPjjKCnXC+lUY7Y19c6
0/kfhHhyqNweRNGl3dhd/9Q5Nw4g/zRDeY0hLXaljJO4v8giHsw=
=7Qf8
-----END PGP SIGNATURE-----

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

From: Christian Kastner <ckk@debian.org>

To: 965362@bugs.debian.org, Chris Lamb <lamby@debian.org>, Andreas Beckmann <anbe@debian.org>

Subject: Re: numpydoc: please make the build reproducible

Date: Thu, 27 Aug 2020 00:07:39 +0200

On 2020-07-20 11:22:16 +0100 "Chris Lamb" <lamby@debian.org> wrote:
> Whilst working on the Reproducible Builds effort [0] we noticed that
> numpydoc could not be built reproducibly.
> 
> This is because it includes a junit-results.xml and .coverage file
> from the test run. (The latter file should have been detected by the
> package-contains-python-coverage-file Lintian tag FYI.)

This was caused by me again, for the same silly reason as in #968557
(broken alias for lintian). I only now saw this bug.

Sorry about that. Fix will be uploaded shortly.

Send a report that this bug log contains spam.