package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.3.0-21+really16.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/python-setuptools_39.0.1-1.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Fwd: [migration of alioth list reproducible-commits]

[Mattia Rizzolo]

On Mon, Jan 29, 2018 at 09:55:35PM +0100, Mattia Rizzolo wrote:
> So, I'm going to ask them to skip our list, and then in the next weeks
> work on moving stuff to rb-commits@ instead (this will also include
> moving the subscribers once the mails moved).

FYI, that's now done.
I:
* subscribed all people from reproducible-commits@alioth to
  rb-commits@l.r-b
* unsubscribed everybody from reproducible-commits@alioth
* moved the notes.git and blog.git to notify that new list instead
* configured the salsa repos to email the new list (they weren't
  emailing anything before)
* enabled moderation for all incoming traffic in reproducible-commits@
  (so I'll notice if anything arrives there that needs updating, during
  my daily list admin routines)


I.e., that list should be good to go.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#893324: diffoscope: terminology used in docs about exclusion options

[Mattia Rizzolo]

Control: tag -1 pending

On Sun, Mar 18, 2018 at 01:26:32PM +0800, Paul Wise wrote:
> Lets turn this into a bug about that instead. I would suggest replacing
> "Exclude" with "Exclude/ignore" within the docs about the options that 
> exclude some parts of the diffoscope output.

Please check out the latest commit, I added 'ignore' to help grepping
through the manpage.  Hopefully that's enough to cover your wish :)

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: pocl has reproducible test result: FTBFS

[Mattia Rizzolo]

On Sun, Mar 18, 2018 at 09:10:45AM +, Holger Levsen wrote:
> On Sun, Mar 18, 2018 at 08:46:14AM +0100, Andreas Beckmann wrote:
> > https://qa.debian.org/developer.php?login=pkg-opencl-devel%40lists.alioth.debian.org
> > 
> > lists pocl as FTBFS from reproducible test results ... which is correct
> > (it does FTBFS on armhf/arm64) but worthless information (so far it
> > never built successfully (due to testsuite failures) on !x86).
> > 
> > Where can this be fixed? No, not on the pocl side :-)
> 
> we can mark it with a special issue, which causes qa.debian.org to not
> display this ftbfs case. i'm about to enter a plane so I wont do it
> right now, but will do so later, unless someone else will do it til
> then.

However, I don't understand why, given that it seems quite clear to me
that nobody is working on a proper port, you haven't restricted the
architectures it can be built for.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.3.0-15+really11.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Accepted diffoscope 91~bpo9+1 (source) into stretch-backports

