- PureOS-project - Purism Mailing Lists

Byzantium versioning
by Guido Günther 15 Dec '20

15 Dec '20

Hi, since we're dropping phone specific package for byzantium we also ought to drop `+librem5.X' in the version numbers. Matthias, what would you suggest here so that we generate higher version numbers in byzantium when backporting a package to both amber and byzantium to be consistent whith the rest of PureOS but also have a higher number than the current <upstream>-<debian-rev)pureos+librem5.<revision> Cheers, -- Guido

3 4

Bits from PureOS | opening the firehose
by Jeremiah C. Foster 04 Dec '20

04 Dec '20

Hello, Some bits from PureOS; 1. Byzantium on all the things 2. End of life for Amber? 3. EFI 1. Due to the fact that there is a new SoC / CPU in the Mini and the Librem 14, we need to move to a new kernel for these new devices. The good news is that the Byzantium kernel appears to fit our needs. The Mini that I have here is a Intel Coffee Lake i7-8565U @ 1.80GHz with 8 Cores. uname -a; "Linux 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) x86_64 GNU/Linux" /etc/os-release; VERSION_ID=10.0 VERSION_CODENAME=byzantium Everything has been working quite smoothly except for some issues around accessing our repos; https://tracker.pureos.net/T960 I have an ISO with the installer that Matthias has fixed up and we hope to have a Go / No Go decision with that image for tomorrow (Wednesday). 2. Amber should likely have a EoL date. I feel like that should be a sort of LTS style approach and say we'll support Amber for two more years. We still sell some products (Librem 15, server) with Amber still on it and enterprises expect longer support so something along those lines seems sensible. Feedback most welcome. 3. Can we deliver an installer that supports EFI? I realize this has been a goal for a while and that there is work still needed to be done for this and we have the usual resource constraints. What more needs to be done? Thank you!

2 3

PureOS Phone images
by Jeremiah C. Foster 12 Sep '20

12 Sep '20

Hi, [Feel free to reply on-list, I just wanted to make sure everyone saw this.] [Please find attached an invite to a mumble call at 16:00 CEST tomorrow.] Welcome to a thread about PureOS images for our Librem 5 phone. Let's start with Guido who knows a thing or two about the Librem 5; "I'd like to (slowly) start filling in enough of byzantium so we can build images for the phone. First candidates would be a kernel and flash-kernel. We currently keep the sources at https://source.puri.sm/Librem5/flash-kernel and https://source.puri.sm/Librem5/linux-next - i just wanted to check that there aren't any objections when the number of packages with patches increases quite a bit." Matthias writes; "First of all, thank you for communicating this early :-) I have no fundamental objections to adding it, you would just need to target "byzantium" or "landing". - Any chance that the kernel changes would break the desktop flavor of PureOS? Or would that be a completely separate kernel package and not merged with the desktop kernel? - You'd need to make sure phone things work on amd64 as well as on arm64 in case they have a convergent base and are used on both form factors. And 3) the PureOS team is tiny so we can't maintain lots and lots of PureOS<->Debian delta. But with the phone team's help I think that's absolutely doable there's also secondary questions, like whether it makes sense to just move shared sources to the pureos group(s) in Gitlab also, I'll have to go through with improving Laniakea's sync overview page to be less cluttered - at the moment it's quite hard to know what needs merging where ;-) (that's actually the thing I am working on at the moment, since that also gets rid of the last bit of D code and makes deploying Laniakea easier). - Laniakea can theoretically also build packages from Git repos - you'll need a list of repos and signed tags of a certain format in them, LK will then verify the tag signature and send the repo to a worker to create a source package out of that's then auto-uploaded. It's quite neat in concept... ....in practice I would need to get rid of the manual list and actually verify signatures (at the moment anything would be built, so that's really not deployable) Anyway, that's $future_stuff, let's work on getting the phone pieces into byzantium easily first :-)" Jeremiah writes; - I would like to understand more about the increase in kernel patches; how will they be maintained? What are the expectations of the Librem 5 team, is there going to be a transfer of responsibility for the patches from the Librem 5 team to PureOS team? Our resources are currently thinly stretched across our CI / CD, QA, and support teams, which means adding devices is a heavy lift that needs co-ordination. We don't really have a process for additional devices yet either and there needs to be some thought as we grow given that our Librem 5 traffic might significantly increase load and bandwidth on existing infrastructure. Do we have any data on; - Currently Librem 5 CI (I believe we run Munin on the ARM 02 server no? Do we have output from that which might show load, disk, CPU, etc? - How about the current instance of Laniakea? Are we running Munin? If not, do we have data on the server from a capacity planning standpoint? - I'd like to know a bit more about the plan - do we intend to use your new process to build from git repos with signed tags Matthias? Or are we going to continue to build on ARM 02 and then upload to Laniakea? Best regards, Jeremiah

3 6

Fwd: Bug#969321: transition: GNOME 3.38 (mutter, evolution-data-server, etc.)
by Jeremiah C. Foster 02 Sep '20

02 Sep '20

Hello! Please find attached an email you may already have been aware of but has a bearing on our work in PureOS. Namely that GNOME 3.38 is likely coming into Debian soon (and then to PureOS Byzantium) and will likely be in Bullseye when that's released. Cheers, Jeremiah

1 0

New PureOS images are ready for testing! (2020-07-18)
by Matthias Klumpp 18 Jul '20

18 Jul '20

Hi! We have new images ready for testing for both PureOS 9 (Amber) and the Byzantium development version. For the former, please give feedback on the updated images on their tracking bug: https://tracker.pureos.net/T919 The Byzantium development images were also generated per-month as usual and can be found at https://downloads.pureos.net/byzantium/ for testing. Cheers, Matthias

1 0

Bits from PureOS | Happy hypoxia averted (so far)
by Jeremiah C. Foster 03 Jul '20

03 Jul '20

Hello all! Admit it, you've missed this mailing list haven't you? :-) Firstly, I wanted to ask a question about backporting a 5.6 kernel for Amber. This would be used on the new mini that's been announced. ( https://shop.puri.sm/shop/librem-mini/) While the currently Amber kernel 4.19 works, according to Mr. Chromebox there are a couple of issues; - 4.19 doesn't have great support for the Comet Lake chipset - Bringing up a coreboot port with the mini, one can't use PureOS as it's not bootable from the vendor UEFI firmware What is the easiest way to create a bootable OEM image for Mr. Chromebox to boot the new mini? My guess is that we ought to be able to just build a Byzantium image and things should "just work". I say that because Debian 10 apparently supports EFI - https://wiki.debian.org/UEFI. Can we build an OEM image for Byzantium? How is this done for amber, is there a particular script I can use or a set of steps we use to do this? We ought to likely document this process for posterity. :-) Getting a new image for the factory floor will help a lot, we have more than minis in the pipeline as you may have seen. More to come, specifically some notes about buildstream and reprotest as well as variables for gitlab-ci.yml. Regards, Jeremiah

1 0

Fwd: [AppStream] AppStream 0.12.11 released!
by Jeremiah C. Foster 12 May '20

12 May '20

Relevant for our interests. -- -- Jeremiah C. Foster <jeremiah.foster(a)puri.sm> Gpg key id: 798DB834436A7BE38C97422D0DC062205451931B

2 1

Bits from PureOS | Life in the time of novel corona virus
by Jeremiah C. Foster 20 Mar '20

20 Mar '20

Hi everyone, A somber note today mostly to try to express solidarity for everyone on the list and anyone involved who may be going through hard times. Let me know personally if there's anything I can do. With regard to PureOS it is onward and upward. Matthias has been working on integrating flatpak support into Laniakea. This is a big deal and I'm really excited to see it. We've been working on a CI pipeline that builds flatpaks and then they get uploaded to the CD system, but that has been problematic because a lot of the technolgy is new and it's shifted around a lot. Flatpaks also do a sort of nested virtualization or nested isolation and that can be difficult to handle with many of the tools we use. Having some native functionality in Laniakea will be very helpful. I've been doing some poking at OpenQA from the SuSE folks. It is not packaged for Debian (though it's core package os-autoinst is). Trying to get a log in to Debian's instance of OpenQA https://openqa.debian.net/ leads to some weird site called microfocus.com. I wonder what relationship that holds to Debian's infrastructure? I'll have to dig a little more but I believe that having PureOS tested there might be a good thing. Kali is tested there as well so it may save us some disk space and CPU time to have it done there. We'll need to make sure that it meets the Free Software policies we have and while OpenQA itself surely does (its GPLv2), we shouldn't have to give info to a third party to access testing services. The RYF application for the Librem Key is still in process. We've updated the source code and it's README and nearly completed our response to the FSF so hopefully we'll receive some good news when we resubmit. That's it for now! Stay well and we'll get through this together! Jeremiah PS - I really mean it when I say you can reach out to me personally, I'm happy to talk to anyone on this list about PureOS, Purism, or just personal stuff. -- Jeremiah C. Foster <jeremiah.foster(a)puri.sm> Gpg key id: 798DB834436A7BE38C97422D0DC062205451931B

