View all weekly reports

Reproducible Builds: Weekly report #192

Published: Jan 1, 2019.

Here’s what happened in the Reproducible Builds effort between Sunday December 23 and Saturday December 29 2018:

Packages reviewed and fixed, and bugs filed

In addition, Mattia Rizzolo filed a build failure bug. website development

Chris Lamb made a huge number of updates to our project website this week:

  • Set a temporary logo for Christmas. [][]

  • Move our homepage to the new visual style. [][]

  • Split, tidy and expand footer. [][][] and link the main heading element of blog posts “back” to themselves [].

  • Move the tools, resources and events pages to new visual style. [][][][]

  • Update the support mechanisms for the weekly reports, such as dropping the migrate-blog-posts script [] as well as fixing some title handling [] [].

  • Improve a number of styles, such as blockquotes, linked headings should not have “link” styling, unpublished blog post drafts, etc. [][][]

  • Tidy and highlight the display of our sponsors. [][]

  • Add the ablity to override the entire <head> title [] and improve spacing etc. on mobile browsers [].

In addition, Arnout Engelen and Hervé Boutemy made an initial stab at documenting the JVM “buildinfo” format. [][]

Test framework development

There were a number of updates to our Jenkins-based testing framework that powers this week, including:

  • Holger Levsen updated the Coreboot support to point to the new Git repositories to new URI. []

  • Mattia Rizzolo updated the “wrong future” check for the 2019 (part of our many build variations). [][] as well as a various bits of node maintenance. [][][]

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, 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