View all weekly reports

Reproducible Builds: Weekly report #201

Published: Mar 5, 2019.


Here’s what happened in the Reproducible Builds effort between Sunday February 24 and Saturday March 2 2019:

diffoscope development

diffoscope is our in-depth “diff-on-steroids” utility which helps us diagnose reproducibility issues in packages. This week:

  • Chris Lamb:
    • Improved the displayed comment when falling back to a binary diff to include the file type. (#49)
    • Tidied definition of “no file-specific differences were detected” message suffix. []
    • Corrected a “recurse” typo. []
  • Vagrant Cascadian updated diffoscope in GNU Guix. []

Packages reviewed and fixed, and bugs filed

In addition, one of Chris Lamb’s previous patches for the Sphinx documentation system was merged upstream. He also updated his branch against the shadow password utility.

Test framework development

We operate a comprehensive Jenkins-based testing framework that powers tests.reproducible-builds.org. This week, Holger Levsen made the following improvements:

  • Improve the output of the Debian reproducible “SHA1” checker [], also including stats for non-reproducible binNMUs, arch:all and arch:amd64 packages [].
  • Deal with zero results in the SHA1 checker. []
  • Move SHA1 checker to osuosl173 node. []
  • Add setup_schroot_buster_diffoscope job on osuosl173 node. []
  • Node maintenance. [][][]

In addition, Mattia Rizzolo performed some armhf node maintenance. []


This week’s edition was written by Bernhard M. Wiedemann, Chris Lamb, Holger Levsen, Vagrant Cascadian & reviewed by a bunch of Reproducible Builds folks on IRC & the mailing lists.


View all weekly reports

Follow us on Twitter @ReproBuilds, Mastodon @reproducible_builds@fosstodon.org & Reddit and please consider making a donation. • Content licensed under CC BY-SA 4.0, style licensed under MIT. Templates and styles based on the Tor Styleguide. Logos and trademarks belong to their respective owners. • Patches for this website welcome via our Git repository (instructions) or via our mailing list. • Full contact info