2 2

January 2020 in Reproducible Builds
by Chris Lamb 10 Feb '20

10 Feb '20

==================================================================== o ⬋ ⬊ January 2020 in Reproducible Builds o o ⬊ ⬋ https://reproducible-builds.org/reports/2020-01/ o ==================================================================== Welcome to the January 2020 report from the Reproducible Builds project. In this month's issue, we cover: * Upstream news & event coverage — Reproducing the Telegram messenger, etc. * Software development — Updates and improvements to our tooling * Distribution work — More work in Debian, openSUSE & friends * Misc news — From our mailing list & how to get in touch (Q: But what are reproducible builds...?) Whilst anyone can inspect the source code of free software for malicious flaws, almost all software is distributed to end users as pre-compiled binaries. The motivation behind the reproducible builds effort is to ensure no flaws have been introduced during this compilation process by promising identical results are always generated from a given source, thus allowing multiple third-parties to come to a consensus on whether a build was compromised. If you are interested in contributing, please visit the Contribute [1] page on our website. [1] https://reproducible-buids.org/contribute/ Upstream news & event coverage ============================== The Telegram [2] messaging application has documented full instructions [3] for verifying that its original source code is exactly the same code that is used to build the versions available on the Apple App Store and Google Play. [2] https://telegram.org/ [3] https://core.telegram.org/reproducible-builds Reproducible builds were mentioned in a panel on Software Distribution with Sam Hartman, Richard Fontana, & Eben Moglen [4] at the Software Freedom Law Center's 15h Anniversary Fall Conference [6] (at ~35m21s). [4] https://www.youtube.com/watch?v=rMinFopJMW0&t=2121s [6] https://www.softwarefreedom.org/events/2019/annual-conference/ Vagrant Cascadian will present a talk at SCALE 18x [7] in Pasadena, California on March 8th titled "There and Back Again, Reproducibly" [8]. [7] https://www.socallinuxexpo.org/scale/18x [8] https://www.socallinuxexpo.org/scale/18x/presentations/there-and-back-again… Matt Graeber [9] (@mattifestation) posted on Twitter that: > If you weren't aware of the reason Portable Executable [11] timestamps > in Win 10 binaries were nonsensical, Raymond's post explains the reason: > to support reproducible builds. ... referencing an article by Raymond Chen from January 2018 [12] which, amongst other things, mentions: > One of the changes to the Windows engineering system begun in Windows > 10 is the move toward reproducible builds. [9] https://medium.com/@mattifestation [11] https://en.wikipedia.org/wiki/Portable_Executable [12] https://devblogs.microsoft.com/oldnewthing/20180103-00/?p=97705 Jan Nieuwenhuizen announced the release of GNU Mes 0.22 [13] which produced a bit-for-bit identical "mescc-mes-static" binary with the mes-rb5 package within the GNU Guix operating system. Vagrant Cascadian subsequently uploaded this version of Mes to Debian. [13] https://lists.reproducible-builds.org/pipermail/rb-general/2020-January/001… Software development ==================== diffoscope ---------- diffoscope [17] is our in-depth and content-aware diff-like utility that can locate and diagnose reproducibility issues. It is run countless times a day on our testing infrastructure [18] and is essential for identifying fixes and causes of nondeterministic behaviour. [17] https://diffoscope.org [18] https://tests.reproducible-builds.org/debian/reproducible.html This month, diffoscope versions 135 and 136 were uploaded to Debian unstable by Chris Lamb. He also made the following changes to diffoscope itself, including: * New features: * Support external difference tools such as Meld [19], etc. similar to git-difftool(1). [20] * Extract resources.arsc files as well as classes.dex from Android .apk files to ensure that we show differences there. [21] * Fallback to the regular .zip container format for .apk files if apktool is not available. [22][23][24][25] * Drop --max-report-size-child and --max-diff-block-lines- parent; scheduled for removal in January 2018. [26] * Append a comment to a difference if we fallback to a less- informative container format but we are missing a tool. [27][28] * Bug fixes: * No longer raise a KeyError exception if we request an invalid member from a directory container. [29] * Documentation/workflow improvements: * Clarify that "install X" in various outputs actually refers to system-level packages. [30] * Add a note to the Contributing documentation to suggest enable concurrency when running the tests locally. [31] * Include the CONTRIBUTING.md file in the PyPI.org [32] release. [33][34] * Logging improvements: * Log a debug-level message if we cannot open a file as container due to a missing tool to assist in diagnosing issues. [35] * Correct a debug message related to compare_meta calls to quote the arguments correctly. [36] * Add the current PATH environment variable to the "Normalising locale..." debug-level message. [37] * Print the Starting diffoscope $VERSION line as the first line of the log as we are, well, starting diffoscope. [38] * If we don't know the HTML output name, don't emit an enigmatically truncated HTML output for debug message. [39] * Tests: * Don't exhaustively output the entire HTML report when testing the regression for #875281; parsing the JSON and pruning the tree should be enough. [41] * Refresh and update the fixtures for the .ico tests to match the latest version of Imagemagick [42] in Debian unstable. [43] * Code improvements: * Add a .git-blame-ignore-revs file to improve the output of git-blame(1) by ignoring large changes when introducing the Black [44] source code reformatter and update the CONTRIBUTING.md guide on how to optionally use it locally. [45] * Add a noqa line to avoid a false-positive Flake8 [46] "unused import" warning. [47] * Move logo.svg to under the doc/ directory [48] and make setup.py executable [49]. * Tidy diffoscope.main's configure method. [50][51][52][53] * Drop an assertion that is guaranteed by parallel if conditional [54] and an unused "Difference" import from the APK comparator. [55] * Turn down the volume for a recommendation in a comment. [56] * Rename the diffoscope.locale module to diffoscope.environ as we are modifying things beyond just the locale (eg. calling tzset [57], etc.) [58] * Factor-out the generation of foo not available in path comment messages into the exception that raises them [59] and factor out running all of our many zipinfo into a new method [60]. * trydiffoscope [61] is the web-based version of diffoscope. This month, Chris Lamb fixed the PyPI.org [62] release by adding the trydiffoscope script itself to the MANIFEST file and performing another release cycle. [63] In addition, Marc Herbert adjusted the cbfstool [64] tests to search for expected keywords in the output, rather than specific output [65], fixed a misplaced debugging line [66] and added a "Testing" section to the CONTRIBUTING.rst [67] file. Vagrant Cascadian updated to diffoscope 135 [68] in GNU Guix [69]. [19] https://meldmerge.org/ [20] https://salsa.debian.org/reproducible-builds/diffoscope/issues/87 [21] https://salsa.debian.org/reproducible-builds/diffoscope/issues/27 [22] https://salsa.debian.org/reproducible-builds/diffoscope/commit/bbbb322 [23] https://salsa.debian.org/reproducible-builds/diffoscope/commit/6710868 [24] https://salsa.debian.org/reproducible-builds/diffoscope/commit/85c2100 [25] https://salsa.debian.org/reproducible-builds/diffoscope/commit/b1b9977 [26] https://salsa.debian.org/reproducible-builds/diffoscope/commit/fee25e5 [27] https://salsa.debian.org/reproducible-builds/diffoscope/commit/0615036 [28] https://salsa.debian.org/reproducible-builds/diffoscope/commit/88bc142 [29] https://salsa.debian.org/reproducible-builds/diffoscope/commit/7765669 [30] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c99cd9b [31] https://salsa.debian.org/reproducible-builds/diffoscope/commit/9d88cda [32] https://pypi.org/ [33] https://salsa.debian.org/reproducible-builds/diffoscope/commit/0e5a0c5 [34] https://salsa.debian.org/reproducible-builds/diffoscope/commit/aa9db34 [35] https://salsa.debian.org/reproducible-builds/diffoscope/commit/5757c8b [36] https://salsa.debian.org/reproducible-builds/diffoscope/commit/3e3a18d [37] https://salsa.debian.org/reproducible-builds/diffoscope/commit/600831b [38] https://salsa.debian.org/reproducible-builds/diffoscope/commit/9a200bc [39] https://salsa.debian.org/reproducible-builds/diffoscope/commit/b709d89 [41] https://salsa.debian.org/reproducible-builds/diffoscope/issues/84 [42] https://imagemagick.org/ [43] https://salsa.debian.org/reproducible-builds/diffoscope/commit/614b0d1 [44] https://black.readthedocs.io/en/stable/ [45] https://salsa.debian.org/reproducible-builds/diffoscope/commit/4e40f75 [46] https://flake8.pycqa.org/en/latest/ [47] https://salsa.debian.org/reproducible-builds/diffoscope/commit/8993168 [48] https://salsa.debian.org/reproducible-builds/diffoscope/commit/f8f0d14 [49] https://salsa.debian.org/reproducible-builds/diffoscope/commit/efb7bdc [50] https://salsa.debian.org/reproducible-builds/diffoscope/commit/d377d3b [51] https://salsa.debian.org/reproducible-builds/diffoscope/commit/d2e283c [52] https://salsa.debian.org/reproducible-builds/diffoscope/commit/d658583 [53] https://salsa.debian.org/reproducible-builds/diffoscope/commit/8eb852a [54] https://salsa.debian.org/reproducible-builds/diffoscope/commit/722d735 [55] https://salsa.debian.org/reproducible-builds/diffoscope/commit/026ff74 [56] https://salsa.debian.org/reproducible-builds/diffoscope/commit/412fef1 [57] https://docs.python.org/3/library/time.html [58] https://salsa.debian.org/reproducible-builds/diffoscope/commit/786ff48 [59] https://salsa.debian.org/reproducible-builds/diffoscope/commit/3a5f46d [60] https://salsa.debian.org/reproducible-builds/diffoscope/commit/3b94c0c [61] https://try.diffoscope.org [62] https://pypi.org/ [63] https://salsa.debian.org/reproducible-builds/trydiffoscope/issues/1 [64] https://www.coreboot.org/CBFS [65] https://salsa.debian.org/reproducible-builds/diffoscope/commit/d59dd2a [66] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c150ae8 [67] https://salsa.debian.org/reproducible-builds/diffoscope/commit/0beddf1 [68] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=a3bf43481902ff10d0293… [69] https://guix.gnu.org/ reprotest --------- reprotest is our end-user tool to build same source code twice in widely differing environments and then checks the binaries produced by each build for any differences. This month, versions 0.7.11 and 0.7.12 were uploaded to Debian unstable [70] by Holger Levsen. This month, Iñaki Malerba improved the version test to split on the + character [71] and Ross Vandegrift updated the code to allow the user to override timeouts from the surrounding environment [72]. Holger Levsen also made the following additionally changes: * Drop the short timeout and use the install timeout instead. (#897442) * Use "real" reStructuredText [74] comments instead of using the raw directive. [75] * Update the PyPI [76] classifier to express we are using Python 3.7 now. [77] [70] https://tracker.debian.org/pkg/reprotest [71] https://salsa.debian.org/reproducible-builds/reprotest/commit/dc67985 [72] https://salsa.debian.org/reproducible-builds/reprotest/commit/7f645f9 [74] https://docutils.sourceforge.io/rst.html [75] https://salsa.debian.org/reproducible-builds/reprotest/commit/9eb1017 [76] https://pypi.org/ [77] https://salsa.debian.org/reproducible-builds/reprotest/commit/19c6d5a Other tools ----------- * disorderfs is our FUSE [78]-based filesystem that deliberately introduces non-determinism into directory system calls in order to flush out reproducibility issues. This month, Chris Lamb fixed an issue by ignoring the return values of fsyncdir to ensure (for example) dpkg(1) can "flush" /var/lib/dpkg correctly [79] and merged a change from Helmut Grohne to use the build architecture's version of pkg-config [80] to permit cross- architecture builds [81]. * strip-nondeterminism is our tool to remove specific non- deterministic results from a completed build. This month, version 1.6.3-2 was uploaded to Debian unstable [82] by Holger Levsen to bump the Standards-Version. [78] https://en.wikipedia.org/wiki/Filesystem_in_Userspace [79] https://salsa.debian.org/reproducible-builds/disorderfs/commit/07c6e80 [80] https://www.freedesktop.org/wiki/Software/pkg-config/ [81] https://salsa.debian.org/reproducible-builds/disorderfs/commit/520937a [82] https://tracker.debian.org/news/1095745/accepted-strip-nondeterminism-163-2… Upstream development -------------------- The Reproducible Builds project detects, dissects and attempts to fix as many unreproducible packages as possible. Naturally, we endeavour to send all of our patches upstream. This month, we wrote another large number of such patches, including: * Arnout Engelen (for the NixOS distribution [83]): * bash [84] (enable PGRP_PIPE regardless of build-time kernel version) * jitterentropy [85] (remove timestamps from Gzip[86]-compressed manpages, already filed upstream [87]) * ms-sys [88] (remove timestamps from .gz manpages, already upstream [89]) * Bernhard M. Wiedemann (for the openSUSE [90] distribution): * ImageMagick [91] (toolchain, .png date) * brickv [92] (sort a Python glob/readdir(3)) * cpython [93] (.pyc reproducibility) * doxygen [94] (merged a toolchain patch to prevent nondeterminism from ASLR) * fastjet-contrib [95] (sort find / readdir) * openjfx [96] (Java date) * ruby [97] (Reopen unsorted Ruby glob issue) * rubygem-sassc [98] (sort a Ruby readdir(3)) * Chris Lamb: * #948279 filed against python-gmusicapi. * #948582 filed against bochs. * #948872 filed against pcbasic. * #949379 filed against vmatch. * #949580 filed against pkg-js-tools. * #949684 filed against mcomix. * #949817 filed against shotcut (forwarded upstream [113]). * #950138 filed against pikepdf (forwarded upstream [116]). * Jelle van der Waa (Arch Linux [117]): * ardour [118] (hash ordering) * drumkv1 [119] (remove timestamp from .gz manpage) * frotz [120] (drop date) * frotz-dumb [121] * gnutls [122] (remove timestamps from .gz manpages) * samplv1 [123] (remove timestamp from .gz manpage) * sane [124] (date) * shards [125] (date) * Martin Liška: * gcc [126] (toolchain, fixing randomness in some .o files, with Alexander Monakov & Richard Biener) * Vagrant Cascadian submitted a large number patches via the Debian bug tracking system targeting the packages Civil Infrastructure Platform [127] as identified by the CIP package set [128] including: * #948757 & #948759 filed against apache2. * #948771 filed against guile-2.2. * #949114 & #949115 filed against alsa-tools. * #949270 & #949271 filed against libtool. * #949273 & #949275 filed against geoip. * #949324 filed against groff. * #949338 filed against gettext. * #949341 filed against sqlite3. * #949342 & #949343 filed against flex. * #949346 & #949348 filed against libnet. [83] https://nixos.org [84] https://github.com/NixOS/nixpkgs/pull/77196 [85] https://github.com/NixOS/nixpkgs/pull/77202 [86] https://www.gnu.org/software/gzip/manual/gzip.html [87] https://github.com/smuellerDD/jitterentropy-library/commit/0eca18fbd30318f5… [88] https://github.com/NixOS/nixpkgs/pull/77096 [89] https://sourceforge.net/p/ms-sys/patches/7/ [90] https://www.opensuse.org/ [91] https://github.com/ImageMagick/ImageMagick/pull/1270 [92] https://github.com/Tinkerforge/brickv/pull/23 [93] https://bugs.python.org/issue34033 [94] https://github.com/doxygen/doxygen/issues/7474 [95] https://github.com/alisw/fastjet/pull/6 [96] https://github.com/openjdk/jfx/pull/99 [97] https://bugs.ruby-lang.org/issues/8709 [98] https://github.com/sass/sassc-ruby/pull/178 [113] https://github.com/mltframework/shotcut/pull/824 [116] https://github.com/pikepdf/pikepdf/pull/76 [117] https://archlinux.org [118] https://github.com/ardour/ardour/pull/464/ [119] https://github.com/rncbc/drumkv1/pull/31 [120] https://gitlab.com/DavidGriffith/frotz/issues/189 [121] https://bugs.archlinux.org/task/65149 [122] https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gnu… [123] https://github.com/rncbc/samplv1/pull/30 [124] https://gitlab.com/sane-project/backends/issues/228 [125] https://github.com/crystal-lang/shards/pull/314 [126] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93274 [127] https://www.cip-project.org/ [128] https://tests.reproducible-builds.org/debian/bullseye/amd64/pkg_set_CIP.html Distribution work ================= openSUSE -------- In openSUSE [156], Bernhard M. Wiedemann published his monthly Reproducible Builds status update [157] and submitted the following bugs and patches: * doxygen [158] (toolchain, ASLR [159]; already merged upstream) * frotz [160] (version update & date) * gcc9 [161] (report unreproducible .o files, forwarded upstream [162]) * mingw* [163] (report random filename in .a files) * perl-TimeDate [164] (fix a "year 2020" bug, forwarded upstream [165]) * python-sherpa [166] (CPU-detection via --mtune=native) * qpress [167] (make PGO reproducible) * rubygem-sassc [168] (CPU & readdir, partially submitted upsteam [169]) * stgit [170] (recreate unreproducible .pyc files with fixed filesystem readdir(3) order) * xmvn [171] (report nondeterminism from filesystem order and randomness) Many Python packages were updated to avoid writing .pyc files with an embedded random path, including jupyter-jupyter-wysiwyg [172], jupyter- jupyterlab-latex [173], python-PsyLab [174], python-hupper [175], python-ipyevents [176] (don't rewrite .zip file), python-ipyleaflet [177], python-jupyter-require [178], python-jupyter_kernel_test [179], python-nbdime [180] (do not rewrite .zip, avoid time-based .pyc), python-nbinteract [181], python-plaster [182], python-pythreejs [183], python-sidecar [184] & tensorflow [185] (use pip install --no- compile). [156] https://www.opensuse.org/ [157] https://lists.opensuse.org/opensuse-factory/2020-01/msg00296.html [158] https://build.opensuse.org/request/show/766399 [159] https://en.wikipedia.org/wiki/Address_space_layout_randomization [160] https://build.opensuse.org/request/show/765634 [161] https://bugzilla.opensuse.org/show_bug.cgi?id=1160986 [162] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93274 [163] https://bugzilla.opensuse.org/show_bug.cgi?id=1160672 [164] https://build.opensuse.org/request/show/762957 [165] https://rt.cpan.org/Public/Bug/Display.html?id=124509 [166] https://build.opensuse.org/request/show/760838 [167] https://build.opensuse.org/request/show/767311 [168] https://build.opensuse.org/request/show/763080 [169] https://github.com/sass/sassc-ruby/pull/178 [170] https://build.opensuse.org/request/show/765317 [171] https://bugzilla.opensuse.org/show_bug.cgi?id=1162112 [172] https://build.opensuse.org/request/show/763685 [173] https://build.opensuse.org/request/show/763683 [174] https://build.opensuse.org/request/show/763260 [175] https://build.opensuse.org/request/show/763287 [176] https://build.opensuse.org/request/show/763292 [177] https://build.opensuse.org/request/show/763285 [178] https://build.opensuse.org/request/show/763266 [179] https://build.opensuse.org/request/show/763282 [180] https://build.opensuse.org/request/show/763281 [181] https://build.opensuse.org/request/show/763263 [182] https://build.opensuse.org/request/show/763261 [183] https://build.opensuse.org/request/show/763259 [184] https://build.opensuse.org/request/show/763257 [185] https://build.opensuse.org/request/show/763522 Debian ------ There was yet more progress towards making the Debian Installer [187] images reproducible. Following-on from last months' efforts, Chris Lamb requested a status update [188] on the Debian bug in question. [186] https://debian.org/ [187] https://www.debian.org/devel/debian-installer/ [188] https://bugs.debian.org/926242#157 Daniel Schepler posted to the debian-devel [190] mailing list to ask whether "running dpkg-buildpackage manually from the command line" [191] is supported, particularly with respect to having extra packages installed during the package was built either resulted in a failed build or even broken packages (eg. #948522, #887902, etc.). Our .buildinfo files could be one solution to this as they record the environment at the time of the package build. Holger disabled scheduling of packages from the "oldstable" stretch release on tests.reproducible-builds.org [194]. This is the first time since stretch's existence that we are no longer testing this release. [190] https://lists.debian.org/debian-devel/ [191] https://lists.debian.org/debian-devel/2020/01/msg00263.html [194] https://tests.reproducible-builds.org/ OpenJDK [195], a free and open-source implementation of the Java Platform was updated in Debian [196] to incorporate a number of patches from Emmanuel Bourg, including: * Make the generated character data source files reproducible. (#933339) * Make the generated module-info.java files reproducible. (#933342) * Make the generated copyright headers reproducible. (#933349) * Make the build user reproducible. (#933373) [195] https://jdk.java.net [196] https://tracker.debian.org/news/1094089/accepted-openjdk-11-110610-1-source… 83 reviews of Debian packages were added, 32 were updated and 96 were removed this month adding to our knowledge about identified issues [201]. Many issue types were updated by Chris Lamb, including: * timestamp_in_casacore_tables * random_identifiers_in_epub_files_generated_by_asciidoc * nondeterministic_ordering_in_casacore_tables * captures_build_path_in_golang_compiler * captures_build_path_via_haskell_adddependentfile * png_generated_by_plantuml_captures_kernel_version_and_builddate [201] https://tests.reproducible-builds.org/debian/index_issues.html Lastly, Mattia Rizzolo altered the permissions and shared the notes.git repository [202] which underpins the aforementioned package classifications with the entire "Debian" group on Salsa [203], therefore giving all DDs write access to it. This is an attempt to invite more direct contributions instead of merge requests. [202] https://salsa.debian.org/reproducible-builds/reproducible-notes [203] https://salsa.debian.org/ Other distributions ------------------- The FreeBSD Project [204] Tweeted that: > Reproducible builds are turned on by default for -RELEASE [205] ... which targets the next released version of this distribution [206]. Daniel Ebdrup [207] followed-up to note that this option: > Used to be turned on in -CURRENT when it was being tested, but it > has been turned off now that there's another branch where it's used, > whereas -CURRENT has more need to have the revision printed in uname > (which is one of the things that make a build unreproducible). [208] [204] https://www.freebsd.org/ [205] https://twitter.com/debdrup/status/1217488583503892480 [206] https://svnweb.freebsd.org/base?view=revision&revision=338642 [207] https://nullrouted.org/ [208] https://twitter.com/debdrup/status/1217515991267184645 For Alpine Linux [209], Holger Levsen disabled the builders run by the Reproducible Builds project as our patch to the abuild utility (see December's report [210] doesn't apply anymore and thus all builds have become unreproducible again. Subsequent to this, a patch was merged upstream. [211] [209] https://alpinelinux.org/ [210] https://reproducible-buids.org/reports/2019-12/ [211] https://github.com/alpinelinux/abuild/pull/110#issuecomment-580195097 In GNU Guix [212], on January 14th, Konrad Hinsen posted a blog post entitled "Reproducible computations with Guix" [213] which, amongst other things remarks that: > The [guix time-machine command] machine actually downloads the > specified version of Guix and passes it the rest of the command line. > You are running the same code again. Even bugs in Guix will be > reproduced faithfully! [209] https://alpinelinux.org/ [210] https://reproducible-buids.org/reports/2019-12/ [211] https://github.com/alpinelinux/abuild/pull/110#issuecomment-580195097 [212] https://guix.gnu.org/ [213] http://guix.gnu.org/blog/2020/reproducible-computations-with-guix/ The Yocto Project [214] reported that they have reproducible cross-built binaries that are independent of both the underlying host distribution the build is run on and independent of the path used for the build. This is now being continually tested on the Yocto Project's automated infrastructure to ensure this state is maintained in the future. [214] https://www.yoctoproject.org/ Project website & documentation ------------------------------- There was more work performed on our website [215] this month, including: * Chris Lamb: * Python SOURCE_DATE_EPOCH [216] documentation, clarifying that the second example generates a Python str-type, not a datetime.datetime [217] * Correct word omissions in the report template. [218] * Link to to our mailing list overview page [219] (and not the archives). [220] * Apply the Black [221] source code reformatter to the draft generation script. [222] * Move continuous tests heading level to <h1> (vs. <h2>) to match the other pages. [223] * Calculate the report authors dynamically. [224] * Holger Levsen: * Add Alpine Linux to our projects [226] and testing [227] pages. [228] * Add links to our list of projects being tested [229] [230] and mark Fedora [231] as being disabled at this time [232]. In addition, Arnout Engelen added a Scala [233] programming language example for the SOURCE_DATE_EPOCH environment variable [235], David del Amo updated the link to the Software Freedom Conversancy [236] to remove some double parentheses [237] and Peter Wu added a Debian example for the -ffile-prefix-map argument to support Clang [238] version 10 [239]. [215] https://reproducible-builds.org/ [216] https://reproducible-buids.org/docs/SOURCE_DATE_EPOCH [217] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/8e… [218] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/7b… [219] https://lists.reproducible-builds.org/listinfo/rb-general [220] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/6e… [221] https://black.readthedocs.io/en/stable/ [222] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/9f… [223] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/e1… [224] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/21… [226] https://reproducible-buids.org/who/ [227] https://reproducible-buids.org/citests/ [228] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/45… [229] https://reproducible-buids.org/citests/ [230] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/3f… [231] https://getfedora.org/ [232] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/19… [233] https://www.scala-lang.org/ [235] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/49… [236] https://sfconservancy.org/ [237] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/f4… [238] https://clang.llvm.org/ [239] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/a9… Testing framework ----------------- We operate a full-featured and comprehensive Jenkins [240]-based testing framework that powers tests.reproducible-builds.org [241]. This month, the following changes were made: * Adrian Bunk: * Use the et_EE locale/language instead of fr_CH. In Estonian, the "z" character is sorted between "s" and "t" which is contrary to common incorrect assumptions about the sorting order of ASCII [242] characters. [243] * Add ffile_prefix_map_passed_to_clang to the list of issues filtered as these build failures should be ignored. [244] * Remove the ftbfs_build_depends_not_available_on_amd64 from the list of filtered issues as this specific problem no longer exists. [245] * Holger Levsen: * Debian [246]: * Always configure apt to ignore expired release files on hosts running in the future. [247] * Create an "oldsuites" page, showing suites we used to test in the past. [248][249][250][251][252] * Schedule more old packages from the buster distribution. [253] * Deal with shell escaping and other options. [254][255][256] * Reverse the suite ordering on the packages page. [257][258] * Show bullseye statistics on dashboard page, moving away from buster [259] and additionally omit stretch [260]. * F-Droid [261]: * Document the increased diskspace requirements; we require over 700 GiB now. [262] * Misc: * Gracefully deal with umount problems. [263][264] * Run code to show "todo" entries locally. [265] * Use mmdebstrap instead of debootstrap. [266][267][268] * Jelle van der Waa (Arch Linux [269]): * Set the PACKAGER variable to a valid string to avoid noise in the logging. [270] * Add a link to the Arch Linux-specific package page in the overview table. [271] * Mattia Rizzolo: * Fix a hard-coded reference to the current year. [272] * Ignore "No server certificate defined" warning messages when automatically parsing logfiles. [273] * Vagrant Cascadian special-cased u-boot [274] on the armhf architecture: First, do not build the all architecture as the dependencies are not available on this architecture [275] and also pass the --binary-arch argument to pbuilder too [276]. The usual node maintenance was performed by Mattia Rizzolo [277][278], Vagrant Cascadian [279][280][281][282] and Holger Levsen. [240] https://jenkins.io/ [241] https://tests.reproducible-builds.org [242] https://en.wikipedia.org/wiki/ASCII [243] https://salsa.debian.org/qa/jenkins.debian.net/commit/d1f68a80 [244] https://salsa.debian.org/qa/jenkins.debian.net/commit/ea55e4bc [245] https://salsa.debian.org/qa/jenkins.debian.net/commit/64a062e3 [246] https://debian.org/ [247] https://salsa.debian.org/qa/jenkins.debian.net/commit/30a71a97 [248] https://salsa.debian.org/qa/jenkins.debian.net/commit/ffc13a29 [249] https://salsa.debian.org/qa/jenkins.debian.net/commit/c1accbfb [250] https://salsa.debian.org/qa/jenkins.debian.net/commit/13550757 [251] https://salsa.debian.org/qa/jenkins.debian.net/commit/2545eba2 [252] https://salsa.debian.org/qa/jenkins.debian.net/commit/d9b11c34 [253] https://salsa.debian.org/qa/jenkins.debian.net/commit/e5ebb1fa [254] https://salsa.debian.org/qa/jenkins.debian.net/commit/a35cc960 [255] https://salsa.debian.org/qa/jenkins.debian.net/commit/872453bb [256] https://salsa.debian.org/qa/jenkins.debian.net/commit/b5091f70 [257] https://salsa.debian.org/qa/jenkins.debian.net/commit/d27e8d3f [258] https://salsa.debian.org/qa/jenkins.debian.net/commit/d495b88f [259] https://salsa.debian.org/qa/jenkins.debian.net/commit/db5cf9c0 [260] https://salsa.debian.org/qa/jenkins.debian.net/commit/5516f56f [261] https://f-droid.org/ [262] https://salsa.debian.org/qa/jenkins.debian.net/commit/a6a0a691 [263] https://salsa.debian.org/qa/jenkins.debian.net/commit/a555f19e [264] https://salsa.debian.org/qa/jenkins.debian.net/commit/9f58a8df [265] https://salsa.debian.org/qa/jenkins.debian.net/commit/cdad9995 [266] https://salsa.debian.org/qa/jenkins.debian.net/commit/6ce1a757 [267] https://salsa.debian.org/qa/jenkins.debian.net/commit/cab70212 [268] https://salsa.debian.org/qa/jenkins.debian.net/commit/464508f1 [269] https://archlinux.org/ [270] https://salsa.debian.org/qa/jenkins.debian.net/commit/66c8eee0 [271] https://salsa.debian.org/qa/jenkins.debian.net/commit/95c9006e [272] https://salsa.debian.org/qa/jenkins.debian.net/commit/d61c0338 [273] https://salsa.debian.org/qa/jenkins.debian.net/commit/1919aa19 [274] https://www.denx.de/wiki/U-Boot/ [275] https://salsa.debian.org/qa/jenkins.debian.net/commit/08ef4bae [276] https://salsa.debian.org/qa/jenkins.debian.net/commit/0c838739 [277] https://salsa.debian.org/qa/jenkins.debian.net/commit/0c6b7024 [278] https://salsa.debian.org/qa/jenkins.debian.net/commit/e60be6d4 [279] https://salsa.debian.org/qa/jenkins.debian.net/commit/79dbfa03 [280] https://salsa.debian.org/qa/jenkins.debian.net/commit/d2fcbfab [281] https://salsa.debian.org/qa/jenkins.debian.net/commit/d3d94fcc [282] https://salsa.debian.org/qa/jenkins.debian.net/commit/19baf9e9 Misc news --------- On our mailing list [283] this month: * Chris Lamb responded in-depth to a thread on "Reproducible system images" [284] that was started in December [285] by Lars Wirzenius. This then led to a sub-thread regarding reproducible Docker images [286]. * Holger Levsen posted a brief request for help [287] regarding the bot that lives on our #reproducible-builds IRC channel that interfaces with our Twitter handle [288]. [283] https://lists.reproducible-builds.org/listinfo/rb-general/ [284] https://lists.reproducible-builds.org/pipermail/rb-general/2020-January/001… [285] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/00… [286] https://lists.reproducible-builds.org/pipermail/rb-general/2020-January/001… [287] https://lists.reproducible-builds.org/pipermail/rb-general/2020-January/001… [288] https://twitter.com/ReproBuilds § If you are interested in contributing to the Reproducible Builds project, please visit our "Contribute" [289] page on our website. However, you can also get in touch with us via: * IRC: #reproducible-builds on irc.oftc.net. * Twitter: @ReproBuilds [290] * Reddit: /r/ReproducibleBuilds [291] * Mailing list: rb-general(a)lists.reproducible-builds.org [292] [289] https://reproducible-builds.org/contribute/ [290] https://twitter.com/ReproBuilds [291] https://reddit.com/r/reproduciblebuilds [292] https://lists.reproducible-builds.org/listinfo/rb-general § This month's report was written by Arnout Engelen, Bernhard M. Wiedemann, Chris Lamb, heinrich5991, Holger Levsen, Jelle van der Waa, Mattia Rizzolo and Vagrant Cascadian. It was subsequently reviewed by a bunch of Reproducible Builds folks on IRC and the mailing list. Best wishes, -- Chris Lamb https://puri.sm

