Here’s what happened in the Reproducible Builds effort between Sunday September 30 and Saturday October 6 2018:
Yet another reminder that the fourth Reproducible Builds summit will be taking place between 11th—13th December 2018 in Paris at Mozilla’s offices. If you are interested in attending please send an email to
email@example.com. More details can also be found on the corresponding event page of our website.
Eric Myhre gave a talk titled Path-agnostic binaries, co-installable libraries, and How To Have Nice Things at All Systems Go 2018 in Berlin, Germany featuring “content addressable splays” that benefit from reproducible builds.
Bernhard M. Wiedemann wrote autoprovenance to help to understand how and where unreproducible files are created. Whilst it is meant to be distribution-agnostic it currently only works with rpmbuild-strace and as such is more useful for RPM-based distros.
Chris Lamb reviewed 35 Debian packages. In addition, 6 were updated and 15 were removed in this week, adding to our knowledge about identified issues. Chris Lamb also added two issue toolchain issues (
randomness_in_python_changelog_references) and Peter Wu updated the documentation for cmake.
Vagrant Cascadian gave an impromptu talk about reproducible builds at CAT Barcamp.
Packages reviewed and fixed, and bugs filed
Bernhard M. Wiedemann:
- bedtools (drop environment.pickle)
- bowtie2 (date, hostname)
- dealii (fixed, date / copyright year)
- gap-ace (drop date)
- gdb (includes testresults)
- gettext-runtime (date)
- gismo (CPU-detection)
- gpg2 (date from patch updating mtime)
- libcbor (bug, parallelism-race)
- llvm/clang (fix FTBFS-2030)
- obs-build (disable ext2/3/4
dir_indexto have more stable readdir)
- pocl (CPU detection)
- python-pyproj (merged, sort python glob /
- python-scipy (merged, sort glob /
- python-service_identity (workaround parallelism-induced ordering issues in
sphinx-build; found that it is not a race condition)
- vpp (fixed bug: FTBFS-j1, upstream)
- wcalc (use
- xine-ui/xine-lib (bug: filesystem ordering causes randomly missing entries)
- Chris Lamb:
- Marek Marczykowski-Górecki:
Test framework development
Arch Linux-specific changes:
- Add new page with scheduled builds.
- Add new page with the recent builds from the last day.
- Explain how many packages were scheduled.
- Delete the first build’s artifacts if the second build fails.
- Reduce the minimum date for rescheduling to 10 days.
- Add comment explaining why we might delete packages that are building.
- Shorten IRC message if longer then 256 characters.
Debian GNU/Linux-specific changes:
- Make all
arm64nodes use codethink16 as an APT proxy. (#909838)
- Allow squid access from other codethink-hosted nodes.
- Install debootstrap from
stretch-backportson the Ubuntu nodes as debootstrap
1.0.78+nmu1ubuntu1.6cannot install on
- Don’t show graphs with oldest
stretchbuilds on performance stats page anymore.
- Schedule more new packages.
- Increase log level when running
- Make all
- Now that the projects have re-joined, merge the LEDE work back in so that we only have OpenWrt tests (1, 2, 3, 4, 5, 6)
- Create a landing page at tests.reproducible-builds.org/openwrt/
- Use upstream Git repository (instead of lynxis’s fork).
- Document that every build is done under a
0022, because this is enforced by the OpenWrt build system.
- Add more console output.
- Automatically mark “sick” nodes as offline after an hour of problems, not three hours.
- Distinguish between automatically and manually offline nodes in health overview.
- Update FreeBSD test system to version 11.2.
- Update some timeouts, including increasing the timeout to 24 hours for some longer-running jobs and adding a timeout of 12 hours for general reproducible jobs & 15 minutes for healthcheck jobs.
- Be move verbose when IRC message sending fails.
This week’s edition was written by Bernhard M. Wiedemann, Chris Lamb, heinrich5991, Holger Levsen, Marek Marczykowski-Górecki, Vagrant Cascadian & reviewed by a bunch of Reproducible Builds folks on IRC & the mailing lists.