View all weekly reports

Reproducible Builds: Weekly report #152

Published: Mar 27, 2018.


Here’s what happened in the Reproducible Builds effort between Sunday March 18 and Saturday March 24 2018:

Packages reviewed and fixed, and bugs filed

diffoscope development

diffoscope is our in-depth and content-aware diff utility that can locate and diagnose reproducibility issues. This week, version 92 was uploaded to unstable by Chris Lamb. It included contributions already covered by posts in previous weeks as well as new ones from:

reprotest development

reprotest is our tool to build software and check it for reproducibility.

trydiffoscope development

trydiffoscope is a lightweight command-line tool to the try.diffoscope.org web-based version of diffoscope.

Reviews of unreproducible packages

88 package reviews have been added, 109 have been updated and 18 have been removed in this week, adding to our knowledge about identified issues.

A random_order_in_javahelper_manifest_files toolchain issue was added by Chris Lamb and the timestamps_in_pdf_generated_by_inkscape toolchain issue was also updated with a URI to the upstream discussion.

Weekly QA work

During our reproducibility testing, FTBFS bugs have been detected and reported by:

  • Adrian Bunk (66)
  • Jeremy Bicha (1)
  • Michael Olbrich (1)
  • Ole Streicher (1)
  • Sebastien KALT (1)
  • Thorsten Glaser (1)

Misc.

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


View all weekly reports

Follow us on Twitter @ReproBuilds. People & projects working on reproducible builds include: Arch Linux, Baserock, Bitcoin, coreboot, Debian, ElectroBSD, F-Droid, FreeBSD, Fedora, GNU Guix, Monero, NetBSD, NixOS, OpenEmbedded, openSUSE, OpenWrt, Qubes OS, Symfony, Tails, Tor Browser, Webconverger, Yocto Project. 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 welcome via our Git repository (instructions) or via our mailing list.