1 0

December 2019 in Reproducible Builds
by Chris Lamb 06 Jan '20

06 Jan '20

==================================================================== o ⬋ ⬊ December 2019 in Reproducible Builds o o ⬊ ⬋ https://reproducible-builds.org/reports/2019-12/ o ==================================================================== Welcome to the December 2019 report from the Reproducible Builds project. In these reports we outline the most important things that we have been up to over the past month. As a quick recap, whilst anyone can inspect the source code of free software for malicious flaws, almost all software is distributed to end users as pre-compiled binaries. The motivation behind the reproducible builds effort is to ensure no flaws have been introduced during this compilation process by promising identical results are always generated from a given source, thus allowing multiple third-parties to come to a consensus on whether a build was compromised. In this report for December, we cover: * Media coverage — A Google whitepaper, The Update Framework graduates within the Cloud Native Computing Foundation, etc. * Reproducible Builds Summit 2019 — What happened at our recent meetup? * Distribution work — The latest reports from Arch, Debian and openSUSE, etc. * Software development — Patches, patches, patches... * Mailing list summary * Contact — How to contribute. If you are interested in contributing to our project, please visit the Contribute [1] page on our website. [1] https://reproducible-builds.org/contribute/ Media coverage ============== Google published Binary Authorization for Borg [2], a whitepaper on how they reduce exposure of user data to unauthorised code as well as methods for verifying code provenance using their Borg [3]) cluster manager. In particular, the paper notes how they attempt to limit their "insider risk", ie. the potential for internal personnel to use organisational credentials or knowledge to perform malicious activities. The Linux Foundation [4] announced that The Update Framework [5] (TUF) has graduated within [6] the Cloud Native Computing Foundation (CNCF) and thus becomes the first specification and first security- focused project to reach the highest maturity level in that group. TUF is a technology that secures software update systems initially developed by Justin Cappos [8] at the NYU Tandon School of Engineering [9]. Andrew "bunnie" Huang published a blog post asking "Can We Build Trustable Hardware?" [11]. Whilst it concludes pessimistically that "open hardware is precisely as trustworthy as closed hardware" it does mention that reproducible builds can: > Enable any third-party auditor to download, build, and confirm > that the program a user is downloading matches the intent of the > developers. At the 36th Chaos Communication Congress [12] (36C3) in Leipzig, Hannes Mehnert from the MirageOS [13] project gave a presentation called *Leaving legacy behind* [14] which talks generally about *Mirage* system offering a potential alternative and minimalist approach to security but has a section on reproducible builds (at 38m41s. [ 2] https://cloud.google.com/security/binary-authorization-for-borg/ [ 3] https://en.wikipedia.org/wiki/Borg_(cluster_manager [ 4] https://www.linuxfoundation.org/ [ 5] https://theupdateframework.io/ [ 6] https://www.cncf.io/announcement/2019/12/18/cloud-native-computing-foundati… [ 8] https://engineering.nyu.edu/faculty/justin-cappos [ 9] https://engineering.nyu.edu/ [11] https://www.bunniestudios.com/blog/?p=5706 [12] https://events.ccc.de/congress/2019/wiki/index.php/Main_Page [13] https://mirage.io/ [14] https://media.ccc.de/v/36c3-11172-leaving_legacy_behind Reproducible Builds Summit 2019 =============================== We held our fifth annual Reproducible Builds summit [16] between the 1st and 8th December at Priscilla, Queen of the Medina [17] in Marrakesh, Morocco. The aim of the meeting was to spend time dicussing and working on Reproducible Builds with a widely diverse agenda and the event was a huge success. During our time together, we updated and exchanged the status of reproducible builds in our respective projects, improved collaboration between and within these efforts, expanded the scope and reach of reproducible builds to yet more interested parties, established and continued strategic long-term thinking in a way not typically possible via remote channels, and brainstormed designs for tools to enable end- users to get the most benefit from reproducible builds. Outside of these achievements in the hacking sessions kpcyrd made a breakthrough in Alpine Linux [18] by producing the first reproducible package — specifically, py3-uritemplate [19] — in this operating system. After this, progress was accelerated and by the denouement of our meeting the reproducibility status in Alpine reached 94%. In addition, Jelle van der Waa, Mattia Rizzolo and Paul Spooren discussed and implemented substantial changes to the database that underpins the testing framework that powers tests.reproducible-builds.org in order to abstract the schema in a distribution agnostic way, for example to allow submitting the results of attempts to verify officially distributed Arch Linux packages. Lastly, Jan Nieuwenhuizen, David Terry and Vagrant Cascadian used three entirely-separate distributions (GNU Guix, NixOS and Debian) to produce a bit-for-bit identical GNU Mes [26] binary despite using three different major versions of GCC and other toolchain components to build an initial binary, which was then used to build a final, bit-for-bit identical, binary of Mes. The event was held at Priscilla, Queen of the Medina [27] in Marrakesh, a location «sui generis» that stands for gender equality, female empowerment and the engagement of vulnerable communities locally through cultural activism. The event was open to anybody interested in working on Reproducible Builds issues, with or without prior experience. A number of reports and blog posts have already been written, including for: * openSUSE [28] * OCaml, "opam" and MirageOS [29] * GNU Guix [30] [16] https://reproducible-builds.org/events/Marrakesh2019/ [17] https://www.queenscollective.org/artistryasactivism [18] https://alpinelinux.org/ [19] https://tests.reproducible-builds.org/alpine/main/py3-uritemplate/py3-urite… [26] https://www.gnu.org/software/mes/ [27] https://www.queenscollective.org/artistryasactivism [28] https://lizards.opensuse.org/2019/12/13/opensuse-on-reproducible-builds-sum… [29] https://hannes.nqsb.io/Posts/ReproducibleOPAM [30] https://guix.gnu.org/blog/2019/reproducible-builds-summit-5th-edition/ Distribution work ================= Within Debian, Chris Lamb categorised a large number of packages and issues in the Reproducible Builds notes.git [34] repository, including identifying and creating markdown_random_email_address_html_entities and nondeterministic_devhelp_documentation_generated_by_gtk_doc. [34] https://salsa.debian.org/reproducible-builds/reproducible-notes/activity In openSUSE, Bernhard published his monthly Reproducible Builds status update [38] and filed the following patches: * hidviz [39] (use convert -strip) * python-ipydatawidgets [40] (make pip install reproducible, avoid trouble with Zip order & mtime [41]) * python-jupyterlab-templates [42] (make pip install reproducible) * python-jupyterlab [43] (make pip install reproducible) * python-mox3 [44] (drop Sphinx [45] environment.pickle file) * rpmlint-mini [46] (sort Python compile file list) * rubygem-ronn [47] ( Ruby date, submitted upstream [48] with updated patch) * syslinux6 [49] (sort find / readdir; already upstream) Bernhard also filed bugs against: * libhugetlbfs [50] (unreproducible .ldscript file) * libmicro [51] (Link-Time Optimisation [52] causing unreproducible object files; fix by Martin Pluskal [53]) * python-swifter [54] (report failure to build on single-core CUPs) * tesseract-ocr [55] (report variations via their build machine's CPU) [38] https://lists.opensuse.org/opensuse-factory/2019-12/msg00174.html [39] https://build.opensuse.org/request/show/754485 [40] https://build.opensuse.org/request/show/760182 [41] https://en.wikipedia.org/wiki/Mtime [42] https://build.opensuse.org/request/show/757375 [43] https://build.opensuse.org/request/show/755664 [44] https://build.opensuse.org/request/show/760190 [45] http://www.sphinx-doc.org/ [46] https://build.opensuse.org/request/show/754705 [47] https://build.opensuse.org/request/show/757287 [48] https://github.com/kamontat/ronn/pull/3 [49] https://build.opensuse.org/request/show/759820 [50] https://bugzilla.opensuse.org/show_bug.cgi?id=1159558 [51] https://bugzilla.opensuse.org/show_bug.cgi?id=1159556 [52] https://en.wikipedia.org/wiki/Interprocedural_optimization [53] https://build.opensuse.org/request/show/758238 [54] https://bugzilla.opensuse.org/show_bug.cgi?id=1158578 [55] https://bugzilla.opensuse.org/show_bug.cgi?id=1159231 The Yocto Project announced that it is running continuous tests on the reproducibility of its output [57] which can observed through the oe-selftest runs on their build server [58]. This was previously limited to just the mini images but this has now been extended to the larger graphical images. The test framework is available for end users to use against their own builds. Of particular interest is the production of binary identical results despite arbitrary build paths to allow more efficient builds through reuse of previously built objects, a topic covered in more-depth in a recent LWN article [59]. [56] https://www.yoctoproject.org/ [57] http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oeqa/selftest/cases… [58] https://autobuilder.yoctoproject.org/typhoon/#/console [59] https://lwn.net/Articles/804640/ In Arch Linux, the database structure on tests.reproducible- builds.org was changed and the testing jobs updated to match and work has been started on a verification test job which rebuilds the officially released packages and verifies if they are reproducible or not. In the "hacking" time after our recent summit, several key packages were made reproducible, raising the amount of reproducible packages by approximately 1.5%. For example libxslt [62] was patched with the patch originating from Debian and openSUSE. [62] https://www.archlinux.org/packages/extra/x86_64/libxslt/ Software development ==================== diffoscope ---------- diffoscope [64] is our in-depth and content-aware diff-like utility that can locate and diagnose reproducibility issues. It is run countless times a day on our testing infrastructure [65] and is essential for identifying fixes and causes of non-deterministic behaviour. This month, diffoscope version 134 was uploaded to Debian unstable by Chris Lamb. He also made the following changes to diffoscope itself, including: * Always pass a filename with a .zip extension to zipnote otherwise it will return with an UNIX exit code [66] of 9 and we fallback to displaying a binary difference for the entire file. [67] * Include the libarchive [68] file listing for ISO images to ensure that timestamps — and not just dates — are visible in any difference. [69] * Ensure that our autopkgtests [70] are run with our pyproject.toml [71] present for the correct black source code formatter settings. [72] * Rename the text_option_with_stdiout test to text_option_with_stdout [73] and tidy some unnecessary boolean logic in the ISO9660 tests [75]. [64] https://diffoscope.org [65] https://tests.reproducible-builds.org/debian/reproducible.html [66] https://en.wikipedia.org/wiki/Exit_status [67] https://salsa.debian.org/reproducible-builds/diffoscope/commit/a93aa33 [68] https://www.libarchive.org/ [69] https://salsa.debian.org/reproducible-builds/diffoscope/issues/81 [70] https://ci.debian.net/ [71] https://snarky.ca/clarifying-pep-518/ [72] https://bugs.debian.org/945993 [73] https://salsa.debian.org/reproducible-builds/diffoscope/commit/cb1c732 In addition, Eli Schwartz fixed an error in the handling of the progress bar [76] and Vagrant Cascadian added external tool reference for the zstd [77] compression format for GNU Guix [79] as well as updated the version to 133 in that distribution [80][81]. [75] https://salsa.debian.org/reproducible-builds/diffoscope/commit/341b98a [76] https://salsa.debian.org/reproducible-builds/diffoscope/commit/8706b87 [77] https://github.com/facebook/zstd [79] https://salsa.debian.org/reproducible-builds/diffoscope/commit/8c1b357 [80] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6a65185ee46babca0630d… [81] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=5de06b9dfb7e8fa5e3218… Project website & documentation ------------------------------- There was more work performed on our website this month, including: * Bernhard M. Wiedemann: * Add an OCaml example to our SOURCE_DATE_EPOCH documentation [84] and simplify the POSIX shell and date format usage [85][86] * Add a few "logo only" variations of our logo. [87] * Chris Lamb: * Add a link to the Tails [88] privacy-related operating system's instructions on how to verify a downloaded image. [90] * Add a link to the Reproducible Builds subreddit [91] to the page footer. [92] * Correct a "name" typo [93], add a missing "to" [94] and correct capitalisations of "OCaml" throughout the site [95]. * Jelle van der Waa: * Update the GNU Guix logo to the new design. [97] * Fix "signed tarballs are available" link on our Tools [98] page. [99] * Mattia Rizzolo: * Add an explicit robots.txt [100] file. [101] * Add a Google "site verification" [102] token. (Also added to the diffoscope website). [104][105] [88] https://tails.boum.org/ [90] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/fe… [91] https://www.reddit.com/r/reproduciblebuilds/ [92] https://salsa.debian.org/reproducible-builds/reproducible-website/issues/20 [93] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/f0… [94] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/02… [95] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/3b… [97] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/87… [98] https://reproducible-builds.org/docs/jvm/ [99] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/87… [100] https://www.robotstxt.org/ [101] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/63… [102] https://support.google.com/webmasters/answer/9008080?hl=en [104] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/1b… [105] https://salsa.debian.org/reproducible-builds/diffoscope-website/commit/875e… In addition, Paul Spooren added a new page overviewing our Continuous Tests [106] overview [107], Hervé Boutemy made a number of improvements to our Java and JVM documentation [108] expanding and clarifying various definitions as well as adding external links [109][110][111][112] and Mariana Moreira added a .jekyll-cache entry to the .gitignore file [114]. [106] https://reproducible-builds.org/citests/ [107] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/1c… [108] https://reproducible-builds.org/docs/jvm/ [109] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/79… [110] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/93… [111] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/f3… [112] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/fd… [114] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/eb… Upstream patches ---------------- The Reproducible Builds project detects, dissects and attempts to fix as many currently-unreproducible packages as possible. We endeavour to send all of our patches upstream where appropriate. This month, we wrote a large number of such patches, including: * Arnout Engelen: * sbt [115] (timestamps and file order in generated archives) * NixOS [116] installer/iso-image [117] (timestamps in ISO installer image) * Generated an updated NixOS reproducibility report [118] for nixos-unstable's iso_minimal installer image. * Bernhard M. Wiedemann: * bowtie [119] (date) * charybdis [120] (shell date & time) * coq [121] (report that .vo files vary from build order) * coq [122] (OCaml date) * kismet [123] (date) * libcec [124] (CMake: use TIMESTAMP variable instead of build date) * lifelines [125] (date) * OpenStack Python packages [126] (don't package a .pickle file) * orthanc [127] (sort Python readdir) * perl [128] (fix documentation-related build failure in 2020) * php7-pear [129] (sort a PHP-based readdir) * pmix [130] (date, time, host & user) * pw3270 [131] (make date & convert -strip) * python-autobahn [132] (report stuck tests on single CPU machine) * python-psychtoolbox [133] (sort Python readdir) * python-python-crfsuite [134] (sort Python glob [135] / readdir) * ripgrep [136] (report variations from CPU) * rubygem-ronn [137] (updated date patch) * vpp [138] (shell date, regression fix) * Multiple patches to the grass Geographic Information System. [140][141][142] * Jelle van der Waa: * tbb [143] (hostname, date & time) * pcp [144] (date & time) * libcec [145] (date & time) * cgdb [146] (date & time) * cloc [147] (date & time) * dlang [148] (please add support SOURCE_DATE_EPOCH in the D programming language [149] compiler, dlang) * dlang [150] (date & time in the D dtools library) * Chris Lamb: * #857454 re-opened against qtltools * #946315 filed against infernal (forwarded upstream [155]). * #946330 filed against usb-modeswitch-data (applied upstream). * #946331 filed against gtk-doc (forwarded upstream [160]). * #946332 filed against nftables. * #946333 filed against node-chart.js (forwarded upstream [165]). * #946335 filed against parsinsert. * #947608 filed against markdown. * #947708 filed against libtext-markdown-perl. [115] https://github.com/sbt/sbt/pull/5344 [116] https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+label%3A%226.topic%3A+repr… [117] https://github.com/NixOS/nixpkgs/pull/75484 [118] https://arnout.engelen.eu/nixos-r13y/report/ [119] https://github.com/BenLangmead/bowtie/pull/99 [120] https://github.com/charybdis-ircd/charybdis/pull/297 [121] https://github.com/coq/coq/issues/11229 [122] https://github.com/coq/coq/pull/11227 [123] https://github.com/kismetwireless/kismet/pull/195 [124] https://github.com/Pulse-Eight/libcec/pull/487 [125] https://github.com/lifelines/lifelines/pull/389 [126] https://review.opendev.org/700810 [127] https://bitbucket.org/sjodogne/orthanc/pull-requests/12/sort-file-lists/diff [128] https://github.com/Perl/perl5/pull/17390 [129] https://github.com/pear/pear-core/pull/105 [130] https://github.com/openpmix/openpmix/pull/1560 [131] https://github.com/PerryWerneck/pw3270/pull/2 [132] https://github.com/crossbario/autobahn-python/issues/1275 [133] https://github.com/Psychtoolbox-3/Psychtoolbox-3/pull/614 [134] https://github.com/scrapinghub/python-crfsuite/pull/115 [135] https://docs.python.org/3/library/glob.html [136] https://github.com/BurntSushi/ripgrep/issues/1441 [137] https://github.com/kamontat/ronn/pull/3 [138] https://gerrit.fd.io/r/c/vpp/+/23819 [140] https://github.com/OSGeo/grass/pull/247 [141] https://github.com/OSGeo/grass/pull/251 [142] https://github.com/OSGeo/grass/pull/263 [143] https://github.com/intel/tbb/issues/202 [144] https://github.com/performancecopilot/pcp/pull/805 [145] https://github.com/Pulse-Eight/libcec/issues/485 [146] https://github.com/cgdb/cgdb/pull/215 [147] https://github.com/AlDanial/cloc/pull/438 [148] https://issues.dlang.org/show_bug.cgi?id=20444 [149] https://dlang.org/ [150] https://issues.dlang.org/show_bug.cgi?id=20445 [155] https://github.com/EddyRivasLab/infernal/pull/19 [160] https://gitlab.gnome.org/GNOME/gtk-doc/merge_requests/37 [165] https://github.com/chartjs/Chart.js/pull/6817 Test framework -------------- We operate a comprehensive Jenkins-based testing framework that powers tests.reproducible-builds.org. This month, the following changes were made: * Holger Levsen: * Alpine: * Indicate where Alpine is being built on the node overview page. [175] * Turn off debugging output. [176] * Sleep longer if no packages are to be built. [177] * Misc: * Add some help text to our script to powercycle IONOS [178] (*neé* Profitbricks) nodes. [179] * Install mosh [180] everywhere. [181] * Only install ripgrep [182] on Debian nodes. [183] * Mattia Rizzolo: * Arch Linux: * Normalise the suite names in the database. [185][186][187][188][189] * Drop an unneeded line in the scheduler. [190] * Debian: * Fix a number of SQL errors. [192][193][... [194][195] * Use the debian.debian_support Python library over apt_pkg to perform version comparisons. [196] * Misc: * Permit other distributions to use our web-based package scheduling script. [197 * Reformat our power-cycling script using Black [198] and use the Python logging [199] module. [200] * Introduce a dsources database view to simplify some queries [201] and add a build_type field to support both "doublerebuilds" and verification rebuilds [202]. * Move (almost) all the timestamps in the database schema from raw strings to "real" timestamp data types. [203] * Only block bots on jenkins.debian.net [204] and tests.reproducible-builds.org [205], not any other sites. [206] * kpcyrd (for Alpine Linux): * Patch/install the abuild utility to one that is reproducible. [208][209][210][211] * Bump the number of build workers and collect garbage more frequently. [212][213][214][215] * Classify and display build results consistently. [216][217][218] * Ensure that tmux [219] and ripgrep [220] is installed. [221][222] * Support building packages in the future. [223][224][225] [175] https://salsa.debian.org/qa/jenkins.debian.net/commit/4af96f16 [176] https://salsa.debian.org/qa/jenkins.debian.net/commit/6a461023 [177] https://salsa.debian.org/qa/jenkins.debian.net/commit/f1d3c700 [178] https://www.ionos.com/ [179] https://salsa.debian.org/qa/jenkins.debian.net/commit/23442fc2 [180] https://mosh.org/ [181] https://salsa.debian.org/qa/jenkins.debian.net/commit/25e3d43b [182] https://github.com/BurntSushi/ripgrep [183] https://salsa.debian.org/qa/jenkins.debian.net/commit/f3a3ce6b [185] https://salsa.debian.org/qa/jenkins.debian.net/commit/7a0295e8 [186] https://salsa.debian.org/qa/jenkins.debian.net/commit/231884e8 [187] https://salsa.debian.org/qa/jenkins.debian.net/commit/62750403 [188] https://salsa.debian.org/qa/jenkins.debian.net/commit/d8473a13 [189] https://salsa.debian.org/qa/jenkins.debian.net/commit/77d3b173 [190] https://salsa.debian.org/qa/jenkins.debian.net/commit/035f6170 [192] https://salsa.debian.org/qa/jenkins.debian.net/commit/cd4ee15d [193] https://salsa.debian.org/qa/jenkins.debian.net/commit/e380dad1 [194] https://salsa.debian.org/qa/jenkins.debian.net/commit/8c515b2d [195] https://salsa.debian.org/qa/jenkins.debian.net/commit/528f3bce [196] https://salsa.debian.org/qa/jenkins.debian.net/commit/7677b378 [197] https://salsa.debian.org/qa/jenkins.debian.net/commit/cb775560 [198] https://black.readthedocs.io/ [199] https://docs.python.org/3/library/logging.html [200] https://salsa.debian.org/qa/jenkins.debian.net/commit/325b9f57 [201] https://salsa.debian.org/qa/jenkins.debian.net/commit/95eb84e6 [202] https://salsa.debian.org/qa/jenkins.debian.net/commit/86160814 [203] https://salsa.debian.org/qa/jenkins.debian.net/commit/6e7a475c [204] https://jenkins.debian.net/ [205] http://tests.reproducible-builds.org/ [206] https://salsa.debian.org/qa/jenkins.debian.net/commit/e09cda74 [208] https://salsa.debian.org/qa/jenkins.debian.net/commit/3b55b4d3 [209] https://salsa.debian.org/qa/jenkins.debian.net/commit/b4cfe3d3 [210] https://salsa.debian.org/qa/jenkins.debian.net/commit/2d81fa1a [211] https://salsa.debian.org/qa/jenkins.debian.net/commit/6c3c15e0 [212] https://salsa.debian.org/qa/jenkins.debian.net/commit/35a3dd33 [213] https://salsa.debian.org/qa/jenkins.debian.net/commit/a97cb13c [214] https://salsa.debian.org/qa/jenkins.debian.net/commit/83cc9dca [215] https://salsa.debian.org/qa/jenkins.debian.net/commit/30138aa1 [216] https://salsa.debian.org/qa/jenkins.debian.net/commit/21026d76 [217] https://salsa.debian.org/qa/jenkins.debian.net/commit/70a8fe35 [218] https://salsa.debian.org/qa/jenkins.debian.net/commit/9eeb3a5a [219] https://tmux.github.io/ [220] https://github.com/BurntSushi/ripgrep [221] https://salsa.debian.org/qa/jenkins.debian.net/commit/332f2549 [222] https://salsa.debian.org/qa/jenkins.debian.net/commit/3b43b4f9 [223] https://salsa.debian.org/qa/jenkins.debian.net/commit/912f3126 [224] https://salsa.debian.org/qa/jenkins.debian.net/commit/71380c9a [225] https://salsa.debian.org/qa/jenkins.debian.net/commit/5ee25a02 Lastly, Paul Spooren removed the project overview from the bottom-left of the generated pages [226] and the usual node maintenance was performed by Holger Levsen [227] and Mattia Rizzolo [228][229], etc. [226] https://salsa.debian.org/qa/jenkins.debian.net/commit/23eb5845 [227] https://salsa.debian.org/qa/jenkins.debian.net/commit/dea04259 [228] https://salsa.debian.org/qa/jenkins.debian.net/commit/7587e568 [229] https://salsa.debian.org/qa/jenkins.debian.net/commit/6d8111ce Mailing list summary ==================== There was considerable activity on our mailing list [230] this month. Firstly, Bernhard M. Wiedemann posted a thread asking "What is the goal of reproducible builds?" [231] in order to encourage refinements, extra questions and other contributions to what an end-user experience of reproducible builds should or even could look like. Eli Schwartz then resurrected a previous thread titled "Progress in rpm and openSUSE in 2019" [232] to clarify some points around Arch Linux and Python package installation. Hans-Christoph Steiner followed- up to a separate thread [234] originally started by Hervé Boutemy announcing the status of .buildinfo file support in the Java ecosystem, and Paul Spooren then informed the list [235] that Google Summer of Code is now looking for projects for the latest cohort. Lastly, Lars Wirzenius enquired about the status of Reproducible system images [237] which resulted in a large number of responses [238]. [230] https://lists.reproducible-builds.org/listinfo/rb-general/ [231] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/00… [232] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/00… [234] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/00… [235] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/00… [237] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/00… [238] https://lists.reproducible-builds.org/pipermail/rb-general/2019-December/th… Contact ======= If you are interested in contributing to the Reproducible Builds project, please visit the "Contribute" page on our website: https://reproducible-builds.org/contribute/ However, you can get in touch with us via: * IRC: #reproducible-builds on irc.oftc.net. * Twitter: https://twitter.com/@ReproBuilds * Reddit: https://reddit.com/r/reproduciblebuilds * Mailing list: https://lists.reproducible-builds.org/listinfo/rb-general This month's report was written by Arnout Engelen, Bernhard M. Wiedemann, Chris Lamb, Hervé Boutemy, Holger Levsen, Jelle van der Waa, Lukas Puehringer and Vagrant Cascadian. It was subsequently reviewed by a bunch of Reproducible Builds folks on IRC and the mailing list. -- o ⬋ ⬊ Chris Lamb o o reproducible-builds.org ⬊ ⬋ o

1 0

2025

2024

2023

2022

2021

2020

2019

2018

PureOS-project