View all weekly reports

Reproducible Builds: Weekly report #148

Published: Feb 27, 2018.

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

Logo and Outreachy/GSoC

Reproducible work in other projects

There were a number of blog posts related to reproducible builds published this week:

Development and fixes in Debian key packages

Norbert Preining added calls to dh_stripnondeterminism to a number of TexLive packages which should let them become reproducible in Debian (#886988).

“Y2K-bug reloaded”

As part of the work on reproducible builds for openSUSE, Bernhard M. Wiedemann built packages 15 years in the future and discovered a widespread systematic errors in how Perl’s Time::Local functions are used.

This affected a diverse set of software - including git and our strip-nondeterminism (via Archive::Zip)

grep was run on 16,896 tarballs in openSUSE’s devel:languages:perl project and 102 of them contained timegm or timelocal calls. Of those, over 30 were problematic and some more need to be analyzed:

Packages reviewed and fixed, and bugs filed

Reviews of unreproducible packages

60 package reviews have been added, 32 have been updated and 30 have been removed in this week, adding to our knowledge about identified issues.

Two new toolchain issue types have been added:

Weekly QA work

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

  • Adrian Bunk (41)
  • Andreas Beckmann (1)
  • Boyuan Yang (1) development


This week’s edition was written by Bernhard M. Wiedemann, kpcyrd, 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, Mastodon & 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