View all weekly reports

Reproducible Builds: Weekly report #191

Published: Dec 25, 2018.


Merry Christmas from everybody working on reproducible builds. 🎅 Here’s what happened in the Reproducible Builds effort between Sunday December 16 and Saturday December 22 2018:

Packages reviewed and fixed, and bugs filed

Test framework development

There were a number of updates to our Jenkins-based testing framework that powers tests.reproducible-builds.org this week by Holger Levsen including:

  • Arch Linux-specific changes:
    • Extend refresh_pattern. []
  • Debian-specific changes:
    • Adopt to new “offline nodes” syntax. []
    • Fix a bug where offline nodes were not recognised as such. []
    • Limit unrep_with_dbd_issues() to Debian architectures for now. []
  • Misc/generic changes:
    • Don’t use existing hosts as example. []
    • Add link to database schema. (Thanks for Bernhard M. Wiedemann for pointing out that was missing.) []
    • Thank the OSU Open Source Lab from Oregon State University (OSUOSL) for hosting the new amd64 nodes [] as well as add the new nodes themselves [][], perform the various networking configuration [] and other various tweaks [].
  • Various bits of build node maintenance. [][][][]

In addition, Mattia Rizzolo updated the reproducible_notes.py script to only store notes for Debian packages in the database for now. []

reproducible-builds.org website development

Chris Lamb made a huge number of updates to our reproducible-builds.org project website this week:

Finally, heinrich5991 provided two grammatical fixups to our “How to join the Salsa group” page. [][]


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


View all weekly reports

Follow us on Twitter @ReproBuilds 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 welcome via our Git repository (instructions) or via our mailing list.