[Mattia Rizzolo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Mar 2018 11:34:17 +0100
Source: diffoscope
Binary: diffoscope
Architecture: source
Version: 91~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Reproducible builds folks 
<reproducible-builds@lists.alioth.debian.org>
Changed-By: Mattia Rizzolo <mat...@debian.org>
Description:
 diffoscope - in-depth comparison of files, archives, and directories
Closes: 849386 863879 863880 877726 886736 886963 887180 888112 888401 888402 
890528
Changes:
 diffoscope (91~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
 .
 diffoscope (91) unstable; urgency=medium
 .
   [ Mattia Rizzolo ]
   * d/clean: Remove .cache/.
   * diff: Wrap long regular expression for improved readability.
   * comparators.json: Fix UnicodeDecodeError with a non-UTF8 locale.
   * d/copyright: Update for the new year.
   * d/control: Bump Standards-Version to 4.1.3, no changes needed.
   * tests/android:
 + Skip tests involving abootimg on BE archs (see #725729).
 .
   [ Daniel Shahaf ]
   * diffoscope.diff: Document feeders.  Closes: #863880
   * Optimize the common case of feeders.  Closes: #863879
 .
   [ Juliana Oliveira ]
   * {tempfiles, utils.archive}: catch possible FileNotFoundError.
   * comparators.java: add support for procyon-decompiler.  Closes: #849386
   * {command, feeders, diff}: replaces subprocess.Popen() by .run().
 This is done in preparation for work on multiprocessing (#842837).
 + {command, zip, feeders}: replaces .wait by the new .returncode property.
 + comparators.utils.command: replaces .stderr_content by .stderr.
   * tests:
 + test_progress: fix test case for some broken versions of
   python-progressbar.  Closes: #877726
 + utils.tools: add support for modules on skip_unless* annotations.
 .
   [ Chris Lamb ]
   * comparators:
 + utils/compare:
   - Show extended filesystem metadata even when directly comparing two
 files, not just when we specify two directories.  Closes: #888402
 + macho:
   - If the If the LLVM disassembler does not work, try the
 internal one.  Closes: #886736
   - Always strip the filename, not just when by itself.
 + json:
   - Do some cheap fuzzy parsing to detect JSON files not named .json.
   - Also match unicode JSON files.
   - Optionally compare JSONs with the jsondiff module.  Closes: #888112
 + directory:
   - Report differences in extended file attributes when comparing files.
 Closes: #888401
 + xsb:
   - Add support for comparing XMLBeans binary schemas.
 + barkeley_db:
   - Add support for comparing Berkeley DB files.  Closes: #890528
   * Misc code cleaup.
   * tests:
 + comparators.test_elf: Return '0' if we can't parse the readelf
   version number.  Closes: #886963
   * debian:
 + Explicitly build-depend and recommend e2fsprogs.  Closes: #887180
 .
   [ Ximin Luo ]
   * Partially revert the changes done for #888402 to maintain the current.
 behaviour of --exclude-directory-metadata.
   * Refactor how the configuration is loaded:
 + Move the defaults into a Config.reset() method.
 + reset() the configuration at the end of main(), to help the testsuite.
Checksums-Sha1:
 21b3eb84069b916e4ab6f077bbc0706a8a0e8288 3460 diffoscope_91~bpo9+1.dsc
 0b646d4f9f4e8422e539e97d7c8ef2d06557c7be 18064336 diffoscope_91~bpo9+1.tar.xz
 c9fb0a4042bdec8d4c8784038a8e1f6552819864 19974 
diffoscope_91~bpo9+1_amd64.buildinfo
Checksums-Sha256:
 450c19737784505cb603db26f3a6bd69d478daf6d92bea58bd95c1ac23fbc285 3460 
diffoscope_91~bpo9+1.dsc
 a8b595363d455113e376c6efbdcc0832ced7da8d92b34169c245ea3fea210411 18064336 
diffoscope_91~bpo9+1.tar.xz
 755ff9d76f2e2f806e7ad0e1dfff46ba336ae8e20da72736c07cfb9821415d66 19974 
diffoscope_91~bpo9+1_amd64.buildinfo
Files:
 477b482634ba8ac244ecb16a98e9d72d 3460 devel optional diffoscope_91~bpo9+1.dsc
 369ee73d343224b8a1e9c299f0c4f260 18064336 devel optional 
diffoscope_91~bpo9+1.tar.xz
 1e53b1ba8d5e19ed99f78598795bd225 19974 devel optional 
diffoscope_91~bpo9+1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlqecLwACgkQCBa54Yx2
K604ZxAAvOr20BRHPmMSfQFt5K+Jtvk947vsI+l32yqczvuynkUVbHOCg4amrqzE
SArj4nNuVhh+G0yV4eXac4XkZtsYMwkwnAX+bBT/sZxxe48rqc+vwJFa7j1+ffwd
NbE8eJuCHhGnZ6mNFt2ganVkVW8m33pDNXC7Djk5t8rDOlFyJJ7bmjepOcog5HQw
FV6jdzIQolQkmkFpIpSK6a8S6jDEgKsHz/R9R2w8jgZdBGvHlUd6eTbZIq8gPapF
xG9Iomc87RfGH7xYRV8qcMD1qw8/1Ti0LVIUcfO46CbPq/n1vCqnxHUZr7/zmHuP
yZ/oyYsc66Gz9Wi7A4lexXWP48jpP7KQpL+f+Ywmn8HiGOZy4/IaYifeu55/54yq
ySvyAEZfDBS5/Krw4nzAEKVaXSF16nBjUP/vkp2c5rTRMbeWVxdVCTyTKXxnzlKm
O4+LbgIdrW/qANf6J+LDYtXsrhGzFkQZxcNzfqrORqZsxyRHF0eY9padSwmsETJ7
zy4e/lRvBU4arReOr7+OQI9bbDrN581/rPucugph9Au8INmbSDNDYLTPpSmnf/la
qBjgKt1xWzdDW4oqWCndhDsL383R/hZWp8a/FcSUXvbWjh2sXnWs8bVE4a96uzVa
uvA0j3We5KeA5T8A3WkLBiehyU82uYrIVkdBim5YgJzE0NmB+yg=
=TTRb
-END P

Bug#891903: diffoscope: programming error in except clause

[Mattia Rizzolo]

FTR, this happened also on ubuntu autopkgtest, where the tests fail on
armhf, arm64, ppc64el, s390x whilst it passes on x86.
http://autopkgtest.ubuntu.com/packages/diffoscope

I planned on debugging that next week (as I need to do it anyway to get it
land on ubuntu)

On Fri, Mar 2, 2018 at 11:57 AM Chris Lamb  wrote:

> Hi Zbigniew,
>
> > I'm trying to update diffoscope to version 91 in Fedora rawhide
>
> Thanks for the report!
>
> > It seem pretty clear that .decode() is called on a str object, which
> > cannot work.
>
> .. which is odd as this code as been around for ages:
>
>
> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=eb070310e23e44deb6b0caaa7d022d72b13406a6
>
> I wonder if your s390x build environment has some kind of
> Unicode/terminal foo going on?
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
>
>
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#891867: diffoscope: improve .changes diffs

[Mattia Rizzolo]

On Thu, Mar 01, 2018 at 09:00:27PM +, Chris Lamb wrote:
> >  differences.append(Difference.from_text(
> > -self.deb822.get_as_string('Checksums-Sha256'),
> > -other.deb822.get_as_string('Checksums-Sha256'),
> > +self.deb822.get_as_string('Checksums-Sha256') + "\n",
> > +other.deb822.get_as_string('Checksums-Sha256') + "\n",
> 
> Why not .strip() them all instead, out of interest?

Because deb822.get_as_string() returns a single string containing all of
'Checksums-Sha256' (in this case) with the \n embedded in that string.
So to .str() them all you'd need to instead do a .splitlines() of
deb822.get_as_string() and then add something clever to Difference to
handle the array instead of a text.

I am not a fan of "randomly" adding \n either, but for sure it is the
simplest way to make the diff behaviour here saner.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Accepted diffoscope 91 (source) into unstable

[Mattia Rizzolo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Mar 2018 13:40:48 +0100
Source: diffoscope
Binary: diffoscope
Architecture: source
Version: 91
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 
<reproducible-builds@lists.alioth.debian.org>
Changed-By: Mattia Rizzolo <mat...@debian.org>
Description:
 diffoscope - in-depth comparison of files, archives, and directories
Closes: 849386 863879 863880 877726 886736 886963 887180 888112 888401 888402 
890528
Changes:
 diffoscope (91) unstable; urgency=medium
 .
   [ Mattia Rizzolo ]
   * d/clean: Remove .cache/.
   * diff: Wrap long regular expression for improved readability.
   * comparators.json: Fix UnicodeDecodeError with a non-UTF8 locale.
   * d/copyright: Update for the new year.
   * d/control: Bump Standards-Version to 4.1.3, no changes needed.
   * tests/android:
 + Skip tests involving abootimg on BE archs (see #725729).
 .
   [ Daniel Shahaf ]
   * diffoscope.diff: Document feeders.  Closes: #863880
   * Optimize the common case of feeders.  Closes: #863879
 .
   [ Juliana Oliveira ]
   * {tempfiles, utils.archive}: catch possible FileNotFoundError.
   * comparators.java: add support for procyon-decompiler.  Closes: #849386
   * {command, feeders, diff}: replaces subprocess.Popen() by .run().
 This is done in preparation for work on multiprocessing (#842837).
 + {command, zip, feeders}: replaces .wait by the new .returncode property.
 + comparators.utils.command: replaces .stderr_content by .stderr.
   * tests:
 + test_progress: fix test case for some broken versions of
   python-progressbar.  Closes: #877726
 + utils.tools: add support for modules on skip_unless* annotations.
 .
   [ Chris Lamb ]
   * comparators:
 + utils/compare:
   - Show extended filesystem metadata even when directly comparing two
 files, not just when we specify two directories.  Closes: #888402
 + macho:
   - If the If the LLVM disassembler does not work, try the
 internal one.  Closes: #886736
   - Always strip the filename, not just when by itself.
 + json:
   - Do some cheap fuzzy parsing to detect JSON files not named .json.
   - Also match unicode JSON files.
   - Optionally compare JSONs with the jsondiff module.  Closes: #888112
 + directory:
   - Report differences in extended file attributes when comparing files.
 Closes: #888401
 + xsb:
   - Add support for comparing XMLBeans binary schemas.
 + barkeley_db:
   - Add support for comparing Berkeley DB files.  Closes: #890528
   * Misc code cleaup.
   * tests:
 + comparators.test_elf: Return '0' if we can't parse the readelf
   version number.  Closes: #886963
   * debian:
 + Explicitly build-depend and recommend e2fsprogs.  Closes: #887180
 .
   [ Ximin Luo ]
   * Partially revert the changes done for #888402 to maintain the current.
 behaviour of --exclude-directory-metadata.
   * Refactor how the configuration is loaded:
 + Move the defaults into a Config.reset() method.
 + reset() the configuration at the end of main(), to help the testsuite.
Checksums-Sha1:
 cf78d47c07e0cea4b0d667c02a0beff82b2cb28b 3429 diffoscope_91.dsc
 f10a233ff4469d6405eac3bc6c03da6d33962efb 8935512 diffoscope_91.tar.xz
 1413267eea08eb05b0664a4ba13b46abc50a9df7 20151 diffoscope_91_amd64.buildinfo
Checksums-Sha256:
 28e12196a5e461349d1cfdfa96bb3914337f6bd6327d13637de80a5bedd08169 3429 
diffoscope_91.dsc
 12034827db747b831b0c80a340f607c8ac4b85936610d38985135941b8a4f0ee 8935512 
diffoscope_91.tar.xz
 a456c23241bed0e2dc6230a03e3f7897ad9a715f54da1e662b4f7864c0804d5f 20151 
diffoscope_91_amd64.buildinfo
Files:
 4a1c8bd026d379c91fec4db88eee3679 3429 devel optional diffoscope_91.dsc
 a72769fc6dc5f80c6a31b873023a 8935512 devel optional diffoscope_91.tar.xz
 728e5ffa6fff19b50c3baf3dfe0a2ee6 20151 devel optional 
diffoscope_91_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlqX9qYACgkQCBa54Yx2
K62jGg/+J2JLNEmq/nVoNa182wyzTzerZVy03V5Pc4WBt1pyZ4DPbvDrAhZvWZmP
qBXr54UxkbbNfXa+fYAph4xr7D5xL4olDEOFRcDf5UJfGwdjaravc6CeE1z915eW
IJkFIOd17ySKlxM5RAVQ1xtQqXiCsBBHa4W2XryleNivJOSOKotEbkEul8MrregE
HREtWF76l7t5Mas2bFxD0xjYAfIYgB8vDLCFnsoOHsqUKksf2PYr60ge2CmCLKUO
Lw/gTcXD+T8k6UBoC2HXmU/2Wgsd9KClAOHUWwdJK78akvvjSC+zBfcewW1vtM1P
lVui0SjSmd7K3suNZgNnrCboKpq7J8ULR8g1GikElxV6orkDsmhX5SfqgsiqWsqw
yZbm1VHRBtOawnQUD8U2bLqVZsTOsE5JMF7ehHjGehEgoCgg3oNTbY8cIAWyd8y/
erk43kNYKhYdHbEfpvGRJekSvJOS8BY4h94ThJ1B4dElUhMzESJ5Fa2S/Ik3fyDS
WKWY8rS3WSons4WL+yjvd7Y2hfuf/IWt6XaG2rge3ODJlwD3BxFrLg7NzkNhH7NJ
a1yITYx2JbMahQZQribpkdPiFcx38y0LcAT25br8AY+asa0fr7qPOfshQfytFiIs
bDfMRuWM5I6KsCwvE4Gtjrawrux03EdbB0piGQzWKpfAmO3qqdE=
=L47V
-END PGP SIGNATURE-


___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.3.0-9+really5.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [disorderfs] 02/02: Override no-upstream-changelog as we are upstream.

[Mattia Rizzolo]

On Wed, Feb 07, 2018 at 08:44:37AM +, Chris Lamb wrote:
> commit e98218f863d7013f9bac62f3ba06234106c40389
> Author: Chris Lamb <la...@debian.org>
> Date:   Wed Feb 7 08:43:45 2018 +
> 
> Override no-upstream-changelog as we are upstream.

Well, but no-upstream-changelog is a thing for the users as I see it.
What you probably mean is that the content of what should be in the
upstream changelog is already covered by the debian changelog, right?

> diff --git a/debian/disorderfs.lintian-overrides 
> b/debian/disorderfs.lintian-overrides
> new file mode 100644
> index 000..fc882fe
> --- /dev/null
> +++ b/debian/disorderfs.lintian-overrides
> @@ -0,0 +1 @@
> +no-upstream-changelog


Also please add a comment next to the override itself explaining the
reasons for the override.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Fwd: [migration of alioth list reproducible-commits]

[Mattia Rizzolo]

On Mon, Jan 29, 2018 at 07:22:29PM +0530, Chris Lamb wrote:
> > agreed. thanks for presenting the options clearly.
> 
> Same here. :)

Cool.

> We should probably keep reproducible-bugs as a "Debian" list, mind you?

Sure, WFM.
(Also, you are the only owner of that ml, so feel free to reply to the
mail you got :)


So, I'm going to ask them to skip our list, and then in the next weeks
work on moving stuff to rb-commits@ instead (this will also include
moving the subscribers once the mails moved).

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Fwd: [migration of alioth list reproducible-commits]

[Mattia Rizzolo]

As you may know, alioth is dying, and services and stuff are being moved
off, or directly left them to die peacefully.

Holger already asked to migrate reproducible-builds@¹, and we've been
asked for reproducible-commits@² as well.

It's my opinion that we should kill
reproducible-comm...@lists.alioth.debian.org and instead start to more
effectively use rb-comm...@lists.reproducible-builds.org.

After all most of the commits we do are not directly tied to debian
itself.  Alright, the most prominent user of that list is the notes.git
repo, which currently it's still debian-only, but I still believe we
should move stuff there.


Comments welcome.


¹ 
https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20180122/009826.html
² https://lists.alioth.debian.org/mailman/listinfo/reproducible-commits
³ https://lists.reproducible-builds.org/listinfo/rb-commits
  note: diffoscope commits are instead sent to diffoscope@l.r-b.o (and
  I'd love to also see bugs there, mhh…

- Forwarded message from alioth lists migration team 
<ad...@alioth-lists.debian.net> -

Date: Sun, 28 Jan 2018 18:26:47 +
From: alioth lists migration team <ad...@alioth-lists.debian.net>
To: reproducible-commits-ow...@lists.alioth.debian.org
Subject: Action requested: migration of alioth list reproducible-commits
X-Mailer: MIME::Lite 3.030 (F2.85; T2.13; A2.18; B3.15; Q3.13)
Message-Id: <e1efrfd-0008bn...@alioth-lists-01.debian.net>

Dear list owner,

As per the announcement on debian-devel-announce[1] the migration of
lists.alioth.debian.org mailing lists is now underway. If you would
like reproducible-comm...@lists.alioth.debian.org
to be included in this process, to ensure that the list still works
after the migration in late March/April, please let us know by replying
to this email. Otherwise, the list will stop working at migration time
and the archives will no longer be accessible.

Feel free to also let us know if the list is no longer needed, so we can
note that down too. Replies must be received by 15th March 2018.

More information about the new service can be found here:
<https://wiki.debian.org/Alioth/MailingListContinuation>

Thanks,
the alioth-lists migration team.

[1] <https://lists.debian.org/debian-devel-announce/2018/01/msg3.html>




- End forwarded message -

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.3.0-5+really1.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#887180: diffoscope should depend on e2fsprogs explicitly

[Mattia Rizzolo]

Control: tag -1 pending

On Thu, Jan 25, 2018 at 04:39:39PM +0530, Chris Lamb wrote:
> A patch for this is:
> 
>   commit 13fe60e2a9eea0ac0a32453091cc524c90cd85ac
>   Author: Chris Lamb <la...@debian.org>
>   Date:   Thu Jan 25 22:08:42 2018 +1100
>   
>   Explicitly depend on e2fsprogs. (Closes: #887180)
>   
>debian/control | 1 +
>diffoscope/main.py | 1 -
>2 files changed, 1 insertion(+), 1 deletion(-)

Right.
I checked that we had no missing instances of @tool_required() and that
lsattr was the only program from e2fsprogs used by diffoscope.

Thanks, applied!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Mattia Rizzolo]

On Thu, Jan 25, 2018 at 06:45:36AM +0530, Chris Lamb wrote:
>   
> https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=1b121ea4efdb9fc614d32172b9749b5dd4afc550

So this added a new build dependency, etc.
I've built the required backports, and uploaded them to DELAYED/10 so
that they will land to stretch-backports' NEW after they migrate to
testing (as python-jsondiff was accepted into unstable for the first
time only two days ago).

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#888112: diffoscope: compare JSON files using Python jsondiff module

[Mattia Rizzolo]

On Tue, Jan 23, 2018 at 09:41:18PM +0800, Paul Wise wrote:
> The Python jsondiff module allows comparing JSON files in a better way
> than just comparing the plain text like diffoscope currently does.

Actually, that's a problem.
Diffoscope has a json comparator, that works great, but it's failing for
your example:

> $ curl -s 'https://salsa.debian.org/api/v4/users/1' > 1
> $ curl -s 'https://salsa.debian.org/api/v4/users/2' > 2

mattia@warren /tmp % diffoscope --debug 1 2
2018-01-23 15:45:31 D: diffoscope.presenters.formats: Will generate the 
following formats: text
2018-01-23 15:45:31 D: diffoscope.main: Starting diffoscope 90
2018-01-23 15:45:31 D: diffoscope.locale: Normalising locale, timezone, etc.
2018-01-23 14:45:31 D: diffoscope.main: Starting comparison
2018-01-23 14:45:31 D: diffoscope.comparators: Loaded 63 comparator classes
2018-01-23 14:45:31 D: diffoscope.comparators.utils.specialize: Using TextFile 
for 1
2018-01-23 14:45:31 D: diffoscope.comparators.utils.specialize: Using TextFile 
for 2
2018-01-23 14:45:31 D: diffoscope.comparators.utils.compare: Comparing 1 
(TextFile) and 2 (TextFile)
...

I.e. it's not recognizing them as json files.
If I simply rename them to 1.json and 2.json and run diffoscope on them:

mattia@warren /tmp % diffoscope --debug 1.json 2.json
2018-01-23 15:46:40 D: diffoscope.presenters.formats: Will generate the 
following formats: text
2018-01-23 15:46:40 D: diffoscope.main: Starting diffoscope 90
2018-01-23 15:46:40 D: diffoscope.locale: Normalising locale, timezone, etc.
2018-01-23 14:46:40 D: diffoscope.main: Starting comparison
2018-01-23 14:46:40 D: diffoscope.comparators: Loaded 63 comparator classes
2018-01-23 14:46:40 D: diffoscope.comparators.utils.specialize: Using JSONFile 
for 1.json
2018-01-23 14:46:40 D: diffoscope.comparators.utils.specialize: Using JSONFile 
for 2.json
2018-01-23 14:46:40 D: diffoscope.comparators.utils.compare: Comparing 1.json 
(JSONFile) and 2.json (JSONFile)
2018-01-23 14:46:40 D: diffoscope.comparators.utils.file: 
File.has_same_content: < 1.json> < 
2.json>
2018-01-23 14:46:40 D: diffoscope.diff: Running diff -aU7 
/tmp/tmpfpv5c6dm_diffoscope/fifo1 /tmp/tmpfpv5c6dm_diffoscope/fifo2
2018-01-23 14:46:40 D: diffoscope.diff: diff -aU7 
/tmp/tmpfpv5c6dm_diffoscope/fifo1 /tmp/tmpfpv5c6dm_diffoscope/fifo2: returncode 
1, parsed True
 
|##|
  100% Time: 0:00:00 
2018-01-23 14:46:40 D: diffoscope.presenters.formats: Generating 'text' output 
at '-'
--- 1.json
+++ 2.json
│   --- 1.json
├── +++ 2.json
│ @@ -1,16 +1,16 @@
│  {
│ -"avatar_url": 
"https://seccdn.libravatar.org/avatar/9a5dac7fca5fa69fcb4fa36b948ff766?s=80=identicon;,
│ -"bio": "",
│ -"created_at": "2017-12-17T12:04:05.482Z",
│ -"id": 1,
│ +"avatar_url": 
"https://seccdn.libravatar.org/avatar/a0177f306e580e136af48558989f2782?s=80=identicon;,
│ +"bio": null,
│ +"created_at": "2017-12-17T12:46:16.992Z",
│ +"id": 2,
│  "linkedin": "",
│ -"location": "",
│ -"name": "Administrator",
│ -"organization": "",
│ +"location": null,
│ +"name": "Paul Martin",
│ +"organization": null,
│  "skype": "",
│  "state": "active",
│  "twitter": "",
│ -"username": "root",
│ -"web_url": "https://salsa.debian.org/root;,
│ +"username": "pm",
│ +"web_url": "https://salsa.debian.org/pm;,
│  "website_url": ""
│  }
1 mattia@warren /tmp %  
        
   :(


Which is arguably even much better than what you get from that jsondiff
command :)


FTR, it seems the only check used to decide whether a file is a json
file, is to look for a '.json' as a filename suffix (and I'm not sure we
can do much better without looking into the file, which is probably too
expensive a check).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/dpkg_1.19.0.5.0~reproducible1.dsc 
has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: packages that FTBFS twice in a row ...

[Mattia Rizzolo]

On Sat, Dec 23, 2017 at 08:27:50AM +, Holger Levsen wrote:
> On Fri, Dec 22, 2017 at 10:43:34PM +0100, Mattia Rizzolo wrote:
> > So, yes, source packages can be built reproducibly!
> 
> neat, thanks for pointing this out! In which version of dpkg was that
> feature?

dpkg (1.18.11) unstable; urgency=medium
…
  * Make dpkg-source generate reproducible source packages when run
standalone, by honoring SOURCE_DATE_EPOCH.
…
  * Perl modules:
…
- Fix reproducible source package support in Dpkg::Source::Archive, by
  sorting the tar contents with --sort=name.
…
 -- Guillem Jover <guil...@debian.org>  Sun, 06 Nov 2016 03:09:02 +0100

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: packages that FTBFS twice in a row ...

[Mattia Rizzolo]

On Fri, Dec 22, 2017 at 04:32:50PM +, Holger Levsen wrote:
> no. the creation of Debian source packages is not reproducible at the
> moment. I don't recall whether we found a fundamental problem with it or
> if simply we had other fishes to fry.

Actually, Guillem went ahead and did this himself.  He also thought it
would be hard, but after trying only few changes to dpkg were needed.
Look:

mattia@warren ..vel/reproducible/diffoscope/diffoscope (git)-[master] % mkdir 
../a ../b
mattia@warren ..vel/reproducible/diffoscope/diffoscope (git)-[master] % 
dpkg-source -b .
dpkg-source: info: using options from diffoscope/debian/source/options: 
--tar-ignore=.*.sw? --tar-ignore=*/*~ --tar-ignore=,,* --tar-ignore=.[#~]* 
--tar-ignore=.deps --tar-ignore=.git --tar-ignore=.gitattributes 
--tar-ignore=.gitignore --tar-ignore=.gitmodules
dpkg-source: info: using source format '3.0 (native)'
dpkg-source: info: building diffoscope in diffoscope_89.tar.xz
dpkg-source: info: building diffoscope in diffoscope_89.dsc
mattia@warren ..vel/reproducible/diffoscope/diffoscope (git)-[master] % dcmd mv 
../diffoscope_89.dsc ../a
mattia@warren ..vel/reproducible/diffoscope/diffoscope (git)-[master] % 
dpkg-source -b .
dpkg-source: info: using options from diffoscope/debian/source/options: 
--tar-ignore=.*.sw? --tar-ignore=*/*~ --tar-ignore=,,* --tar-ignore=.[#~]* 
--tar-ignore=.deps --tar-ignore=.git --tar-ignore=.gitattributes 
--tar-ignore=.gitignore --tar-ignore=.gitmodules
dpkg-source: info: using source format '3.0 (native)'
dpkg-source: info: building diffoscope in diffoscope_89.tar.xz
dpkg-source: info: building diffoscope in diffoscope_89.dsc
mattia@warren ..vel/reproducible/diffoscope/diffoscope (git)-[master] % dcmd mv 
../diffoscope_89.dsc ../b
mattia@warren ..vel/reproducible/diffoscope/diffoscope (git)-[master] % cd ..
mattia@warren ~/devel/reproducible/diffoscope % diffoscope a/diffoscope_89.dsc 
b/diffoscope_89.dsc
 
|##|
  100% Time: 0:00:00
mattia@warren ~/devel/reproducible/diffoscope %


So, yes, source packages can be built reproducibly!
:D

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.2.0-21+really17.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.2.0-18+really14.0~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Please review the draft for week 132's blog post

[Mattia Rizzolo]

On Tue, Nov 07, 2017 at 01:19:16PM +, Chris Lamb wrote:
> Chris Lamb wrote:
> 
> > Please review the draft for week 132's blog post:
> 
> Published. Many thanks to all who contributed and reviewed!

Except that you dropped the t.r-b.o section while it was still in FIXME.
Last week a bunch of stuff happened there (as you might guess, with the
summit and all)...
I understand the deadline but, could you please be more considerate and
evaluate whether it's really all done before publishing?


(btw, I don't think I'll have the time myself to put it on the blog
today)

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [Qa-jenkins-dev] Bug#880873: jenkins.debian.org: Move some IRC announcements to #debian-reproducible-changes.

[Mattia Rizzolo]

Control: user jenkins.debian@packages.debian.org
Control: usertag -1 reproducible

On Sun, Nov 05, 2017 at 09:37:28AM +, Chris Lamb wrote:
>   Move some IRC announcements to #debian-reproducible-changes.
>   
>   This changes the behaviour such that we always announce on our "noisy"
>   #debian-reproducible-changes but keeps the main #debian-reproducible
>   channel free for a) when we really want to notify the channel such as 
> when
>   we want to preserve artifacts or explicitly ask to be notified and b)
>   regular chat.

I'm torn on this: I don't find the current scheduling messages to be
_so_ noisy.

I'd like to hear what the other people that lurk in the channel thing of
this change (hence CCing reproducible-builds ML).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [diffoscope] 01/01: test_dtb.py: Only parse the version number, not any "-dirty" suffix. (Closes: #880279)

[Mattia Rizzolo]

You did this, but actually the bug was already fixed (i.e. it wasn't broken
by the "-dirty" suffix, but due to the output changing the order of the
lines)
Nonetheless, I find your solution of using a regular expression superior to
my guesswork, but I would have still considered the -dirty suffix relevant
and part of the version.

On Fri, 3 Nov 2017, 10:02 a.m. Chris Lamb,  wrote:

> This is an automated email from the git hooks/post-receive script.
>
> lamby pushed a commit to branch master
> in repository diffoscope.
>
> commit d4ce05062e0368549ffe34276233f48f9ab68900
> Author: Chris Lamb 
> Date:   Fri Nov 3 10:01:39 2017 +0100
>
> test_dtb.py: Only parse the version number, not any "-dirty" suffix.
> (Closes: #880279)
> ---
>  tests/comparators/test_dtb.py | 19 +++
>  1 file changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/tests/comparators/test_dtb.py b/tests/comparators/test_dtb.py
> index 635ff30..eeb5db6 100644
> --- a/tests/comparators/test_dtb.py
> +++ b/tests/comparators/test_dtb.py
> @@ -18,6 +18,7 @@
>  # You should have received a copy of the GNU General Public License
>  # along with diffoscope.  If not, see .
>
> +import re
>  import pytest
>  import subprocess
>
> @@ -35,14 +36,16 @@ dtb2 = load_fixture('devicetree2.dtb')
>
>
>  def fdtdump_version():
> -out = subprocess.check_output(('fdtdump', '--version'),
> stderr=subprocess.STDOUT)
> -# We are looking for a line like
> -#   Version: DTC 1.4.5
> -# that usually is placed last
> -for line in reversed(out.decode().splitlines()):
> -if line.startswith('Version: '):
> -return line.split()[2]
> -raise ValueError('Error parsing `fdtdump --version` output')
> +out = subprocess.check_output(
> +('fdtdump', '--version'),
> +stderr=subprocess.STDOUT,
> +).decode('utf-8')
> +
> +m = re.search(r'Version: DTC (?P\d+\.\d+\.\d+)', out)
> +if m is None:
> +raise ValueError("Error parsing `fdtdump --version` output")
> +
> +return m.group('version')
>
>
>  def test_identification(dtb1):
>
> --
> Alioth's /usr/local/bin/git-commit-notice on /srv/
> git.debian.org/git/reproducible/diffoscope.git
>
> ___
> Reproducible-commits mailing list
> reproducible-comm...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/reproducible-commits
>
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [debhelper-devel] "Rules-Requires-Root: no" vs ExtUtils::Install + dh_strip_nondeterminism

[Mattia Rizzolo]

On Sun, Oct 29, 2017 at 04:02:20PM +0100, Axel Beckert wrote:
> > Yes.  I tried the same package you brought as an example,
> > systray-mdstat, which has png files that gets modified.
> 
> Huh? Maybe there has been a misunderstanding, but it didn't do that
> for me:
> 
> Neither dh_strip_nondeterminism emitted anything during a fakerooted
> build (which it AFAIK should if it changes anything), nor did
> "strip-nondeterminism share/*" cause "git status" to show any changes
> in the files afterwards.

Are you running with DH_VERBOSE=1?  Because here I clearly get that by
trying to build systray-mdstat as currently in unstable:

   dh_strip_nondeterminism
Using 1504826979 as canonical time
Normalizing 
debian/systray-mdstat/usr/share/perl5/auto/share/dist/systray-mdstat/harddrivespare.png
 using File::StripNondeterminism::handlers::png
Normalizing 
debian/systray-mdstat/usr/share/perl5/auto/share/dist/systray-mdstat/harddrivefail.png
 using File::StripNondeterminism::handlers::png
Normalizing 
debian/systray-mdstat/usr/share/perl5/auto/share/dist/systray-mdstat/harddriveok.png
 using File::StripNondeterminism::handlers::png
Normalizing 
debian/systray-mdstat/usr/share/perl5/auto/share/dist/systray-mdstat/error.png 
using File::StripNondeterminism::handlers::png
Normalizing 
debian/systray-mdstat/usr/share/perl5/auto/share/dist/systray-mdstat/harddrivewarn.png
 using File::StripNondeterminism::handlers::png


> In contrary to that, running "strip-nondeterminism -t png
> t/fixtures/png/tEXt.png.in" in strip-nd's git repo clearly shows such
> a change:
> 
> → git status --short
> → strip-nondeterminism -t png t/fixtures/png/tEXt.png.in
> → git status --short
>  M t/fixtures/png/tEXt.png.in
> → 
> 
> But for systray-mdstat:
> 
> → git status --short
> → strip-nondeterminism -t png share/*
> → git status --short

For handlers like png's you might need to define a time (i.e. use the -T
option, possibly with --clamp-timestamp)

> > Pending release, shall I cut one right away?
> 
> I'd be happy if it would only take days (and not weeks) to get this
> fix into unstable. But that's just my wish. :-)

Ok, I'll see about it ;)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [debhelper-devel] "Rules-Requires-Root: no" vs ExtUtils::Install + dh_strip_nondeterminism

[Mattia Rizzolo]

On Sat, Oct 28, 2017 at 07:11:37PM +0200, Axel Beckert wrote:
> > I tried live patching strip-nd by chaging the
> > open(my $fh, '+<', $filename)
> > to
> > open(my $fh, '<', $filename)
> > and indeed I could get a build completely identical to the one done
> > without R³ and unpatched strip-nd (and the log confirms files are still
> > being processed by strip-nd.
> 
> Did your example contain a PNG which needs a fixup?

Yes.  I tried the same package you brought as an example,
systray-mdstat, which has png files that gets modified.

> Looking at
> https://anonscm.debian.org/git/reproducible/strip-nondeterminism.git/tree/t/fixtures/png
> it seems as if tEXt.png.in is a case where strip-nd should change
> something (while the other examples contain symlinks and hence I
> expect those being examples where nothing should be changed).

Yes.

> Maybe the test suite should do a variant with read-only files which
> need to be modified, too, to verify that this case works, too, and
> continues to work.

That's annoying to do, as it would be to be done through code since git
doesn't store the w bit.

> > So, I think that to handle this issue we should just drop that single
> > byte from strip-nd and consider it done.
> 
> \O/

https://anonscm.debian.org/git/reproducible/strip-nondeterminism.git/commit/?id=e32fed6
Pending release, shall I cut one right away?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/dpkg_1.19.0.4.0~reproducible1.dsc 
has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#878342: diffoscope: incredibly huge amount of temporary files when comparing src:wine artifacts

[Mattia Rizzolo]

Package: diffoscope
Version 87
Severity: important

Today I tried to manually run diffoscope over a build of src:wine to see
whether we could get a usable diff.
Unfurtunately, diffoscope died with ENSPC after 3 hours and half.  The
partition had ~50 GB free when I started diffoscope, and after it died
it left around 21 GB of temporary files, not sure whether all the 50 GB
were used in a specific moment, but even 21 GB are a lot.

I have the artifacts available (~ 200 MB) if anybody wants to
investigate.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: apg bug report #870890 fixed in last version

[Mattia Rizzolo]

On Sun, Oct 08, 2017 at 11:40:27PM -0500, jathan wrote:
> Hi everyone. I have read in the last message of bug report #870890 that
> the bug is already fixed in the last version of apg. Do I need to do
> something else regarding to update some file of Reproducible Builds Team
> to record this apg status?

I think you are talking of the note that appears in the apg's
reproducible page?  Usually nothing, we have automation in place to
automatically remove archived bugs, so that bug would be removed in ~2
months.

But given that you asked about it, I've now removed it manually :)

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Please review the draft for week 126's blog post

[Mattia Rizzolo]

On Sun, Sep 24, 2017 at 07:14:22PM +0100, Chris Lamb wrote:
> > I already had to do something similar in e222b3a
> 
> (To save others looking it up, this is refering to:)
> 
>   https://anonscm.debian.org/git/reproducible/blog.git/commit/?id=e222b3a

Actually looks like I copied the wrong id, sorry!!
A more relevant commit to what I was I trying to highlight would be

https://anonscm.debian.org/git/reproducible/blog.git/commit/?id=fd352f9354851916b27fa13f2da07fd758aba953

The tracker link is better described as nitpicking maybe :)

> Naturally, please let know if there are other things like this.

What I was about, is that the sentence implies that what's *right after*
is all the changelog of the release, which is not right.
I've committed a change to the template, could you please check it out
whether it looks alright to you?

-- 
regards,
            Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Please review the draft for week 126's blog post

[Mattia Rizzolo]

Hi Chris!

On Sun, Sep 24, 2017 at 09:09:49AM +0100, Chris Lamb wrote:
> Please review the draft for week 126's blog post:
> 
>   https://reproducible.alioth.debian.org/blog/drafts/126/


I'm writing this here instead of committing directly, as I think it's
something that would be better fixed in the template.

I already had to do something similar in e222b3a and fd352f9 for
example.  The point being, that sentence about diffoscope seems to imply
that's all that went into release, which ain't true.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

package uploaded to our repo

[Mattia Rizzolo]

https://reproducible.alioth.debian.org/debian/gcc-7_7.2.0-10.0+really6~reproducible1.dsc
 has just been uploaded to 
https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#876140: strip-nondeterminism: log which handlers "strip-nd"s a file

[Mattia Rizzolo]

Package: libfile-stripnondeterminism-perl
Version: 0.038-1
Severity: wishlist

Since 0.030 strip-nd prints a log when fixing a file, like
|   dh_strip_nondeterminism
|Using 1505769410 as canonical time
|Normalizing debian/libtse3-dev/usr/lib/x86_64-linux-gnu/libtse3.a


I'd find it handy (even if it might be obvious for most cases) to print
the name of the handler that does the normalization.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#875324: diffoscope: Increased number of timeouts in recent versions?

[Mattia Rizzolo]

On Mon, Sep 11, 2017 at 04:33:55PM +0100, Chris Lamb wrote:
> One theory I've just thought of is that we are seeing more timeouts
> simply because we have seen a larger number of GCC uploads recently.
> 
> This not only produce either more diffoscope outputs in the first
> place (as it makes packages unreproducible), the ones that it does
> create are quite large.

That's certainly true.  After the gcc uploads I always had to reschedule
all packages built in the previous day with an unpatched GCC that also
were unreproducible, to weed out false positive; and not to say that
before those uploads the builds were hugely different due to build paths
variation.  So there were generally more diffoscope runs (which also
means more `objdump` processes, which tends to be heavy on the CPU),
which could just lead to a relevant increase of the general system load,
leading to a general slowness and also causing more "diffoscope
timeouts".

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#875280: diffoscope: ValueError: Unable to parse diff headers

[Mattia Rizzolo]

 
from_command
**kwargs
  File "/usr/lib/python3/dist-packages/diffoscope/difference.py", line 158, in 
from_feeder
unified_diff = diff(feeder1, feeder2)
  File "/usr/lib/python3/dist-packages/diffoscope/diff.py", line 252, in diff
return run_diff(fifo1_path, fifo2_path, fifo1.end_nl_q, fifo2.end_nl_q)
  File "/usr/lib/python3/dist-packages/diffoscope/tools.py", line 87, in 
tool_check
return fn(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/diffoscope/diff.py", line 175, in 
run_diff
parser.parse()
  File "/usr/lib/python3/dist-packages/diffoscope/diff.py", line 71, in parse
self._action = self._action(line.decode('utf-8', errors='replace'))
  File "/usr/lib/python3/dist-packages/diffoscope/diff.py", line 90, in 
read_headers
raise ValueError('Unable to parse diff headers: %r' % line)
ValueError: Unable to parse diff headers: 'diff: error while loading shared 
libraries: libc.so.6: cannot open shared object file: No such file or 
directory\n'


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Outreachy 15 for Reproducible Builds

[Mattia Rizzolo]

Hi!

So, Debian after all will partecipate in round 15!

I've created the project page, basically copy-pasting the previous one:
https://wiki.debian.org/Outreachy/Round15/Projects/ReproducibleBuildsOfDebi=
an

If you are willing to mentor/co-mentor for this round please move your
name to the relevant line, I kept the last confirmed co-mentors in the
page in a separated line.

Also please read the whole page again, and commit directly any
modification you'd find an improvement.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [disorderfs] 04/06: Update to latest Standards-Version; no changes required

[Mattia Rizzolo]

On Mon, Aug 21, 2017 at 05:39:10PM +, Ximin Luo wrote:
> Update to latest Standards-Version; no changes required


Actually, a change was required:

> --- a/debian/control
> +++ b/debian/control
> @@ -3,7 +3,7 @@ Maintainer: Reproducible builds folks 
> <reproducible-builds@lists.alioth.debian.o
>  Uploaders: Andrew Ayer <a...@andrewayer.name>, Chris Lamb <la...@debian.org>
>  Section: utils
>  Priority: extra
^^^

> -Standards-Version: 3.9.8
> +Standards-Version: 4.0.1

That's obsoleted with policy 4.0.1.


BTW, please also add your key to debian/upstream/signing-key.asc, bonus
for using misc.git/dump-keys.sh which I personally like quite a lot over
the usual gpg "dumb dump" :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Bug#844431: Revised patch: seeking seconds

[Mattia Rizzolo]

On Tue, 15 Aug 2017, 11:02 p.m. Adrian Bunk  wrote:

> Tracker:
> https://tracker.debian.org/pkg/hsqldb1.8.0
> "Does not build reproducibly during testing"
>

And indeed it's not reproducible according to policy: it's storing the
build user at the very least.

>
> Let's look at the mdds package, that has red unreproducible entries in
> the maintainer dashboard:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mdds.html
>
> mdds is unreproducible only in sid since more things (including the
> build path) are varied there. The information behind "differences"
> confirms that the build path is the only issue.
>
> According to policy, mdds is reproducible.
>

And indeed its unreproducibility is not reported in tracker and ddpo (DMD
does because it's using a source data that includes everything, not just
the state we want to push.  But then, DMD has a tendency to show *lots* of
things, if you disagree with it, please take it to the DMD maintainer, not
us).

Unless policy is supposed to be completely detached from reality,
> the criteria for claiming in various places that a package is
> unreproducible have to match the policy definition of reproducibility.
>

IMHO, you are arguing about a non existent issue.  I believe we are always
being reasonable, otherwise I'd like to ask you to point us to actual
situation where we could have acted better.  Yes, I'm aware of the
src:libreoffice case.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Revised patch: seeking seconds

[Mattia Rizzolo]

On Sun, 13 Aug 2017, 6:15 a.m. Stuart Prescott,  wrote:

> Policy is not a stick but policy can document where we want to be,
> particularly when we are talking about standard practice. It is already
> standard practice that packages build reproducibly with things like build-
> path variation -- we have upwards of 80% of the archive doing that.
>

I want to remember to you all that said ~80% is achieved only through a
patched dpkg and GCC.  At the very least a specifically patched compiler
with a patch still in heated discussion upstream for integration should not
be required, before considering build paths such important thing to require
reproducibility despite it.

(Not commenting on the other parts of the mail, but good points there)
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Requsting help: reproducibility regressions in pwgen and e2fsprogs?

[Mattia Rizzolo]

On Wed, Aug 09, 2017 at 11:36:55PM -0400, Theodore Ts'o wrote:
> Yet both seem to be broken, and with pwgen, it looks like it's being
> the debugging pathname has somehow leaked into the ELF / debugging
> information:

That's actually our fault, sorry if it leaked off to you.  In unstable
we are experimenting with build path variation, and that causes
unreproducible results unless a patched gcc (coupled with a patched
dpkg) is in use.  We aren't setting any block, so every time a new gcc
is uploaded to the regular archive it overwrites our version…

I've scheduled both pwgen and e2fsprogs for rebuild now, thye should
turn sunny soon.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#871413: diffoscope: AssertionError with cups/2.2.4-3 in unstable/amd64

[Mattia Rizzolo]

Package: diffoscope
Version: 85
Severity: important

As seen in tests.reproducible-builds.org today:

Mon Aug  7 15:30:34 UTC 2017  I: diffoscope 85 will be used to compare the two 
builds:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 396, in main
sys.exit(run_diffoscope(parsed_args))
  File "/usr/lib/python3/dist-packages/diffoscope/main.py", line 376, in 
run_diffoscope
PresenterManager().output(difference, parsed_args, has_differences)
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/formats.py", line 
106, in output
data['klass'].run(data, difference, parsed_args)
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/html/html.py", 
line 713, in run
jquery_url=parsed_args.jquery_url,
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/html/html.py", 
line 705, in output_html
self.output_difference(ctx, difference)
  File "/usr/lib/python3/dist-packages/diffoscope/presenters/html/html.py", 
line 615, in output_difference
assert node is difference
AssertionError


(I haven't tried to reproduce it nor anything)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#871244: diffoscope: support keybox files with kbxutil

[Mattia Rizzolo]

Hi dkg!

On Mon, Aug 07, 2017 at 02:03:13AM -0400, Daniel Kahn Gillmor wrote:
> The gnupg-utils package (currently only in experimental, but hopefully
> soon to be moved to unstable) ships kbxutil, which should provide
> sufficient textual diffs to get a better hint at the changes.
> 
> in debian stable, kbxutil used to be shipped in the gnupg package
> itself, but depending on gnupg itself will pull in the whole suite
> (including per-user daemons like gpg-agent and dirmngr, which aren't
> necessary for the public data manipulation needed by diffoscope), so
> gnupg-utils is probably a better way to go.

As you know we/I regularly backport diffoscope to Debian stable, so we
care about having those tools available there as well.
So, do you plan on making gnupg-utils available in stretch-backports
(with all the ongoing maintenance that such choice entails) or do you
think that having an alternate build-dependency+recommends is a way to
go here (possibly with a version restriction, e.g.
gnupg-utils | gnupg (<< 2.1.21-4~)
)?

I'd like to avoid having a delta between buster and stretch-bpo, at
least not this early in the development cycle..


Also, do you plan on sending a patch for diffoscope? :D

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: sbuild: please add the srebuild sbuild wrapper to reproduce builds

[Mattia Rizzolo]

On Tue, Aug 01, 2017 at 07:27:36PM +0200, Johannes Schauer wrote:
> this bug has been listed in the "NMU campaign" email on d-devel.  But I wonder
> how it ended up there.

That's just an UDD query…  But I wonder whether this bug should be
tagged as "infrastructure" (which would have avoid it being listed)...

> fix for this is still blocked by another bug (#802241) which is not on the NMU
> list,

umh… that's weird, that one definitly should be in the list (even if
clearly we don't want to NMU dpkg!)

udd=> select * from bugs_usertags where id=802241;
email|tag|   id   
-+---+
 reproducible-builds@lists.alioth.debian.org | toolchain | 802241
(1 row)

guess there is a bug in my SQL query (on top of the bug_list file
attached to the d-d mail)

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: NMU campagin

[Mattia Rizzolo]

On Wed, Jul 26, 2017 at 02:32:50PM +0200, Mattia Rizzolo wrote:
> Please review it and let's discuss here the bits you do not agree about
> the plan.

Alright, so everybody liked the plan and only wording changes happened.

ISTM that there are actually fewer packages/bugs than what I thought,
only 404 bugs reduced to 348 when filtering for the "older than 6
months" thing... but well, let's get those down as well :)

> Also, I haven't written it there, but I'd like to take this occasion to
> also upload changes ragarding other projects:
>  * multi-arch hints, as found in tracker.d.o
>  * crossbuild and bootsrap patches, as filed in the bts by helmut
>  * MIA uploaders removal, as filed in the bts
>  * some depraction bugs, like the recent automake1.11 ones (but there
>are more, like several debhelper-related)
> I think a campagin like this where we are probably going to upload
> hundreds of packages to be a great chance at tackling those things as
> well.

I hope you agree as well on this :)

FWIW, I plan to give until next week to see if anybody screams before
starting myself ^^

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

NMU campaign for Reproducible Builds patches

[Mattia Rizzolo]

Hi people,

As we mentioned in our recent report[0], we have realised just how
many of the patches we have submitted[1] have been regrettably
unacknowledged or otherwise have not uploaded to Debian.

That's why are planning a NMU campaign to lower the number of open
reproducible bugs.  We have already NMUed packages in the past (notably
for packages in the essential set) but we have mostly left maintainers
to pick up the patches at their own pace up to now.

At the end of this "campaign" we expect to see a significant drop in
the number of unreproducible packages as we are talking about roughly
300 packages here which, whilst being only less than a third of the
unreproducible packages in Buster, contains several "toolchain"
packages, affecting more than themselves.
Also, whilst we hope this campaign will have a huge impact, we're also
doing it to better be be able to focus on the remaining —harder—
unreproducible packages.

Naturally, we promise to follow the NMU rules[2] in particular
regarding the DELAYED queue: we plan to do all of our uploads for the
wishlist bugs (the vast majority of them) to DELAYED/15.

Also, for now we are going to target only bugs filed more than 6 months
ago; attached is a list of the affected bugs, and a dd-list of affected
packages.
If you do not wish for us to upload your packages, please consider
reviewing and possibly uploading our patches as soon as possible, or
leave a message in the bug report stating so.

We currently plan to start sometime during DebConf (or DebCamp),
without any specific priority or rate.


Best wishes,
   Mattia Rizzolo
   Chris Lamb
   Holger Levsen


PS: no, this time Jenkins will not do anything, all the NMU work will
be carried out by humans!


[0] https://lists.debian.org/debian-devel-announce/2017/07/msg4.html
[1] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=reproducible-builds@lists.alioth.debian.org;exclude=pending:done
https://tests.reproducible-builds.org/debian/index_bugs.html
[2] https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu


-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
Adam Conrad <adcon...@0c3.net>
   initramfs-tools (U)

Adrian Knoth <a...@drcomp.erfurt.thur.de>
   libffado (U)

Agustin Henze <t...@debian.org>
   doit

Al Stone <a...@debian.org>
   libevocosm

Alastair McKinstry <mckins...@debian.org>
   console-data

Alberto Capella Silva <alberk...@gmail.com>
   tcpreen

Alejandro Garrido Mota <alejan...@debian.org>
   cclive

Alejandro Garrido Mota <garridom...@gmail.com>
   libquvi

Alen Zekulic <a...@nms.hr>
   the

Ales Zabala Alava (Shagi) <sh...@gisa-elkartea.org>
   txt2tags (U)

Alessio Treglia <ales...@debian.org>
   idjc (U)
   masscan
   tsdecrypt (U)

Alexander Wirt <formo...@debian.org>
   asciidoc (U)
   file-rc (U)
   iproute2 (U)
   keepalived

Alexandre Dantas <e...@alexdantas.net>
   nsnake
   snake4

Andrea Colangelo <war...@ubuntu.com>
   tennix

Andreas Barth <a...@not.so.argh.org>
   netpbm-free

Andreas Beckmann <a...@debian.org>
   module-assistant (U)

Andreas Henriksson <andr...@fatal.se>
   iproute2 (U)

Andreas Tille <ti...@debian.org>
   mc (U)

Andrew Shadura <andre...@debian.org>
   aspell-sk (U)

Andrew Starr-Bochicchio <a...@debian.org>
   libgtk2-appindicator-perl (U)

Andrey Rahmatullin <w...@wrar.name>
   hibernate

Anibal Monsalve Salazar <ani...@debian.org>
   elida
   libtext-charwidth-perl
   mpack
   pciutils
   sensible-utils
   ssmtp
   uswsusp (U)

Anselm Lingnau <ling...@debian.org>
   abcm2ps

Ansgar Burchardt <ans...@debian.org>
   cclive (U)
   libquvi (U)
   quvi

Antoine Beaupré <anar...@debian.org>
   bugs-everywhere (U)

Anton Zinoviev <an...@lml.bas.bg>
   console-data (U)

Anton Zinoviev <zinov...@debian.org>
   console-setup (U)

Antonio Radici <anto...@dyne.org>
   libhtml-lint-perl (U)

Antonio Terceiro <terce...@debian.org>
   goaccess (U)
   mailman-api

Apollon Oikonomopoulos <apoi...@debian.org>
   python-hiredis (U)

Ari Pollak <a...@debian.org>
   gtkspell

Aurelien Jarno <aure...@debian.org>
   fonts-dustin (U)
   openhackware (U)

Axel Beckert <a...@debian.org>
   amora-server
   zsh (U)

Barak A. Pearlmutter <b...@debian.org>
   bbdb (U)
   jacal

Bartosz Fenski <fe...@debian.org>
   reaver

Bastien Roucariès <ro...@debian.org>
   imagemagick (U)

Ben Hutchings <b...@decadent.org.uk>
   initramfs-tools (U)
   kernel-handbook (U)

Ben Wong <b...@wongs.net>
   zssh

Benda Xu 

Status update from the Reproducible Builds project

[Mattia Rizzolo]

Contacts


For Debian-related queries, we are reachable via mail at
reproducible-builds@lists.alioth.debian.org and we hang out in IRC in
#debian-reproducible on the OFTC network.

For general purpose queries (not strictly related to Debian) our
channels are rb-gene...@lists.reproducible-builds.org [3] and
#reproducible-builds on the OFTC network.


Thanks
==

We want to thank all the entities that helped our endeavour.

In no particular order:
 * Profitbricks — https://profitbricks.com — for sponsoring the x86 VMs
   our CI runs on, not only for Debian, but also for other projects
 * Codethink — https://codethink.co.uk — for sponsoring the arm64 nodes
 * Core Infrastructure Initiative — https://coreinfrastructure.org — for
   sponsoring some us to work on the Reproducible Builds
 * Linux Foundation — https://linuxfoundation.org — for sponsoring our
   meetups and some more
 * Debian — https://debian.org — for sponsoring some of the armhf
   equipment and partially covering some expenses for our physical
   meetups
   
... and many others that helped us along the path.

Also many thanks to all those of you that contributed to the project,
and also those that simply merged our patches: all of you helped a lot!


Best wishes,

  for the Reproducible Builds team,
 Mattia Rizzolo
 Chris Lamb
 Vagrant Cascadian
 Holger Levsen
 Jenkins

[1] https://lists.debian.org/debian-devel-announce/2015/02/msg7.html
[2] https://reproducible-builds.org/who/
[3] https://lists.reproducible-builds.org/listinfo/rb-general
[4] https://tests.reproducible-builds.org/debian/
[5] https://tests.reproducible-builds.org/debian/stretch/
[6] at a footnote level, that's a cheat, as the stretch builds happen
without varying the build path :P  That doesn't change that it's an
impressive result considering where we started 3 years ago
[7] https://tests.reproducible-builds.org/debian/stats_bugs_sin_ftbfs_state.png
[8] https://tests.reproducible-builds.org/debian/stats_bugs_sin_ftbfs.png
[9] https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles
[10] https://wiki.debian.org/ReproducibleBuilds/BuildinfoInfrastructure
[11] https://manpages.debian.org/unstable/dpkg-dev/deb-buildinfo.5.en.html
[12] https://bugs.debian.org/763822
[13] https://bugs.debian.org/862073
[14] https://debconf17.debconf.org/talks/91/
[15] Renamed from "debbindiff" to remove the "deb" part, as it was made
 Debian-agnostic.
[16] https://bugs.debian.org/844431
[17] https://tests.reproducible-builds.org/debian/unstable/index_dd-list.html

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#866120: diffoscope: please add an xml comparator

[Mattia Rizzolo]

On Fri, Jul 21, 2017 at 10:48:07AM +0100, Chris Lamb wrote:
> … And I've now also merged the code into our Git repo. Thanks!

Did you both go through
https://docs.python.org/3/library/xml.html#xml-vulnerabilities and
decided that the standard minidom was safe for our usages?

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: d-d-a draft, please review

[Mattia Rizzolo]

On Tue, 18 Jul 2017, 10:14 a.m. Chris Lamb,  wrote:

> (Just to clarify; you don't wish to mention a potential NMU campaign
> or a change to Policy? Perhaps I'm forgetting our "plan" here...)
>

That's correct.
I don't want to put in d-d-a something that could potentially be unpopular
or be the spark of any heated discussion.

The plan is to follow up to this report with our nmu proposal in d-d.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: d-d-a draft, please review

[Mattia Rizzolo]

I gently remind you of this; I plan to send it out in 2 days.

On Thu, 13 Jul 2017, 9:25 p.m. Mattia Rizzolo, <mat...@debian.org> wrote:

> On Thu, Jul 13, 2017 at 11:43:04AM -0700, Vagrant Cascadian wrote:
> > Happy to review, just let me know where the text is to review! :)
>
>
> Right, I clearly sent the wrong URL in my previous email!
> The right one:
>
> https://pad.riseup.net/p/ZqHmLV7iEP3L
>
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#868534: diffoscope: autopkgtest failure

[Mattia Rizzolo]

Source: diffoscope
Version: 84
Severity: important

Starting with version 84 a new test started to fail in autopkgtest, the
one running the tests without recommends installed

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/diffoscope/20170715_175521/log.gz

It seems to be caused by commit 037c92388ef75d5ace2d26dd85bcf7693ccf7cf6

comparators/directory: raise warning for getfacl and remove a
redundant try-clause


The important bit of the failure is

E - --- Logging error ---
E - Traceback (most recent call last):
E -   File "/build/diffoscope-84/diffoscope/comparators/directory.py", 
line 124, in compare_meta
E - differences.append(Difference.from_command(Getfacl, path1, 
path2))
E -   File "/build/diffoscope-84/diffoscope/difference.py", line 222, 
in from_command
E - feeder1, command1 = command_and_feeder(path1)
E -   File "/build/diffoscope-84/diffoscope/difference.py", line 217, 
in command_and_feeder
E - if command_excluded(command.shell_cmdline()):
E -   File 
"/build/diffoscope-84/diffoscope/comparators/utils/command.py", line 64, in 
shell_cmdline
E - return ' '.join(map(lambda x: '{}' if x == self.path else 
shlex.quote(x), self.cmdline()))
E -   File "/build/diffoscope-84/diffoscope/tools.py", line 71, in 
tool_check
E - raise RequiredToolNotFound(command)
E - diffoscope.exc.RequiredToolNotFound: getfacl
E - 
E - During handling of the above exception, another exception occurred:
E - 
E - Traceback (most recent call last):
E -   File "/usr/lib/python3.5/logging/__init__.py", line 988, in emit
E - stream.write(msg)
E - ValueError: I/O operation on closed file.


so my feeling is that it has to do with something like
https://github.com/pytest-dev/pytest/issues/14 (but there are countless
other examples on the net)

needless to say, we need to workaround this somehow.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

d-d-a draft, please review

[Mattia Rizzolo]

During the last IRC meeting we agreed on sending a "short" report to dda
as a first step for our NMU campaign.

I drafted it, and it ended up a lot longer than what I'd have liked.  So
please read it, and do any kind of rewriting/re-arrengemente you feel
like.

https://pad.riseup.net/p/reproducible-irc-meeting-10

I intend to send it out by the 20th at the latest (but happy to do
before if we manage to have it ready).

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

deleting old patched packages from our repository

[Mattia Rizzolo]

Hi gang,

In the past some people expressed concerns about deleting old packages
from our repository on alioth.  ISTR the motivation was somewhere on the
lines of "being able to reproduce old builds", or so.
That's why in the past I used to check for builds done with an older
version, reschedule those builds, and once no package had been built
with that particular version of a package move that package to
/home/groups/reproducible/htdocs/old-packages.

Currently we have a gcc-6 in our repository, making the above quite
harder, not to mention that currently querying .buildinfo is still
harder than it ought to be.

Besides, I've never heard of anybody needing those old packages to
"reproduce old builds", making the original complaint kinda moot.

ATM, the old-packages directories contains 16 GB of source and binaries
packages; I consider keeping so many unused files also disrespectful
towards the other users of a shared system like alioth's, which has been
constantly running out of space for years (and DSA "keeps" giving more
disk) and to Debian's backup system.


Therefore, I'd like to delete that directory, and also change the
"policy" to "move old packages to ../old-packages" to "delete old
packages" when they are superseded by a newer version.


Comments welcome.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#866120: diffoscope: please add an xml comparator

[Mattia Rizzolo]

Source: diffoscope
Version: 83
Severity: wishlist

Currently scribus treats XML files as regular text files.  I believe it
could be better by trying to understand them, like it's done for .json,
and provide a more smart output.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#865625: diffoscope: autopkgtest failure

[Mattia Rizzolo]

Source: diffoscope
Version: 83
Severity: important

diffoscope's "command1" test fails:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/diffoscope/20170622_131027/log.gz

=== FAILURES ===
__ test_html_visuals ___

tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_html_visuals0')
capsys = <_pytest.capture.CaptureFixture object at 0x7f5f8412dcc0>

def test_html_visuals(tmpdir, capsys):
report_path = str(tmpdir.join('report.html'))

out = run_images(capsys, '--html', report_path)

assert out == ''
body = extract_body(open(report_path, 'r', encoding='utf-8').read())
>   assert '\n\n\n\n3 
\n\n44ae426082\n\n\n\n\n\n\n'

body   = ' class="diffoscope">\n\n\n\n3 \n\n44ae426082\n\n\n\n\n\n\n'
capsys = <_pytest.capture.CaptureFixture object at 0x7f5f8412dcc0>
out= ''
report_path = '/tmp/pytest-of-debci/pytest-0/test_html_visuals0/report.html'
tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_html_visuals0')

tests/test_presenters.py:125: AssertionError
== 1 failed, 221 passed, 129 skipped in 61.54 seconds ==


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

no plans for strip-nd in stretch-backports

[Mattia Rizzolo]

Just wanted to give you an heads up: I currently do not plan on
backporting strip-nondeterminism to stretch-backports as I was doing in
jessie-backports.  I see little point in updating strip-nd there.

Please speak up if you think otherwise.


OTOH, I plan on keeping up with diffoscope.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: testing buster now

[Mattia Rizzolo]

On Mon, Jun 19, 2017 at 10:29:08AM +, Holger Levsen wrote:
> On Mon, Jun 19, 2017 at 10:04:31AM +0000, Mattia Rizzolo wrote:
> > It seems we broke the DDPO once again…
> 
> whom do we contact to get this fixed?

Techinically, we both can fix it :P
Otherwise, the usual suspect would be Christoph Berg.  I don't get why
it broke, and I don't understand what he did last time we broke it :\
And I feel sorry to ask it to fix again something that broke because we
changed slightly the API.


At least tracker.d.o seems fine.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: testing buster now

[Mattia Rizzolo]

On Mon, Jun 19, 2017 at 11:39 AM Holger Levsen 
wrote:

> We've added Buster yesterday and this broke at least the dashboard, which
> I'm
> going to fix today. If you notice any other breakage, please do tell,
> either
> in this thread or via irc.
>

It seems we broke the DDPO once again…
I don't really get why it breaks so easily, but it has been in that state
since we did s/testing/stretch/, I hoped it would fix itself with buster
but it didn't.


> Thanks to Mattia for helping me renaming "testing" to stretch on Saturday
> and
> adding buster yesterday.
>

s/Saturday/Friday/ :)
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [buildd-tools-devel] Some Debian package upgrades are corrupting rsync "quick check" backups

[Mattia Rizzolo]

On Sat, May 13, 2017 at 03:44:57PM +0100, Chris Lamb wrote:
>  a) Has anything changed in the meantime?

Yes: sbuild stopped repeating the changelog time taking it from the last
entry, and will instead generate a new timestamp based on the current
time:

  * For binNMUs, instead of copying the timestamp of the last changelog entry,
generate a new one (closes: #843773)

In version 0.73.0-1.

>  b) Will this affect stretch? If so, what do we need to do now?

Yes.
IMHO, nothing.

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#860428: reprotest: use an existing HOME in the control build

[Mattia Rizzolo]

On Sun, Apr 16, 2017 at 06:55:34PM +0200, b...@debian.org wrote:
> After several tests (and then more) I eventually tracked it to HOME
> being invariably non-existant in reprotest
> (HOME=/nonexistent/first-build and HOME=/nonexistent/second-build),
> while my normal compilation environment has an existing home (duh!).

Consider that both sbuild and pbuilder have HOME pointing to something
non-existent.

> - non-existing home: ./configure attempts to run conftest.exe, wine
>   can't create '.wine', conftest.exe fails, configure assumes:
>   checking whether we are cross compiling... yes

This feels quite buggy behaviour.  I suggest you consider this another
bug in your package.

> To detect this issue, and probably others, I'd suggest making the
> control build's HOME point to an existing directory.

By all means, I suggest instead having one build with an existent and
writable HOME, and one with a non-existent one (this leaves out the case
of an existent but not writable, though).

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#857940: diffoscope: FTBFS: test errors

[Mattia Rizzolo]

On Thu, Mar 16, 2017 at 03:40:46PM +, Chris Lamb wrote:
> Assuming this is from...
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=diffoscope=all=79=1489658432=0

yes.

> ... it appears to be caused by "graphicsmagick-imagemagick-compat"
> package being installed. With this package installed locally I can
> reproduce the test failures.

umh

> (Perhaps the/this experimental:all buildd is installing packages
> with Recommends, or a different APT pinning, or...?)

The buildds are using the aspcud sbuild resolver for experimental, this
might have something to do with that.
Anyhow, if a package causes the build to fail it should either be in
Build-Conflicts{,-Indep,-Arch}, or the package be fixed, imho (besides,
this is the same argument we brought to add those Build-Conflicts with
package failing to build with a buggy locales-all two years ago…).

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#857940: diffoscope: FTBFS: test errors

[Mattia Rizzolo]

omment: Comment 
#1\n+Comment: Comment #2\n EXIF data: \n'

tests/comparators/test_jpeg_image.py:73: AssertionError
== 2 failed, 282 passed, 15 skipped in 235.62 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest -vv -r sxX -l 
--cov=diffoscope --cov-report=term-missing --cov-report=html
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.5 returned 
exit code 13
debian/rules:29: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Moving towards a deb-buildinfo(5) Format 1.0

[Mattia Rizzolo]

On Sat, Mar 11, 2017 at 03:33:05AM +0100, Guillem Jover wrote:
> I forgot to mention two curretly pending issues, not listed previously:
> 
> * An error in dpkg-genbuildinfo caused by arch-qualified dependencies
>   on a virtual package.
> * Broken dependency recursor in dpkg-genbuildinfo

I suppose there are tracking bugs around for these.

> > So given the above, I've queued a minimal change declaring the format
> > 1.0 for dpkg 1.18.23 or .24, please shout if you see any additional
> > problem or blocker.
> 
> This has happened now, given that the above are implementation details,
> and do not really affect the format.

Thank you for all your work!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [PATCH] reproducible Debian: move cleanup and (eg.) SIGBUS errors to #-changes

[Mattia Rizzolo]

On Fri, Feb 24, 2017 at 09:35:24AM +0800, Chris Lamb wrote:
> Looking at last night's scrollback, there were more non-human messages
> on #debian-reproducible than on #debian-reproducible-changes  :)

I think something broke somewhere, but I have no idea (yet) where.
Also Reiner made me notice it some days ago:

> in #d-reproducible there are a lot of messages about finished builds.
> but i don't see any schedulings for them. are they no longer
> announced?

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [NetBSD] Can we have another run please?

[Mattia Rizzolo]

On Sun, Feb 19, 2017 at 04:56:25PM -0500, Christos Zoulas wrote:
> Thanks,

Triggered!
https://jenkins.debian.net/view/reproducible/view/Singles/job/reproducible_netbsd/143/console

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: targetcli-fb unreproducible: where's the diffoscope output gone?

[Mattia Rizzolo]

On Sat, Feb 18, 2017 at 06:12:44PM +0100, Christian Seiler wrote:
> Ah, now I understand the output. I initially thought rbuild
> was just the first build, and didn't give it too much thought
> since I didn't expect diffoscope to be called there.

rbuild is the first build + some output from the jenkins job (in the
past it also contained the second build, but we thought to split that to
a different file).

> I could work on a patch for this. Could you point me in the right
> direction? According to the wiki, you're using a modified version
> of sbuild, but the link from the wiki leads via a mailing list
> post [1] to
> 
> https://anonscm.debian.org/cgit/reproducible/sbuild.git/
> 
> which doesn't appear to exist (anymore).

We are definitly not using sbuild, which wiki did you read?
All the relevant stuff is kept in the jenkins.debian.net repository at
https://anonscm.debian.org/git/qa/jenkins.debian.net.git

What's needed would be
1) tell the db about such new build result
2) find an appropriate icon and put it in place
3) tell _html_packages.py about that new status and associate the
   icon (umh, maybe that part is in _common.py ?)
4) have _build.sh properly use that new status in the right moments
5) teach the scheduler to have a different scheduling policy for
   those packages (guess it would be "right away").

Another probably easy to deal with those status could be to just discard
the build just done and put the package back in the queue (which would
mean some other build job would pick it up right away); that's already
done for some cases, and so there is a function already in place, and
what is required to do this would be to detect the failure properly (in
the function call_diffoscope_on_changes_file, iirc) and call that
function.  All of this would be in _build.sh.

> [1] 
> https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20141229/000613.html

We are not using that (and besides, it has another goal: to build
starting from a given .buildinfo).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: targetcli-fb unreproducible: where's the diffoscope output gone?

[Mattia Rizzolo]

On Sat, Feb 18, 2017 at 05:50:25PM +0100, Christian Seiler wrote:
> On 02/18/2017 05:42 PM, Mattia Rizzolo wrote:
> > On Sat, Feb 18, 2017 at 04:55:27PM +0100, Christian Seiler wrote:
> >> but where did the link to the diffoscope output go on the
> >> website?
> > Where it is always been.
> 
> And I assume that because diffoscope failed there's no link there
> and that's why I couldn't find it?

Exactly.

> >> targetcli-fb is unreproducible in testing right now (I just
> >> noticed), and I can find the build logs + the diff of the build
> >> logs, but I can't seem to find the link to the diffoscope
> >> differences of the package:
> >>
> >> https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/targetcli-fb.html
> > 
> > Apparently diffoscope "failed" with a bus error...
> 
> Can I find that piece of information somewhere on that page?

Yes, at the bottom of the rbuild log.

> It might be a good idea to change the code behind it to check
> WIFSIGNALED(diffoscope_exit_code) and if that's the case consider
> it to be a temporary test bed error, instead of a reproducibility
> failure - which would result in just an error code.

Yes, you're totally right; it just take some work to do, it has been in
the todo for a while, but it's rare enough to not in fact be a problem
usually.
For now all situations where we're not totally sure a package is
reproducible (in our current framework), it'll be marked as unrep.

> > I just scheduled targetcli-fb/testing/amd64 to build again, I expect
> > that will mark your package as reproducible again.
> 
> Thanks!

np.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: targetcli-fb unreproducible: where's the diffoscope output gone?

[Mattia Rizzolo]

On Sat, Feb 18, 2017 at 04:55:27PM +0100, Christian Seiler wrote:
> maybe this is a case of me overlooking the obvious, but where did
> the link to the diffoscope output go on the website?

Where it is always been.

> targetcli-fb is unreproducible in testing right now (I just
> noticed), and I can find the build logs + the diff of the build
> logs, but I can't seem to find the link to the diffoscope
> differences of the package:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/targetcli-fb.html

Apparently diffoscope "failed" with a bus error...

> Could you point me in the right direction?

Not needed :)
I just scheduled targetcli-fb/testing/amd64 to build again, I expect
that will mark your package as reproducible again.

Thank you for notifying us!

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[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 compare the two 
builds:
|E: Caught signal ‘Terminated’
|Thu Feb 16 03:30:35 UTC 2017  E: otb failed to build reproducibly in 
experimental on i386.

I have yet to try to reproduce it this time (and weird, because in when
I tried before reenabling the saving artifacts it did clean up for me).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Thanks for the extra run

[Mattia Rizzolo]

On Wed, Feb 15, 2017 at 08:45:06PM +, Holger Levsen wrote:
> On Wed, Feb 15, 2017 at 03:21:44PM -0500, Christos Zoulas wrote:
> > Sorry to pester again, but can we have another run?
> 
> sure! (and you're surely not pestering! :)

Indeed you're not pestering, but I didn't notice these requests as after
reading the subjects I just ignored them
Sorry, I'll try to be more careful next time!


-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#855233: diffoscope: Crashes when comparing bad JSON on Python pre-3.5

[Mattia Rizzolo]

Control: tag -1 pending

On Wed, Feb 15, 2017 at 02:47:01PM -0500, Brett Smith wrote:
> Package: diffoscope
> Severity: normal
> Tags: upstream patch

Thank you for your bug and patch, which I merged via IRC before even
noticing this bug report :)

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [diffoscope] diffoscope commit mails

[Mattia Rizzolo]

On Tue, Feb 14, 2017 at 07:50:11PM +, Holger Levsen wrote:
> > > hm, that makes rb-commits@l.r-b.o more noisy and less specific, so maybe 
> > > we should
> > > use diffoscope-comm...@lists.reproducible-builds.org instead?
> > 
> > I don't think it wold: rb-commits is *not used* at all right now, last
> > email was on August (so I'm led to believe some post-commit hook broke
> > somewhere), and all the other things are updated much less often than
> > diffoscope.
> 
> I'm getting commits there every day, eg for diffoscope the last was:
> 
> Date: Mon, 13 Feb 2017 19:39:58 +
> From: Maria Glukhova <siamezzze-gu...@moszumanska.debian.org>
> To: reproducible-comm...@lists.alioth.debian.org, 
> diffosc...@lists.reproducible-builds.org
> Subject: [diffoscope] branch siamezzze/containers updated (5a5c341 -> 9570f1c)
> Reply-To: reproducible-builds@lists.alioth.debian.org, 
> siamezzze-gu...@users.alioth.debian.org
> List-Id: Commit messages for the Reproducible Builds project 
> 

that's a different mailing list, on alioth, reproducible-commits.
I'm talking about rb-commits, on reproducible-builds.org:
https://lists.reproducible-builds.org/listinfo/rb-commits

> > The only thing that I can think of that would clash with this would be
> > dreamed shared notes, that by definition would need to go in that
> > mailing list.
> 
> Please don't call this a dream…

sorry! ;)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: diffoscope 77 in stretch or not?

[Mattia Rizzolo]

On Mon, Feb 13, 2017 at 01:56:42PM -0800, Vagrant Cascadian wrote:
> They've always been against backporting versions not present in testing,
> but I haven't seen a response like that to what I proposed, and don't
> see it listed anywhere on:
> 
>   https://backports.debian.org/Contribute/

because it's not there so explicitly, it's implied in
|Backports are packages taken from the next Debian release (called
|"testing"), adjusted and recompiled for usage on Debian stable. Because
|the package is also present in the next Debian release, you can easily
|upgrade your stable+backports system once the next Debian release comes
|out. (In a few cases, usually for security updates, backports are also
|created from the Debian unstable distribution.)
from https://backports.debian.org/


> > (capitalized, as it happens too often that somebody wants to do it, and
> > then it causes a lot of noise in debian-backports (either IRC or ML),
> > everybody gets more annoyed, etc.)
> 
> I've seen that plenty with a version not in testing, or not in unstable,
> etc. but not noticed any firestorms around packages not in
> stable...

I don't want to search for them, but I'm pretty sure that I've read
emails about
* wheezy-backports versions not being what is in jessie + ~bpo70+1
  https://backports.debian.org/wheezy-backports/older/
  https://backports.debian.org/wheezy-backports/outdated/
  => https://lists.debian.org/debian-backports/2016/05/msg00069.html
* packages in backports not being in whatever+1
  https://backports.debian.org/wheezy-backports/NA/
  luckily this last list is very short.

Same can be said of jessie.
What you were trying to propose is the very same thing that a lot of
people would like to have, like us with a jenkins package...
You can try it, and most probably if they will notice they won't act
just because both rhonda and formorer are quite busy with other stuff to
keep up with enforcing the rules they decide; but if you are unlucky and
they do, I just don't want to be around.

> If, for whatever reason, it's reasonable to continue to maintain an
> older version of diffoscope in stable, the above two points are pretty
> much moot. Just wanted to spell out all the options regarding diffoscope
> and stable, but I'm not attached to any particular strategy.

I don't think it would such a burder; after all it just works, and we
have confirmed through a very coherent check (like running it against
the entire debian archive) that works pretty well.


What I'm concerned is not about having an outdated version in stable -
after all this is what all upstreams face when their package ends up in
debian… - but how to best deal with the freeze :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: diffoscope 77 in stretch or not?

[Mattia Rizzolo]

On Mon, Feb 13, 2017 at 01:32:55PM -0800, Vagrant Cascadian wrote:
> The other obvious option is to not ship a version in stretch and rely on
> stretch-backports, if diffoscope development hasn't yet settled down
> enough (will it ever) for a Debian stable release cycle...

THAT'S NOT POSSIBLE.

backports master have *always* be against such method.
If you upload something to backports you're committing to ship that in
the next stable release.


(capitalized, as it happens too often that somebody wants to do it, and
then it causes a lot of noise in debian-backports (either IRC or ML),
everybody gets more annoyed, etc.)

> How does trydiffoscope fit into the picture? Is it sufficiently isolated
> that the heavy lifting offloaded to a network service is more
> maintainable for a stable release?

It's a difference source package, with a difference schedule, etc.  How
does it fit in this topic?  :)

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: diffoscope 77 in stretch or not?

[Mattia Rizzolo]

On Tue, Feb 14, 2017 at 09:45:41AM +1300, Chris Lamb wrote:
> Let's first try an unblock as that's cleaner and less hassle.

I agree, would you proceed to file the unblock?  As I said, I'm not up
for it myself for this case¹ :)



Then, if the unblock is accepted, I'd say we should either freeze
diffoscope development too, or stop uploading to unstable (or we can
continue development in git only in a non-master branch, release only
critical bugs if we ever find them).


¹ it's really only because I asked too many already, including huge ones
  like one for a new inkscape upstream release, and I don't want to push
  too much with my name ^^
-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: diffoscope 77 in stretch or not?

[Mattia Rizzolo]

On Tue, Feb 14, 2017 at 09:38:51AM +1300, Chris Lamb wrote:
> I didn't decide anything at all; I was enjoying the coding, adding
> features, tests, squashing bugs...

Heh :)

> (However, whatever version ends up in stretch will surely become pretty
> outdated that we will be sending people to Backports within a few
> months anyway, so I'm not overly concerned about this.)

Yeah, sure.  I'm surely going to keep up backporting as soon as
stretch-backports is a thing anyway.

What do you think we should do to fix the RC in stretch?  It's IMHO
either convince the RT of making v77 migrate, or propose a t-p-u.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

diffoscope 77 in stretch or not?

[Mattia Rizzolo]

So, today I uploaded diffoscope v77, fixing the security bug introduced
in v67 (in stretch), plus hopefully fixing for good the tests.

The diff between v67 and v77 is *huge*, this is according to git:
 161 files changed, 4247 insertions(+), 1324 deletions(-)

For a project the size of diffoscope is quite astonishing, IMHO :)

The problem lies on the Debian freeze now in effect: what do we want to
do?
I do not feel confortable asking the release team for an exception,
considering, I've asked them a lot already, for some controversial
things too; so if some of you thinks it should, I invite you to go and
file the unblock request.

The question is also specifically for Chris: what did you plan on to do
with diffoscope in regard to Debian's stretch when you decided to work
on it and commit everything to master *and* upload it to the Debian's
unstable?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#855060: unblock: strip-nondetermism/0.031-1

[Mattia Rizzolo]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Dear release team,

Chris updated strip-nd in unstable.
Keep in mind that even if it is made as a non-native source package, we
are upstream for it.
These are the relevant changes:

strip-nondeterminism (0.031-1) unstable; urgency=medium

  * Don't test for stat(2) blksize and blocks; they are filesystem-specific and
we are already checking the pre- and post-processing contents anyway.
(Closes: #854937)

 -- Chris Lamb <la...@debian.org>  Mon, 13 Feb 2017 17:41:27 +1300

strip-nondeterminism (0.030-1) unstable; urgency=medium

  * Print log entry when fixing a file. (Closes: #777239)
  * Run our entire testsuite in autopkgtests; `perl -MExtUtils::Command::MM
-MTest::Harness` was ignoring all but the first argument. (Closes: #852517)
  * Use error() from Dh_Lib.pm over manual die().
  * Add watch file with cryptographic signature verification.
  * Add documentation regarding uploading a signed tarball.
  * Add myself to AUTHORS and debian/copyright.

 -- Chris Lamb <la...@debian.org>  Thu, 09 Feb 2017 22:11:16 +1300


Now, I don't know whether he aimed these changes for stretch or not, but
I do believe they would make a good addition.

Either way I'll leave the decision to you, you can find attached a
debdiff between testing and unstable.

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for strip-nondeterminism-0.029 strip-nondeterminism-0.031

 Makefile.PL |5 ++
 README  |   10 +
 bin/dh_strip_nondeterminism |8 +++-
 bin/strip-nondeterminism|9 +++-
 debian/changelog|   20 ++
 debian/copyright|1 
 debian/tests/control|2 -
 debian/upstream/signing-key.asc |   76 
 debian/watch|2 +
 lib/File/StripNondeterminism.pm |2 -
 t/fixtures.t|4 +-
 11 files changed, 129 insertions(+), 10 deletions(-)

diff -Nru strip-nondeterminism-0.029/bin/dh_strip_nondeterminism 
strip-nondeterminism-0.031/bin/dh_strip_nondeterminism
--- strip-nondeterminism-0.029/bin/dh_strip_nondeterminism  2016-12-22 
11:52:33.0 +0100
+++ strip-nondeterminism-0.031/bin/dh_strip_nondeterminism  2017-02-13 
05:40:46.0 +0100
@@ -79,10 +79,13 @@
$File::StripNondeterminism::canonical_time = 
str2time($dh{DATE});
}
 
+   verbose_print("Using $File::StripNondeterminism::canonical_time as 
canonical time");
+
foreach (@nondeterministic_files) {
my ($path, $normalize) = @$_;
+   verbose_print("Normalizing $path");
eval { $normalize->($path); 1 }
- or die "dh_strip_nondeterminism: $path: $@";
+ or error("$path: $@");
}
 }
 
@@ -92,8 +95,9 @@
 
 This program is a part of debhelper.
 
-=head1 AUTHOR
+=head1 AUTHORS
 
 Andrew Ayer <a...@andrewayer.name>
+Chris Lamb <la...@debian.org>
 
 =cut
diff -Nru strip-nondeterminism-0.029/bin/strip-nondeterminism 
strip-nondeterminism-0.031/bin/strip-nondeterminism
--- strip-nondeterminism-0.029/bin/strip-nondeterminism 2016-12-22 
11:52:33.0 +0100
+++ strip-nondeterminism-0.031/bin/strip-nondeterminism 2017-02-13 
05:40:46.0 +0100
@@ -29,9 +29,9 @@
 my $cmd = $0;
 $cmd =~ s/.*\///;
 my $usage
-  = "Usage: $cmd [-t|--type FILETYPE] [-T|--timestamp SECONDS] 
[--clamp-timestamp] FILENAME\n";
+  = "Usage: $cmd [-v|--verbose] [-t|--type FILETYPE] [-T|--timestamp SECONDS] 
[--clamp-timestamp] FILENAME\n";
 
-my ($filetype, $timestamp, $clamp_timestamp, $want_help, $want_version);
+my ($filetype, $timestamp, $clamp_timestamp, $want_help, $verbose, 
$want_version);
 my $getopt = Getopt::Long::Parser->new;
 $getopt->configure(qw(no_ignore_case permute bundling));
 $getopt->getoptions(
@@ -39,6 +39,7 @@
'timestamp|T=i', \$timestamp,
'clamp-timestamp!', \$clamp_timestamp,
'help|h', \$want_help,
+   'verbose|v', \$verbose,
'version|V', \$want_version
 ) or die $usage;
 
@@ -73,6 +74,7 @@
next unless $normalizer;
}
 
+   print "Normalizing $filename\n" if $verbose;
eval { $normalizer->($filename); 1 }
  or die "strip-nondeterminism: $filename: $@";
 }
@@ -126,9 +128,10 @@
 
 =back
 
-=head1 AUTHOR
+=head1 AUTHORS
 
 Andrew Ayer
+Chris Lamb
 
 =head1 COPYRIGHT
 
diff -Nru strip-nondeterminism-0.029/debian/

Bug#854937: strip-nondeterminism: autopkgtest failure on armhf

[Mattia Rizzolo]

On Sun, Feb 12, 2017 at 11:05:57PM +1300, Chris Lamb wrote:
> > Furthermore, in the log there are several other warnings
> 
> Could you clarify?

At least these (I call them "warnings" as they don't seem to make the
whole testsuite fail).
Please have a look at the linked log for an eventual context.

| #   Failed test 't/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: blocks 
(actual number of system-specific blocks allocated on disk)'

&

| strip-nondeterminism: /tmp/aqno9kZGbh/android.apk: ignoring signed JAR file

(this is probably part of a test that makes sure we're skipping signed
JARs, but printed that way is misleading)

&

| /tmp/ZpcqZyK_a1/bug_802057.png: 1182 bytes of garbage after IEND chunk at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 152.

&

| /tmp/NsId04ASx7/huge-chunk-size.png: invalid length in 'tEXt' header at 
/usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 127.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#854937: strip-nondeterminism: autopkgtest failure on armhf

[Mattia Rizzolo]

Source: strip-nondeterminism
Version: 0.030-1
Severity: important

Ok, this test ran in Ubuntu, but I'm reporting it here anyway since
1) I have no reason to believe the enviroment there is so special
2) we want our tools to work the same everywhere.

See
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/strip-nondeterminism/20170211_170535_dac85@/log.gz

I already retried it once, and it failed the same way


|# Subtest: t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in
|ok 1 - Normalizer found for /tmp/bztBkjCh9l/vimoutliner_vo_readme_txt.gz
|ok 2 - Got expected output
|ok 3 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: dev (device number 
of filesystem)
|ok 4 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: blksize (preferred 
I/O size in bytes for interacting with the file)
|not ok 5 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: blocks (actual 
number of system-specific blocks allocated on disk)
|#   at t/fixtures.t line 79.
|#  got: '32'
|# expected: '0'
|# Looks like you failed 1 test of 11.
|
|#   Failed test 't/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in'
|#   at t/fixtures.t line 87.
|ok 6 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: mode (file mode 
(type and permissions))
|ok 7 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: nlink (number of 
hard links to the file)
|ok 8 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: uid (numeric user 
ID of file's owner)
|ok 9 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: gid (numeric group 
ID of file's owner)
|ok 10 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in: rdev (the device 
identifier; special files only)
|ok 11 - Unexpected files leftover: 
/tmp/bztBkjCh9l/vimoutliner_vo_readme_txt.gz
|1..11
|not ok 2 - t/fixtures/gzip/vimoutliner_vo_readme_txt.gz.in

(note that I mangled the output, as for some reason the "commented"
lines are reported later, even if TTBOMK the tests are not run in
parallel).


Furthermore, in the log there are several other warnings, that might be
nice to fix/hide as approprited.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

[Mattia Rizzolo]

On Sun, Feb 12, 2017 at 10:27:02PM +1300, Chris Lamb wrote:
> Technically true, but I've only uploaded a python2.7 with my
> PYTHONREVERSEDICTKEYORDER patch for amd64 so far.

I didn't notice the upload, as it was not announced because you didn't
upload the sources; please also upload the source packages (then other
people can provide builds for the other architectures, also).

> Force-pushed as 899a13de to `export-PYTHONREVERSEDICTKEYORDER-pbuilderrc`.

↑ Holger, pls?

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

[Mattia Rizzolo]

On Sun, Feb 12, 2017 at 01:18:56PM +1300, Chris Lamb wrote:
> > Umh, could you please set that variable in the pbuilderrc of the second
> > build instead of using the hooks (which I don't understand how that
> > would ever work
> 
> I just grepped for existing changes (eg. "I capture the environment"). If
> these things don't work as you claim, please could you remove them so they
> are not confusing?

I don't know, did that ever worked?  A grep for CAPTURE_ENVIRONMENT in
the text diffoscope reports returns nothing.
I'm not claiming anything, as I didn't add and tested that variation (as
I suppose whoever added it did), but with my pbuilder knowledge I'd be
very surprised if it does.

> > PS: was it you that triggered a admin password reset?
> 
> Yes. (The button is misleading, I didn't think it would actually reset
> the password but rather give me immediate ML admin access.)

Well, the button on
https://alioth.debian.org/mail/admin/?group_id=100870 says "Reset admin
password", not sure how that can be misleading.

> - write_page "env CAPTURE_ENVIRONMENTnot 
> setCAPTURE_ENVIRONMENT=\"I capture the environment\""
> + write_page "env CAPTURE_ENVIRONMENTnot 
> setCAPTURE_ENVIRONMENT=\"I capture the environment\"on 
> amd64: PYTHONREVERSEDICTKEYORDER=1"

This would be everywhere, not just amd64.
Plus, I think it would look better if added a different line on the
table, separated from CAPTURE_ENVIRONMENT.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

[Mattia Rizzolo]

On Sun, Feb 12, 2017 at 12:46:42AM +0100, Mattia Rizzolo wrote:
> On Sun, Feb 12, 2017 at 10:08:54AM +1300, Chris Lamb wrote:
> > Hi,
> > 
> > (Attachment was too large for Alioth apparently, so re-sending)
> 
> Yes (I discarded the email from the moderation queue now).

BTW, yes, remote to pull from is better anyway than a patch; anyhow, I
increased a tad the limit, as 40 KB are pretty small these days (you
sent a ~53 KB email)



PS: was it you that triggered a admin password reset?

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [PATCH] reproducible Debian: Reverse Python 2.x dict order in the second build.

[Mattia Rizzolo]

On Sun, Feb 12, 2017 at 10:08:54AM +1300, Chris Lamb wrote:
> Hi,
> 
> (Attachment was too large for Alioth apparently, so re-sending)

Yes (I discarded the email from the moderation queue now).

>   commit 02d4d20ae8eab1440b0d9fba8eda3df860d259d8
>   Author: Chris Lamb <la...@debian.org>
>   Date:   Sun Feb 12 10:03:02 2017 +1300
>   
>   reproducible Debian: Reverse Python 2.x dict order in the second build.
>   
>   Signed-off-by: Chris Lamb <la...@debian.org>
>   
>bin/reproducible_common.sh | 2 
> +-
>hosts/bbx15-armhf-rb/etc/pbuilder/rebuild-hooks/D01_modify_environment | 3 
> +++
>hosts/bpi0-armhf-rb/etc/pbuilder/rebuild-hooks/D01_modify_environment  | 3 
> +++

Umh, could you please set that variable in the pbuilderrc of the second
build instead of using the hooks (which I don't understand how that
would ever work, considering the hooks are *executed* inside the chroot,
and not sourced, so variables exported from there shouldn't be seen
during the build, in theory; does that variation even work?)

So just dump it in reproducible_build.sh, line 682 onwards.  1 line
change is better than changing dozens of files anyway, I suppose.

> Please merge from the "export-PYTHONREVERSEDICTKEYORDER" branch of
> https://github.com/lamby/jenkins.debian.net

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

participation in GSoC 2017 / Outreachy 14

[Mattia Rizzolo]

Hi folks!

As I'm sure all of you read through debian-devel-announce (and Holger's
forward here), it's again time to prepare for the summer round of our
usual outreach sessions.

https://lists.debian.org/debian-devel-announce/2017/02/msg3.html

I've made what basically is a copy-paste of our last application here:
https://wiki.debian.org/SummerOfCode2017/ProjectProposals/ReproducibleBuildsOfDebian

I intend to copy it to the Outreachy space once it's ready (also note
how that page is in the "Proposal" space, will be moved once the mentors
are confirmed).


Please read through the page, add/edit the suggested subprojects as you
see fit.

I already put Holger, Reiner, Chris and Ximin as co-mentors; please pull
yourself off if you're not available to mentor this year (well, last
round you were not "needed" after all :)).


-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: NetBSD run

[Mattia Rizzolo]

On Thu, Feb 09, 2017 at 11:31:19PM -0500, Christos Zoulas wrote:
> We fixed it now so if you can run again it will run with the new
> data, and hopefully all the repro issues should be fixed. I know
> it will run again next Thursday, but if you can kick it sooner,
> I'd really appreciate it.

Aye, aye, no need for so much excuses :)
Running at
https://jenkins.debian.net/view/reproducible/view/Singles/job/reproducible_netbsd/140/console

Enjoy!

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#854745: diffoscope: autopkgtest failures

[Mattia Rizzolo]

Control: notfound -1 65
Control: found -1 75

On Fri, Feb 10, 2017 at 01:30:24AM +0100, Mattia Rizzolo wrote:
> Version: 65

off by ten.

Yes I know v76 is out too (and still untested), but I have no reasons to
think that version fixes it.

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#854745: diffoscope: autopkgtest failures

[Mattia Rizzolo]

s_details or len(difference.details) > 0
E   AssertionError

difference = 
fixture= < 
/tmp/pytest-of-debci/pytest-0/test_dot_buildinfo_compare_non0/a/test_1.buildinfo>
has_details = True
has_null_source = True
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x7fad4939bd30>

tests/comparators/utils/nonexisting.py:32: AssertionError
_ test_differences_with_dbgsym _

dbgsym_differences = ]>]>]>]>

@skip_unless_tools_exist('readelf', 'objdump', 'objcopy')
@skip_if_binutils_does_not_support_x86()
@skip_unless_module_exists('debian.deb822')
def test_differences_with_dbgsym(dbgsym_differences):
assert dbgsym_differences.details[2].source1 == 'data.tar.xz'
bin_details = dbgsym_differences.details[2].details[0].details[0]
assert bin_details.source1 == './usr/bin/test'
assert bin_details.details[1].source1.startswith('objdump')
>   assert 'test-cases/dbgsym/package/test.c:2' in 
> bin_details.details[1].unified_diff
E   assert 'test-cases/dbgsym/package/test.c:2' in '@@ -1,14 +1,14 @@\n \n 
\n \n Disassembly of section .text:\n \n 00400400 <.text>:\n-  
400400:\t8d 47 2a  ...\n   40040d:\t48 83 e4 f0  \tand
$0xfff0,%rsp\n   400411:\t50   \tpush   %rax\n'
E+  where '@@ -1,14 +1,14 @@\n \n \n \n Disassembly of section .text:\n 
\n 00400400 <.text>:\n-  400400:\t8d 47 2a  ...\n   40040d:\t48 83 
e4 f0  \tand$0xfff0,%rsp\n   400411:\t50
   \tpush   %rax\n' = .unified_diff

bin_details = , ...delf --wide --decompress 
--hex-dump=.gnu_debuglink {} -- readelf --wide --decompress 
--hex-dump=.gnu_debuglink {} []>]>
dbgsym_differences = ]>]>]>]>

tests/comparators/test_elf.py:129: AssertionError
== 11 failed, 184 passed, 91 skipped in 60.15 seconds ==
adt-run [23:41:54]: test command1: ---]
adt-run [23:41:54]: test command1:  - - - - - - - - - - results - - - - - - - - 
- -
command1 FAIL non-zero exit status 1


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#854670: diffoscope: autopkgtest failures

[Mattia Rizzolo]

Source: diffoscope
Version: 74
Severity: important

autopkgtest still fails:
https://ci.debian.net/data/packages/unstable/amd64/d/diffoscope/20170209_062723.autopkgtest.log.gz

adt-run [06:33:34]: test command1: debian/tests/pytest
adt-run [06:33:34]: test command1: [---
= test session starts ==
platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0 -- 
/usr/bin/python3
cachedir: .cache
rootdir: /tmp/autopkgtest-virt-lxc.shared.u49x4h5t/downtmp/autopkgtest_tmp, 
inifile: 
collecting ... collected 259 items / 2 errors

=== short test summary info 
ERROR tests/comparators/test_debian.py
ERROR tests/comparators/test_elf.py
 ERRORS 
__ ERROR collecting tests/comparators/test_debian.py ___
ImportError while importing test module 
'/tmp/autopkgtest-virt-lxc.shared.u49x4h5t/downtmp/autopkgtest_tmp/tests/comparators/test_debian.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/_pytest/python.py:418: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python3/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:216: in load_module
py.builtin.exec_(co, mod.__dict__)
tests/comparators/test_debian.py:89: in 
@skip_unless_module_exists('debian.deb822')
tests/comparators/utils/tools.py:66: in skip_unless_module_exists
importlib.util.find_spec(name) is None,
/usr/lib/python3.5/importlib/util.py:88: in find_spec
parent = __import__(parent_name, fromlist=['__path__'])
E   ImportError: No module named 'debian'
 ERROR collecting tests/comparators/test_elf.py 
ImportError while importing test module 
'/tmp/autopkgtest-virt-lxc.shared.u49x4h5t/downtmp/autopkgtest_tmp/tests/comparators/test_elf.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/_pytest/python.py:418: in _importtestmodule
mod = self.fspath.pyimport(ensuresyspath=importmode)
/usr/lib/python3/dist-packages/py/_path/local.py:662: in pyimport
__import__(modname)
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:216: in load_module
py.builtin.exec_(co, mod.__dict__)
tests/comparators/test_elf.py:123: in 
@skip_unless_module_exists('debian.deb822')
tests/comparators/utils/tools.py:66: in skip_unless_module_exists
importlib.util.find_spec(name) is None,
/usr/lib/python3.5/importlib/util.py:88: in find_spec
parent = __import__(parent_name, fromlist=['__path__'])
E   ImportError: No module named 'debian'
!!! Interrupted: 2 errors during collection 
=== 2 error in 0.91 seconds 
adt-run [06:33:36]: test command1: ---]
adt-run [06:33:36]: test command1:  - - - - - - - - - - results - - - - - - - - 
- -
command1 FAIL non-zero exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#854593: diffoscope: autopkgtest fail

[Mattia Rizzolo]

On Thu, Feb 09, 2017 at 12:42:36PM +1300, Chris Lamb wrote:
> Ah, my "minimal" chroot had xxd installed.

Yes, autopkgtest's chroots are *very* minimal :)

Thanks for tracking this down!

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#854593: diffoscope: autopkgtest fail

[Mattia Rizzolo]

Source: diffoscope
Version: 71
Severity: important

71 fails the test run without any optional package ("Recommends")
installed:

https://ci.debian.net/data/packages/unstable/amd64/d/diffoscope/20170208_091322.autopkgtest.log.gz

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: [diffoscope] diffoscope commit mails

[Mattia Rizzolo]

On Tue, Feb 07, 2017 at 06:04:35PM +, Holger Levsen wrote:
> > > Shouldn't we drop the mails to 
> > > reproducible-comm...@lists.alioth.debian.org
> > > and just send them to diffosc...@lists.reproducible-builds.org?!
> > IMHO, we shouldn't email them to diffoscope@l.r-b.o either, but instead
> > rb-commits@l.r-b.o, same for the other non-debian specific stuff.
> 
> hm, that makes rb-commits@l.r-b.o more noisy and less specific, so maybe we 
> should
> use diffoscope-comm...@lists.reproducible-builds.org instead?

I don't think it wold: rb-commits is *not used* at all right now, last
email was on August (so I'm led to believe some post-commit hook broke
somewhere), and all the other things are updated much less often than
diffoscope.
The only thing that I can think of that would clash with this would be
dreamed shared notes, that by definition would need to go in that
mailing list.


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: diffoscope commit mails

[Mattia Rizzolo]

[ dropping r-b-commits@l.a.d.o and using instead r-b@l.a.d.o; the former
is very much not a discussion channel ]

On Tue, Feb 07, 2017 at 10:50:58AM +, Holger Levsen wrote:
> currently diffoscope git commit notification mails are being sent to two
> mailinglists, reproducible-comm...@lists.alioth.debian.org and
> diffosc...@lists.reproducible-builds.org, for AFAICS historic reasons only.

Yes.

> Shouldn't we drop the mails to reproducible-comm...@lists.alioth.debian.org
> and just send them to diffosc...@lists.reproducible-builds.org?!

IMHO, we shouldn't email them to diffoscope@l.r-b.o either, but instead
rb-commits@l.r-b.o, same for the other non-debian specific stuff.

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Please review the draft for week 92's blog post

[Mattia Rizzolo]

On Sun, Jan 29, 2017 at 08:11:57PM +, Chris Lamb wrote:
>   https://reproducible.alioth.debian.org/blog/drafts/92/
> 
> Feel free to commit any changes directly to drafts/92.mdwn in Git:
> 
> https://anonscm.debian.org/git/reproducible/blog.git/
> 
>   $ date -d 'Mon Jan 30 23:59:00 UTC 2017'

I have no time for this, but please add something reporting about the
recent changes that happened in dpkg to the buildinfo generator (i.e.
read the dpkg changelog).


(with thanks from guillem whom reminded me of this…)
-- 
regards,
            Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Some Debian package upgrades are corrupting rsync "quick check" backups

[Mattia Rizzolo]

On Mon, Jan 30, 2017 at 02:01:10PM +0200, Henrik Ahlgren wrote:
> On Sat, 2017-01-28 at 23:00 +0100, Lupe Christoph wrote:
> > On Saturday, 2017-01-28 at 14:51:19 +, Holger Levsen wrote:
> > > On Sat, Jan 28, 2017 at 03:04:56PM +0100, Daniel Reichelt wrote:
> > > > I highly suspect this stems from packages' rules files supporting
> > > > reproducible builds.
> > 
> > > I rather think this is due to binNMUs not modifying debian/changelog…
> > > (in the source package while it's modified in the binary packages…)
> > 
> > This is completely counter intuitive. I'm using rsnapshot to backup a
> > few private machines. I will have to set up separate rsnapshots for
> > those parts of the backup that suffer from this , to avoid
> > bogging down the data parts by unnecessary checksum calculations.
> > 
> > This problem may affect many other backups too. Did anybody research
> > backup programs before this  was introduced to Debian?
> 
> Would reproducible-builds@lists.alioth.debian.org be the correct mailing
> list to discuss this?

Not really, because that has been done in sbuild since long before the
reproducible builds project became active: 0.62.2-1, Tue, 05 Apr 2011:
- Improve binNMU handling to permit binNMUs for multiarch packages
  (Closes: #620112).  Currently, binary NMUs use the current date
  in the new changelog entry, but co-installable packages require
  an identical changelog.  To avoid this, take the date from the
  previous changelog entry to ensure the same date for all binNMUs.
  Thanks to Anders Kaseorg for this patch.

And, incidentally, this has been kind of reverted in 0.73.0-1 (Sat, 24
Dec 2016) after a fairly long and annoying discussion in debian-devel:
  * For binNMUs, instead of copying the timestamp of the last changelog entry,
generate a new one (closes: #843773)


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#852013: Patch to prevent segfaults on signal

[Mattia Rizzolo]

On Sat, Jan 28, 2017 at 04:35:47PM -0500, Brett Smith wrote:
> I'm not complaining, just checking: my patch got reverted about twenty
> minutes after it got committed to master.  Are you sure you were testing
> in that time before it got reverted?

Yes.
Chris reverted it after my email.

> Earlier I was able to reproduce what was in your original report: same
> basic flow of debug messages, same issue of tempfiles not going away.
> The only difference I saw was that it segfaulted.  I thought maybe that
> wasn't included in the original report just because your shell didn't
> report it, or something like that.

As I wrote somewhere (but only on IRC maybe), I also noticed segfaults
while trying to reproduce it, but not so often.  It appeared to not
cleanup also when it didn't segfault.

> And it seemed to explain why the
> cleanup code wasn't running: the whole Python process was dying before
> it could get to the `finally` block that does the cleanup.  On my host,
> fixing this segfault and fixing the cleanup code went hand in hand,
> because now diffoscope could reliably get to the cleanup code.


Yesterday I tried several times with what was HEAD (with your patch) and
before that, and appeared to not clean up in both cases, without
sefualt reported.  Today it seem to always clean up with your patches
but always segfault (which is weird, as it never segfaulted reliably for
me) without.  meh.
OTOH, I now realized that somehow my shell might have eaten the
"Segmentation fault" message (although it doesn't do that usually), as I
just had a run terminated with code 139 without said message.
I'll report back once it does not segfault and not clean up.


BTW, I've committed your patche in a separated branch, as it deserves
to get in at some point (pity also because Debian is now freezing, and
we need to get the package into stretch, etc...

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#852015: diffoscope: Suggested improvements to --help output and CONTRIBUTING

[Mattia Rizzolo]

Control: found -1 69
Control: tag -1 pending

On Fri, Jan 20, 2017 at 01:21:28PM -0500, Brett Smith wrote:
> I've attached a series of patches to improve documentation, in the output of
> `--help` and CONTRIBUTING.

Thank you!
I've applied all of them (and then improved a bit more CONTRIBUTING, if
you want to look at it again/more).

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Bug#852013: diffoscope: (possible) regression in tempfile clean up

[Mattia Rizzolo]

package: diffoscope
version: 69
severity: important

If I run something like
TMPDIR=temp diffoscope --debug 1 2
where 1 and 2 are/contains two .debs containing differing elf binaries,
and I happen to interrupt it (by sigTERMing it, be it with ^C by
keyboard or by using the `timeout` command) while it's dumping the
content of the elf files, diffoscope just forgets to remove the
temporary files it created:

% mkdir temp
% TMPDIR=temp timeout 45s diffoscope --debug 1 2
2017-01-20 18:46:57 D: diffoscope.main: Starting diffoscope 69
2017-01-20 18:46:57 D: diffoscope.locale: Normalising locale, timezone, etc.
2017-01-20 17:46:57 D: diffoscope.main: Starting comparison
[……]
2017-01-20 17:56:12 D: diffoscope.comparators.utils.command: Executing objdump 
--line-numbers --disassemble --demangle --section=.plt.got 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp0ca6peha_diffoscope/./usr/lib/paraview/libvtkChartsCorePython27D.so.1
2017-01-20 17:56:12 D: diffoscope.comparators.utils.command: objdump 
--line-numbers --disassemble --demangle --section=.plt.got 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp6nkl4rq5_diffoscope/./usr/lib/paraview/libvtkChartsCorePython27D.so.1
 returned (exit code: 0)
2017-01-20 17:56:12 D: diffoscope.comparators.utils.command: objdump 
--line-numbers --disassemble --demangle --section=.plt.got 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp0ca6peha_diffoscope/./usr/lib/paraview/libvtkChartsCorePython27D.so.1
 returned (exit code: 0)
2017-01-20 17:56:12 D: diffoscope.diff: Running diff -aU7 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp4a3u3s0n/f1 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp4a3u3s0n/f2
2017-01-20 17:56:12 D: diffoscope.diff: diff -aU7 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp4a3u3s0n/f1 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp4a3u3s0n/f2: returncode 0, 
parsed True
2017-01-20 17:56:12 D: diffoscope.comparators.utils.compare: Comparing files 
< .text> and < .text>
2017-01-20 17:56:12 D: diffoscope.comparators.utils.command: Executing objdump 
--line-numbers --disassemble --demangle --section=.text 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp6nkl4rq5_diffoscope/./usr/lib/paraview/libvtkChartsCorePython27D.so.1
2017-01-20 17:56:12 D: diffoscope.comparators.utils.command: Executing objdump 
--line-numbers --disassemble --demangle --section=.text 
/home/mattia/pbuilder/result/unstable/amd64/temp/tmp0ca6peha_diffoscope/./usr/lib/paraview/libvtkChartsCorePython27D.so.1
TMPDIR=temp timeout 45s diffoscope --debug 1 2  42.34s user 7.83s system 111% 
cpu 45.006 total
% ls -1 temp|wc -l
81
%

(last line is my shell telling me how much time it took)


Now, this doesn't happen always, and in my limited testing it seemed to
happen only when interrupting objdump (??!?).  That said, it's worsening
disk space problems on jenkins, as it leaves huge files around for way
longer than usual, until garbage collected by something else.

-- 
regards,
    Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: ftbfs_due_to_semaphore_setup for qtwebengine on abel.d.o

[Mattia Rizzolo]

On Mon, Jan 16, 2017 at 11:53:10PM +0100, Sandro Knauß wrote:
> I had seen the python semaphore problem first only at reproducible-
> builds.org[0]. And I thought, that is a problem of their setup, but now I 
> also 
> get this error on abel.d.o (armhf porterbox). It is mentioned at [1], that it 
> might be a problem of permissions for /dev/shm.

I don't know anything about abel.d.o and why it might have issues (but I
can tell you that you should probably contact DSA rather than
armhf@buildd.d.o which would be the armhf buildd admins).

But for the reproducible test setup, I can tell you that these last few
days work is actually ongoing to fix the issue, Holger made several
changes to the hosts to assure /dev/shm is properly mounted, and from my
side I released a pbuilder that should Fix All The Bugs (waiting for
testing migration to happen, then I'll backport it, then we'll test if
it also fixes tests.reproducible-build.org's bugs).

-- 
regards,
        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds