- PureOS-project - Purism Mailing Lists

Bits from PureOS | 2020 edition
by Jeremiah C. Foster 04 Jan '20

04 Jan '20

Hello faithful readers! Your attention, replies, and hardwork made 2019 a great year for this mailing list. There's been a huge increase in communication here and I'm grateful for the discussion, feedback, and guidance. I'm dropping this link here to let those who read this list know that we've had a summary of the past year published; https://puri.sm/posts/2019-year-in-review-pureos/ With that posted, it is time to look towards 2020 and layout what the priorities are for the new year. Without question I think the number one priority from Purism management is the PureOS Store. In my discussions with Todd about the Store, it is clear not only that it is a high priority, but that the store can be a way to bolster PureOS and its large archive and get Free Software into the hands of users. This, I feel, is hugely important to our mission and so I'm going to prioritize it at the top of the list. Fortunately, this has been an idea that has already been floated and there is work that's been done towards realizing a store or easily accessible archive in some form or another. I hope to be able to pull the disparate threads together; work done in Laniakea, frontend work from Rodolfo and Francois, as well as other infrastrucutre bits to realize the goal. I hope to organize this work in the coming weeks and try and set out a schedule so we can track and measure our progress and, most importantly, communicate the work that's been done by the team because I think it's quite amazing. More regular releases for the folks who install PureOS on machines on the factory floor is also a high priority. We've come so far now with our releases - amber and byzantium - that it's time to support them with a bit more predictable release cycle and more Quality Assurance. To do that let's pick up the thread on releases, I'll try and revive that. Matthias K. has mentioned OpenQA as a potentially useful tool for doing QA on our releases and I agree, I hope to set that up for us before FOSDEM so we can use it. I have a couple other small tasks to complete before that work can be started as well as some administrative housekeeping, but I'm really eager to get more QA for our releases since we've come so far the last year or so. And yes, FOSDEM! I'm going to be there for about a week. I plan on attending the MiniDebCamp: https://wiki.debian.org/DebianEvents/be/2020/MiniDebCamp It would be great if all got a chance to meet up in Brussels, I would really appreciate it. Just having the opportunity to speak face to face would benefit me tremendously and having a chance to outline all of our goals and plans for 2020 will be an added bonus. Thanks for reading this far! Best, Jeremiah

4 5

policy for level of stability of PureOS stable
by Jonas Smedegaard 20 Dec '19

20 Dec '19

How stable is PureOS stable a.k.a. amber? Which criteria for permitting new packages to get included? Which criteria for permitting existing packages to get updated? Do I just use my gut feeling? Concretely, David Seaward wants ldh-gui-suite added, but makes sense to me to address this generally, eary on. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private

4 6

November 2019 in Reproducible Builds
by Chris Lamb 12 Dec '19

12 Dec '19

==================================================================== o ⬋ ⬊ November 2019 in Reproducible Builds o o ⬊ ⬋ https://reproducible-builds.org/reports/2019-11/ o ==================================================================== Welcome to the November 2019 report from the Reproducible Builds project. As a summary of our project, 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 therefore 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 month's report, we cover: * Media coverage and events — A Reproducibility Challenge, etc. * Upstream news — OCaml, Mes, Maven, etc. * Distribution work — The latest reports from Arch, Debian and openSUSE, and friends * Software development — Holiday bonanza of patches, work on diffoscope, etc. * Contributing — How to get in touch, etfc. If you are interested in contributing to our project, please visit the Contribute [1] page on our website. Media coverage and events ========================= We held our fifth annual Reproducible Builds summit [2] between the 1st and 8th December in Marrakesh, Morocco. A full, in-depth report will be posted next month… On November 16th, Vagrant Cascadian presented *There and Back Again, Reproducibly* [3] at the SeaGL [4] in Seattle, Washington. Chris Lamb was featured on The Manifest [5] package management podcast in an episode called *Reproducible Builds project and Debian package management* [6]. ReScience C [7] is an open-access journal that targets computational research and encourages the explicit replication of already published research. This month they announced their *Ten Years Reproducibility Challenge* [8] which promotes the idea that old code — in this instance, a "scientific article [published] before January 1st 2010" — should also run on modern hardware and software in order to check one can obtain the same scientific results in the future. [ 1] https://reproducible-builds.org/contribute/ [ 2] https://reproducible-builds.org/events/Marrakesh2019/ [ 3] https://osem.seagl.org/conferences/seagl2019/program/proposals/671 [ 4] https://seagl.org [ 5] https://manifest.fm [ 6] https://manifest.fm/14 [ 7] http://rescience.github.io/ [ 8] https://rescience.github.io/ten-years/ Upstream news ============= Mike Hommey pushed a change to Mozilla build system [9] to add and print error messages when differences are found between builds as requested in bug #1597903 [10]. There was fresh activity on an old pull request for the OCaml [11] programming language regarding the usage and adoption of the BUILD_PATH_PREFIX_MAP environment variable [12] that is used to ensure that software packages do not embed build-time paths into generated files. On the pull request [13] in question, Gabriel Scherer [14] was kind enough to provide many helpful examples on how to use the rewrite rules [15]. Jan Nieuwenhuizen announced the release of GNU Mes 0.21 [16] and Jeremiah Orians announced [17] the release of mescc-tools-seed [18] version 1.1: > Capable of bootstrapping from a simple hex assembler all the way > to a cross-platform C compiler Work is still ongoing [to] result > in a full bootstrap from a 357 byte bootstrap binary all the way > to GCC. Hervé Boutemy [19] announced the release of three base Apache Maven [20] plugins (source, .jar, and assembly) to get reproducible Builds as a "direct output" from this build system. For more information, please see the "Configuring for Reproducible Builds" [21] section of their documentation. Eli Schwartz reported a bug against the GNU groff [22] typesetting system for incomplete SOURCE_DATE_EPOCH [23] environment variable support; the output files appeared to be embedding the build timezone [24]. [ 9] https://hg.mozilla.org/integration/autoland/rev/cd6b79c74b23 [10] https://bugzilla.mozilla.org/show_bug.cgi?id=1597903 [11] https://ocaml.org/ [12] https://reproducible-builds.org/specs/build-path-prefix-map/ [13] https://github.com/ocaml/ocaml/pull/1515 [14] http://gallium.inria.fr/~scherer/ [15] https://github.com/ocaml/ocaml/pull/1515#issuecomment-559035723 [16] https://lists.reproducible-builds.org/pipermail/rb-general/2019-November/00… [17] https://lists.reproducible-builds.org/pipermail/rb-general/2019-November/00… [18] https://github.com/oriansj/mescc-tools-seed [19] http://people.apache.org/~hboutemy/ [20] https://maven.apache.org/ [21] https://maven.apache.org/guides/mini/guide-reproducible-builds.html [22] https://www.gnu.org/software/groff/ [23] https://reproducible-builds.org/specs/source-date-epoch/ [24] https://savannah.gnu.org/bugs/?57218 Distribution work ================= Arch Linux ---------- A slight but temporary decline in the Arch Linux reproducibility status [25] was determined to be due to a bug in the continuous integration framework where one build was building with --nocheck whilst the other did not, resulting in the test dependencies being installed on one build. This led to differences in the BUILDINFO file which records the build dependencies. Morten Linderud (*Foxboron*) wrote a blog post [26] on the progress of reproducible builds for Arch packages, including how to reproduce packages and a roadmap of future of work. The standard Arch development tools package (devtools) now contains a new tool called makerepropkg which can reproduce a package from the Arch repositories given a seed PKGBUILD file. A lot of work has been put into getting the "[core]" system more reproducible; every package has been rebuilt [27] with a new version of pacman [28] which resolved a previous issue with storing the package size. Build failures and download issues have also been resolved which have lead to an increase of reproducible packages in this distributions continuous integration setup [29]. [25] https://tests.reproducible-builds.org/archlinux/archlinux.png [26] https://linderud.dev/blog/reproducible-arch-linux-packages/ [27] https://lists.archlinux.org/pipermail/arch-dev-public/2019-November/029721.… [28] https://wiki.archlinux.org/index.php/pacman [29] https://tests.reproducible-builds.org/archlinux/archlinux.html openSUSE -------- Bernhard M. Wiedemann posted a summary of openSUSE updates for 2019 [30] including rpm, a high level openSUSE status [31] and fixing problems with .pyc files [32] which is also relevant to Arch Linux. The report also summarises the current reproducibility statu and bernhard also published his monthly Reproducible Builds status update too [33]. [30] https://lists.reproducible-builds.org/pipermail/rb-general/2019-November/00… [31] https://bugzilla.opensuse.org/show_bug.cgi?id=1133809 [32] https://bugzilla.opensuse.org/show_bug.cgi?id=1094323 [33] https://lists.opensuse.org/opensuse-factory/2019-11/msg00370.html Debian ------ Thorsten Glaser [34] filed a bug against the debhelper packaging library [35] to request that it sets and exports a umask [36] of "022" for all operations as a possible "harmonisation potential". A varying umask can result in unreproducible packages as the file permissions on the build system can be embedded into archives generated by the build system. Chris Lamb categorised a large number of packages and issues in the Reproducible Builds "notes [37]" repository, including adding a new ocaml_dune_captures_build_path toolchain issue [38]. Vagrant Cascadian filed a bug against the Lintian [39] Debian static analyser for Debian packages to request that it checks for missing and/or unsigned .buildinfo files [40]. He also uploaded the latest version [41] of GNU Mes [42] to the *unstable* distribution. [34] https://www.mirbsd.org/ [35] https://bugs.debian.org/944691 [36] https://en.wikipedia.org/wiki/Umask [37] https://salsa.debian.org/reproducible-builds/reproducible-notes/activity [38] https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/c12c… [39] https://lintian.debian.org/ [40] https://bugs.debian.org/944707 [41] https://tracker.debian.org/news/1080851/accepted-mes-020-1-source-amd64-int… [42] https://www.gnu.org/software/mes/ Other ----- Natanael Copa (@n_copa) posted on Twitter that he was finally able to make a fully reproducible package [44] for Alpine Linux [45]. The NixOS [46] distribution announced that they plan to run a Christmas Hackathon [47] hosted by Smarkets [48] in London, England on 9th December. [44] https://twitter.com/n_copa/status/1192447768855482369 [45] https://alpinelinux.org/ [46] https://nixos.org/ [47] https://www.meetup.com/NixOS-London/events/266848767 [48] https://smarkets.com/ Software development ==================== 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: * OpenSC [49] (generate consistent DocBook [50] identifiers) [49] https://github.com/OpenSC/OpenSC/pull/1839 [50] https://docbook.org * Bernhard M. Wiedemann: * abseil-cpp [51] (sort the output of find/readdir(2)) * afl [52] (date) * brp-check-suse [53] (to strip link-time optimisation (LTO) [54] data from .o object files) * buzztrax [55] (report a parallelism/nondeterminism issue from GTK-Doc [56]) * cardpeek [57] (fix a previous patch) * cecilia [58] (strip date and time in a .png image file) * lib3270 [59] (merged; date) * maven-plugin-bundle [60] (fix a Java date) * nulloy [61] (.zip issue, already filed upstream [62]) * opencensus-cpp [63] (sort the result of find/readdir(2)) * OpenSC [64] (generate consistent DocBook [65] identifiers) * pcc [66] (fix a build failure from LTO [67] in .a archive files) * perl-HTTP-Cookies [68] (fix a build failure in 2025) * pocl [69] (report compile-time CPU detection) * python-oslo.reports [70] (drop unnecessary files with randomness) * sql-parser [71] (sort find/readdir(2)) * vim [72] (report a build failure when built without parallelism) * Various updates to the RPM package manager [73]: * #931 [74] — Keep at least one changelog entry to set SOURCE_DATE_EPOCH [75]. * #933 [76] — Regression fix so we can override the Build Date header again. * #936 [77] — Sort to avoid ordering issues from parallel header generation. * #944 [78] — Provide a cleaner solution for bug #936 [79] listed above. [51] https://build.opensuse.org/request/show/750468 [52] https://github.com/vanhauser-thc/AFLplusplus/pull/122 [53] https://github.com/openSUSE/brp-check-suse/pull/29 [54] https://en.wikipedia.org/wiki/Interprocedural_optimization [55] https://github.com/Buzztrax/buzztrax/issues/89 [56] https://www.gtk.org/gtk-doc/ [57] https://build.opensuse.org/request/show/746648 [58] https://build.opensuse.org/request/show/750463 [59] https://github.com/PerryWerneck/lib3270/pull/3 [60] https://github.com/apache/felix/pull/209 [61] https://build.opensuse.org/request/show/746033 [62] https://github.com/nulloy/nulloy/pull/149 [63] https://build.opensuse.org/request/show/751817 [64] https://github.com/OpenSC/OpenSC/pull/1839 [65] https://docbook.org [66] https://build.opensuse.org/request/show/745529 [67] https://en.wikipedia.org/wiki/Interprocedural_optimization [68] https://github.com/libwww-perl/HTTP-Cookies/pull/56 [69] https://github.com/pocl/pocl/issues/793 [70] https://review.opendev.org/693327 [71] https://github.com/hyrise/sql-parser/pull/134 [72] https://bugzilla.opensuse.org/show_bug.cgi?id=1157623 [73] https://rpm.org/ [74] https://github.com/rpm-software-management/rpm/pull/931 [75] https://reproducible-builds.org/specs/source-date-epoch/ [76] https://github.com/rpm-software-management/rpm/pull/933 [77] https://github.com/rpm-software-management/rpm/pull/936 [78] https://github.com/rpm-software-management/rpm/pull/944 [79] https://github.com/rpm-software-management/rpm/pull/936 * Chris Lamb: * #943954 for against tm-align [81]. * #943956 for snakemake [83] (forwarded upstream [84]). * #944131 for splitpatch [86] (forwarded upstream [87]). * #944214 filed against libaqbanking [89]. * #944520 for isbg [91] (forwarded upstream [92]). * #944782 for python-sybil [94] (forwarded upstream [95]). * #945105 filed against intel-gpu-tools [97]. * #945576 filed against superlu-dist [99]. * #945822 filed against liblopsub [101]. * genpy [102] [81] https://tracker.debian.org/pkg/tm-align [83] https://tracker.debian.org/pkg/snakemake [84] https://github.com/snakemake/snakemake/pull/80 [86] https://tracker.debian.org/pkg/splitpatch [87] https://github.com/jaalto/splitpatch/pull/8 [89] https://tracker.debian.org/pkg/libaqbanking [91] https://tracker.debian.org/pkg/isbg [92] https://github.com/isbg/isbg/pull/139 [94] https://tracker.debian.org/pkg/python-sybil [95] https://github.com/cjw296/sybil/pull/18 [97] https://tracker.debian.org/pkg/intel-gpu-tools [99] https://tracker.debian.org/pkg/superlu-dist [101] https://tracker.debian.org/pkg/liblopsub [102] https://github.com/ros/genpy/pull/110#event-2768597322 * Vagrant Cascadian: * #944694 filed against resource-agents [104] (forwarded upstream [105]). [104] https://tracker.debian.org/pkg/resource-agents [105] https://github.com/ClusterLabs/resource-agents/commit/088707c81b7ddfc117490… diffoscope ---------- diffoscope [106] is our in-depth and content-aware diff utility that can locate and diagnose reproducibility issues. It is run countless times a day on our testing infrastructure and is essential for identifying fixes and causes of non-deterministic behaviour. This month versions 131, 132 and 133 was uploaded to Debian unstable by Chris Lamb. He also made the following changes: * New features / improvements: * Allow all possible .zip file variations to return from external tools with non-zero exit codes, not just known types we can identify (e.g. Java .jmod and .jar files). (#78 [107]) * Limit .dsc and .buildinfo file matching to files in ASCII or UTF-8 format. (#77 [108]) * Bump the previous max_page_size limit from 400 kB to 4 MB. [109] * Clarify in the HTML and text outputs that the limits are per- format, not global. (#944882 [110]) * Don't use line-based buffering when communicating with subprocesses in "binary" mode. (#75 [111]) * Regression fixes: * Correct the substitution/filtering of paths in ELF output to avoid unnecessary differences depending on the path name provided and commandline. (#945572 [112]) * Silence/correct a Python SyntaxWarning [113] message due to incorrectly comparing an integer by identity vs. equality. (#945531 [114]) * Testsuite improvements: * Refresh the OCaml [115] test fixtures to support versions greater than 4.08.1. [116] * Update an Android manifest [117] test to reflect that parsed XML attributes are returned in a new/sorted manner under Python 3.8. [118] * Dramatically Truncate the tcpdump [119] expected diff to 8KB from ~600KB to reduce the size of the release tarball. [120] * Add a self-test to encourage that new test data files are generated dynamically or at least no new ones are added without an explicit override. [121] * Add a comment that the text_ascii1 and text_ascii2 fixture files are used in multiple tests so is not trivial to remove/replace them. [122] * Drop two more test fixture files for the directory tests. [123] * Don't run our self-test against the output of the Black source code reformatter [124] with versions earlier than "ours" as it will generate different results. [125] * Update an XML test for Python 3.8. [126] * Drop unused an unused BASE_DIR global. [127] * Code improvements: * Rework a long string of or statements into a loop with a break. [128] * Update code to reflect the latest version of the Black [129] source code reformatter. [130] * Correct a reference to the .rdx extension suffix in a comment. [131] [106] https://diffoscope.org [107] https://salsa.debian.org/reproducible-builds/diffoscope/issues/78 [108] https://salsa.debian.org/reproducible-builds/diffoscope/issues/77 [109] https://salsa.debian.org/reproducible-builds/diffoscope/commit/7d6daf7 [110] https://bugs.debian.org/944882 [111] https://salsa.debian.org/reproducible-builds/diffoscope/issues/75 [112] https://bugs.debian.org/945572 [113] https://docs.python.org/3/library/exceptions.html#SyntaxWarning [114] https://salsa.debian.org/reproducible-builds/diffoscope/commit/ecef7e6 [115] https://ocaml.org/ [116] https://salsa.debian.org/reproducible-builds/diffoscope/commit/4754277 [117] https://developer.android.com/guide/topics/manifest/manifest-intro [118] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c01dc80 [119] https://www.tcpdump.org/ [120] https://salsa.debian.org/reproducible-builds/diffoscope/commit/9c66d5f [121] https://salsa.debian.org/reproducible-builds/diffoscope/commit/1c4b127 [122] https://salsa.debian.org/reproducible-builds/diffoscope/commit/69a8cc7 [123] https://salsa.debian.org/reproducible-builds/diffoscope/commit/a0f7a11 [124] https://black.readthedocs.io/en/stable/ [125] https://salsa.debian.org/reproducible-builds/diffoscope/commit/aefa5a3 [126] https://salsa.debian.org/reproducible-builds/diffoscope/commit/06d11dd [127] https://salsa.debian.org/reproducible-builds/diffoscope/commit/02497c9 [128] https://salsa.debian.org/reproducible-builds/diffoscope/commit/477584e [129] https://black.readthedocs.io/en/stable/ [130] https://salsa.debian.org/reproducible-builds/diffoscope/commit/75ea5c3 [131] https://salsa.debian.org/reproducible-builds/diffoscope/commit/4a00369 Other contributions were also made from: * Jelle van der Waa: * Add support for comparing .zst files created by Zstandard [132] compression algorithm. (#34) [133] * Mattia Rizzolo: * Install python3-all whilst running the autopkgtests [134] as we want to run the tests against all supported Python versions. [135] * Use apt-get instead of apt in our Dockerfile. [136] * Add zstd to our test dependencies after the resolution of issue #34. [138] [132] https://github.com/facebook/zstd [133] https://salsa.debian.org/reproducible-builds/issues/34 [134] https://ci.debian.net/ [135] https://salsa.debian.org/reproducible-builds/diffoscope/commit/cb74600 [136] https://salsa.debian.org/reproducible-builds/diffoscope/commit/a5c1364 [137] https://salsa.debian.org/reproducible-builds/issues/34 [138] https://salsa.debian.org/reproducible-builds/diffoscope/commit/2c87e96 strip-nondeterminism -------------------- strip-nondeterminism [139] is our tool to remove specific non- deterministic results from a completed build. This month, Chris Lamb added file as a dependency for libfile-stripnondeterminism-perl (#945212 [140]) and moved away from deprecated $ADTTMP variable [... [141] and made two uploads in total (1.6.2-1 & 1.6.3-1). [139] https://tracker.debian.org/pkg/strip-nondeterminism [140] https://bugs.debian.org/945212 [141] https://salsa.debian.org/reproducible-builds/strip-nondeterminism.git/commi… Project website --------------- There was yet more effort put into our our website [142] this month, including: * Chris Lamb dropped a duplicated use the term "community" and other words [143][144], correcting the capitalisation of GitHub [145] & GitLab [146] [147] and corrected the use of an "an" [148]. * Daniel Edgecumbe added a section on initramfs and .cpio files [149] to our Archive Metadata [150] page. [151] * Hervé Boutemy added a link to Maven Guide to Configuring for Reproducible Builds [152] to our JVM page [153]. [154] * Jelle van der Waa added Arch Linux [155]-specific links for diffoscope [156] and friends to our *Tools* [157] page. [158] [142] https://reproducible-builds.org/ [143] https://salsa.debian.org/reproducible-builds/reproducible-website.git/commi… [144] https://salsa.debian.org/reproducible-builds/reproducible-website.git/commi… [145] https://github.com/ [146] https://gitlab.org/ [147] https://salsa.debian.org/reproducible-builds/reproducible-website.git/commi… [148] https://salsa.debian.org/reproducible-builds/reproducible-website.git/commi… [149] https://reproducible-builds.org/docs/archives/#initramfs-images [150] https://reproducible-builds.org/docs/archives/ [151] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/c5… [152] https://maven.apache.org/guides/mini/guide-reproducible-builds.html [153] https://reproducible-builds.org/docs/JVM/ [154] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/93… [155] https://archlinux.org/ [156] https://diffoscope.org/ [157] https://reproducible-builds.org/docs/tools/ [158] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/0c… Test framework --------------- We operate a comprehensive Jenkins [159]-based testing framework that powers tests.reproducible-builds.org [160]. This month, the following changes were made: * Alexander Couzens (OpenWrt [161]): Fix a typo in the kirkwood architecture. [162] * Holger Levsen: * Debian: * Display newer suites first on pages showing the oldest build results. [163] * Use the fully qualified-domain name (FQDN) when specifying hostnames in our list of offline nodes [164]. [165] * Reflect that coccia.debian.org has changed IP address. [166] * Ignore the Maximum transmission Unit (MTU) [167] on eth0 when checking for host health. [168] * Perform the "/usr merge [169]" variation in the *unstable*, *experimental* and *bullseye* distributions but not on *buster*. [170] * FreeBSD [171]: Upgrade the test VM to FreeBSD 12.1. [172] * Arch Linux [173]: * Don't fail build jobs if the call to diffoscope --version fails; be a bit more verbose in the job output instead. [174][175] * Attempt to be less error prone when ending schroot [176] sessions. [177] * OpenWrt [178]: * Additionally build the brcm47xx, kirkwood, lantiq, mediatek, omap, sunxi and tegra targets. [... [179][180] * Make build job outputs easier to read and thus understand. [181] * Include the build target and subtarget in summary paragraphs at the top of report pages. [182] * Add a reminder to fix the job URL later. [183] * Misc: * Attempt to fix the PureOS [184] package set. [185] * Shorten a "HOWTO" header a tiny bit. [186] * Drop hack to fix the clock. [187] * Improve a script header; patches are even more welcome than bugs! [188] * Disable the use of the OpenSSH [189] ControlMaster feature to prevent Jenkins [190] killing connections. [191] * Make a number of improvements to our boilerplate texts/scripts. [192][... [193][... [194] * Jelle van der Waa: Skip running the Arch Linux [195] tests for continuous builds and rebuilds. [196][... [197] * Mattia Rizzolo: * Set the maximum size for HTML pages generated by diffoscope [198] to 1MB (current default is 400 KB). [199][200] * Update and improve the backup routines for the email relay system managing reproducible-builds.org. [201][202] * Vagrant Cascadian: * Ensure OpenSSH [203] authorized_keys files are processed in the correct directory regardless of where they are run from. [204] * Reduce the level of parallelism on armhf architectures with a lot of cores to reduce swapping on highly parallel builds, additionally ensuring level of parallelism are odd and even numbers on the first and second builds respectfully. [205] [159] https://jenkins.io/ [160] https://tests.reproducible-builds.org [161] https://openwrt.org/ [162] https://salsa.debian.org/qa/jenkins.debian.net/commit/369038e3 [163] https://salsa.debian.org/qa/jenkins.debian.net/commit/aa2ace2f [164] https://salsa.debian.org/qa/jenkins.debian.net/blob/HEAD/jenkins-home/offli… [165] https://salsa.debian.org/qa/jenkins.debian.net/commit/8266e978 [166] https://salsa.debian.org/qa/jenkins.debian.net/commit/25964ef8 [167] https://en.wikipedia.org/wiki/Maximum_transmission_unit [168] https://salsa.debian.org/qa/jenkins.debian.net/commit/1a549068 [169] https://wiki.debian.org/UsrMerge [170] https://salsa.debian.org/qa/jenkins.debian.net/commit/a9919410 [171] https://www.freebsd.org/ [172] https://salsa.debian.org/qa/jenkins.debian.net/commit/75e87e5d [173] https://www.archlinux.org/ [174] https://salsa.debian.org/qa/jenkins.debian.net/commit/de6dce51 [175] https://salsa.debian.org/qa/jenkins.debian.net/commit/8ca7241c [176] https://wiki.debian.org/Schroot [177] https://salsa.debian.org/qa/jenkins.debian.net/commit/32b9fe26 [178] https://openwrt.org/ [179] https://salsa.debian.org/qa/jenkins.debian.net/commit/c40b5f5b [180] https://salsa.debian.org/qa/jenkins.debian.net/commit/c40b5f5b [181] https://salsa.debian.org/qa/jenkins.debian.net/commit/6baae828 [182] https://salsa.debian.org/qa/jenkins.debian.net/commit/3f67936e [183] https://salsa.debian.org/qa/jenkins.debian.net/commit/98c3e2c6 [184] https://pureos.net/ [185] https://salsa.debian.org/qa/jenkins.debian.net/commit/c9066d49 [186] https://salsa.debian.org/qa/jenkins.debian.net/commit/e6494947 [187] https://salsa.debian.org/qa/jenkins.debian.net/commit/3a7ef746 [188] https://salsa.debian.org/qa/jenkins.debian.net/commit/ebefdd51 [189] https://openssh.org/ [190] https://jenkins.io/ [191] https://salsa.debian.org/qa/jenkins.debian.net/commit/81273bf4 [192] https://salsa.debian.org/qa/jenkins.debian.net/commit/c3759e97 [193] https://salsa.debian.org/qa/jenkins.debian.net/commit/35c2b25f [194] https://salsa.debian.org/qa/jenkins.debian.net/commit/2326d159 [195] https://archlinux.org/ [196] https://salsa.debian.org/qa/jenkins.debian.net/commit/e16b3ee7 [197] https://salsa.debian.org/qa/jenkins.debian.net/commit/97145223 [198] https://diffoscope.org [199] https://salsa.debian.org/qa/jenkins.debian.net/commit/0a56df32 [200] https://salsa.debian.org/qa/jenkins.debian.net/commit/e2ce7d08 [201] https://salsa.debian.org/reproducible-builds/rb-mailx-ansible/commit/9563162 [202] https://salsa.debian.org/reproducible-builds/rb-mailx-ansible/commit/734de20 [203] https://openssh.org/ [204] https://salsa.debian.org/qa/jenkins.debian.net/commit/0316d461 [205] https://salsa.debian.org/qa/jenkins.debian.net/commit/620fa54d The usual node maintenance was performed by Holger Levsen. [206][207][208][209] [206] https://salsa.debian.org/qa/jenkins.debian.net/commit/ec74bdf4 [207] https://salsa.debian.org/qa/jenkins.debian.net/commit/37d071e5 [208] https://salsa.debian.org/qa/jenkins.debian.net/commit/06c70874 [209] https://salsa.debian.org/qa/jenkins.debian.net/commit/c3cd0018 Contributing ============ If you are interested in contributing the Reproducible Builds project, please visit the Contribute [210] page on our website. However, you can get in touch with us via: * IRC: #reproducible-builds on irc.oftc.net. * Twitter: https://twitter.com/ReproBuilds * Mailing list: rb-general(a)lists.reproducible-builds.org [211] [210] https://reproducible-builds.org/contribute/ [211] https://lists.reproducible-builds.org/listinfo/rb-general This month's report was written by Arnout Engelen, Chris Lamb, Holger Levsen, Jelle van der Waa, Bernhard M. Wiedemann and Vagrant Cascadian. It was subsequently reviewed by a bunch of Reproducible Builds folks on IRC and the mailing list. -- Chris Lamb https://puri.sm

1 0

October 2019 in Reproducible Builds
by Chris Lamb 07 Nov '19

07 Nov '19

==================================================================== o ⬋ ⬊ October 2019 in Reproducible Builds o o ⬊ ⬋ https://reproducible-builds.org/reports/2019-10/ o ==================================================================== Welcome to the October 2019 report from the Reproducible Builds project. :) In our monthly reports we attempt outline the most important things that we have been up to recently. As a reminder on what our little project is all about, whilst anyone can inspect the source code of free software for malicious changes most software is distributed to end users or servers as precompiled binaries. Reproducible builds tries to ensure that no changes have been made during these compilation processes by promising identical results are always generated from a given source, allowing multiple third-parties to come to a consensus on whether a build was compromised. In this month's report, we will cover: * Media coverage & conferences — Reproducible builds in Belfast & science * Reproducible Builds Summit 2019 — Registration & attendees, etc. * Distribution work — The latest work in Debian, OpenWrt, openSUSE, and more... * Software development — More diffoscope development, etc. * Getting in touch — How to contribute & get in touch If you are interested in contributing to our venture, please visit our *Contribute* page on our website. Media coverage & conferences ============================ Jonathan McDowell [2] gave an introduction on Reproducible Builds in Debian [3] at the Belfast Linux User Group. Whilst not strictly related to reproducible *builds*, Sean Gallagher from Ars Technica wrote an article entitled *Researchers find bug in Python script may have affected hundreds of studies* [6]: > A programming error in a set of Python scripts commonly used for > computational analysis of chemistry data returned varying results based > on which operating system they were run on. [ 2] https://www.earth.li/~noodles/ [ 3] https://www.meetup.com/belfast-lug/events/264951460/ [ 6] https://arstechnica.com/information-technology/2019/10/chemists-discover-cr… Reproducible Builds Summit 2019 =============================== Registration for our fifth annual Reproducible Builds summit that will take place between the 1st and 8th December in Marrakesh, Morocco has opened and invitations have been sent out. Similar to previous incarnations of the event, the heart of the workshop will be three days of moderated sessions with surrounding "hacking" days and will include a huge diversity of participants from Arch Linux, coreboot, Debian, F-Droid, GNU Guix, Google, Huawei, in-toto, MirageOS, NYU, openSUSE, OpenWrt, Tails, Tor Project and many more. We are still seeking additional sponsorship for the event. Sponsoring enables us to enable the attendance of people who would not otherwise be able to attend. If you or your company would be able to sponsor the event, please contact <info(a)reproducible-builds.org>. If you would like to learn more about the event and how to register, please visit our dedicated event page: https://reproducible-builds.org/events/Marrakesh2019/ Distribution work ================= GNU Guix [10] announced that they had significantly reduced the size of their "bootstrap seed" [11] by replacing binutils [12], GCC [13] and glibc [14] with smaller alternatives resulting in the package manager "possessing a formal description of how to build all underlying software" in a reproducible way from a mere 120MB seed. OpenWrt [15] is a Linux-based operating system targeting wireless network routers and other embedded devices. This month Paul Spooren (*aparcar*) posted a patch to their mailing list adding KCFLAGS to the kernel build flags [16] to make it easier to rebuild the official binaries. Bernhard M. Wiedemann posted his monthly Reproducible Builds status update [17] for the openSUSE [18] distribution which describes how rpm was updated [19] to run most builds with the -flto=auto argument, saving mirror disk space/bandwidth. In addition, maven-javadoc-plugin received a toolchain patch [20] (originating from Debian [21]) in order to normalise a date. [10] http://guix.gnu.org/ [11] https://guix.gnu.org/blog/2019/guix-reduces-bootstrap-seed-by-50/ [12] https://en.wikipedia.org/wiki/GNU_Binutils [13] https://gcc.gnu.org/ [14] https://www.gnu.org/software/libc/ [15] https://openwrt.org/ [16] https://lists.infradead.org/pipermail/openwrt-devel/2019-October/019248.html [17] https://lists.opensuse.org/opensuse-factory/2019-10/msg00367.html [18] https://opensuse.org/ [19] https://build.opensuse.org/request/show/732635 [20] https://build.opensuse.org/request/show/735873 § ,''`. : :' : `. `'` `- In Debian this month Didier Raboud (*OdyX*) started a discussion on the debian-devel [22] mailing list regarding building Debian source packages in a reproducible manner (thread index at [23]). In addition, Lukas Pühringer prepared an upload of in-toto [24], a framework to protect supply chain integrity by the Secure Systems Lab [25] at New York University [26] which was uploaded by Holger Levsen. Holger Levsen started a new section on the Debian wiki [27] to centralise to document the progress made on various Debian-specific reproducibility issues [28] and noticed that the "essential" package set in the *bullseye* distribution [29] became unreproducible again, likely due to a a bug in Perl [30] itself. Holger also restarted a discussion [31] on Debian bug #774415 [32] which requests that the devscripts collection of utilities that "make the life of a Debian package maintainer easier" adds a script/wrapper to enable easier end-user testing of whether a package is reproducible. Johannes Schauer (*josch*) explained that their mmdebstrap [33] tool can create bit-for-bit identical [34] Debian chroots [35] of the *unstable* and *buster* distributions for both the essential and minbase bootstrap "variants" [36], and Bernhard M. Wiedemann contributed to a discussion [37] regarding adding a "global" build switch to enable/disable Profile-Guided Optimisation [38] (PGO) and Link-time optimisation [39] in the dpkg-buildflags tool, nothing that "overall it is still very hard to get reproducible builds with PGO enabled." 64 reviews of Debian packages were added, 10 were updated and 35 were removed this month adding to our knowledge about identified issues[40]. Three new types were added by Chris Lamb (*lamby*): nondeterministic_output_in_code_generated_by_ros_genpy [41], nondeterministic_ordering_in_include_graphs_generated_by_doxygen[42] & nondeterministic_defaults_in_documentation_generated_by_pyth- on_traitlets [43]. Lastly, there was a far-reaching discussion regarding the correctness and suitability of setting the TZ environment variable [44] to UTC when it was noted that the value UTC0 [45] was "technically" more correct. [21] https://salsa.debian.org/java-team/maven-javadoc-plugin/blob/master/debian/… [22] https://lists.debian.org/debian-devel/ [23] https://lists.debian.org/debian-devel/2019/10/threads.html#00301 [24] https://in-toto.io/ [25] https://ssl.engineering.nyu.edu/ [26] https://engineering.nyu.edu/ [27] https://wiki.debian.org/ [28] https://wiki.debian.org/ReproducibleBuilds#Solved_issues [29] https://tests.reproducible-builds.org/debian/buster/amd64/pkg_set_essential… [30] https://bugs.debian.org/791362 [31] https://bugs.debian.org/774415#270 [32] https://bugs.debian.org/774415 [33] https://tracker.debian.org/mmdebstrap [34] https://lists.debian.org/debian-devel/2019/10/msg00101.html [35] https://en.wikipedia.org/wiki/Chroot [36] https://sources.debian.org/src/debootstrap/1.0.116/debootstrap.8/#L78-L85 [37] https://bugs.debian.org/940571#26 [38] https://en.wikipedia.org/wiki/Profile-guided_optimization [39] https://en.wikipedia.org/wiki/Interprocedural_optimization [40] https://tests.reproducible-builds.org/debian/index_issues.html [41] https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/d219… [42] https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/2577… [43] https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/3ecd… [44] https://en.wikipedia.org/wiki/Environment_variable#Unix_2 [45] https://lists.reproducible-builds.org/pipermail/rb-general/2019-October/001… Software development ==================== 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: * Bernhard M. Wiedemann: * keeperrl [46] (merged, date) * sphinx-doc [47] (nondeterminism from parallelism via Sphinx [48]) * vlc [49] (sort tar) * A number of expiring SSL testing certificates have been extended to 2049 to fix future builds: * python-M2Crypto [50] * python-aiosmtplib [51] * python-distlib [52] * python-geventhttpclient [53] * python-moto [54] (has a remaining year 2038 bug) * python-oslo.service [55] * python-thriftpy2 [56] [46] https://github.com/miki151/keeperrl/pull/1489 [47] https://github.com/sphinx-doc/sphinx/issues/6714 [48] http://www.sphinx-doc.org/en/master/ [49] https://mailman.videolan.org/pipermail/vlc-devel/2019-October/128188.html [50] https://gitlab.com/m2crypto/m2crypto/merge_requests/235 [51] https://github.com/cole/aiosmtplib/pull/92 [52] https://bitbucket.org/pypa/distlib/pull-requests/44/extend-test-cert-validi… [53] https://github.com/gwik/geventhttpclient/pull/115 [54] https://github.com/spulec/moto/pull/2500 [55] https://review.opendev.org/687822 [56] https://github.com/Thriftpy/thriftpy2/pull/91 * Chris Lamb (*lamby*): * #934698 filed against libchamplain (merged upstream [59]). * #941714 filed against bst-external. * #941715 filed against checkinstall. * #941716 filed against gobject-introspection. * #942005 filed against elph. * #942006 filed against squeak-plugins-scratch. * #942009 filed against stgit. (forwarded upstream [72]). * #942342 filed against traitlets (forwarded upstream [75]). * #942479 filed against frobby. * #942767 filed against python-oslo.reports. * #942847 filed against cloudkitty. * #942848 filed against designate. * #943471 filed against khard (forwarded upstream [90]). * #943674 filed against flask (forwarded upstream [93]). * #943694 filed against ros-genpy (forwarded upstream [96]). * #943829 filed against pmemkv. * #943954 filed against tm-align * #943956 filed against snakemake (forwarded upstream [103]) * spirv-tools [104]. * #942867 & #942870: Filed against r-base (not respecting nocheck and nodoc Debian build profiles [87]). [59] https://gitlab.gnome.org/GNOME/libchamplain/merge_requests/9 [72] https://github.com/ctmarinas/stgit/pull/43 [75] https://github.com/ipython/traitlets/pull/535 [87] https://wiki.debian.org/BuildProfileSpec [90] https://github.com/scheibler/khard/pull/233 [93] https://github.com/pallets/flask/pull/3408 [96] https://github.com/ros/genpy/pull/110 [103] https://github.com/snakemake/snakemake/pull/80 [104] https://github.com/KhronosGroup/SPIRV-Tools/pull/2982 * Mattias Ellert: * #942671 filed against doxygen. Lastly, a request from Steven Engler [107] to sort fields in the PKG-INFO files generated by the setuptools [108] Python module build utilities was resolved [109] by Jason R. Coombs [110] and Vagrant Cascadian added SOURCE_DATE_EPOCH [111] support to LTSP [112]'s manual page generation. [106] https://tracker.debian.org/pkg/doxygen [107] https://github.com/stevenengler [108] https://pypi.org/project/setuptools/ [109] https://github.com/pypa/setuptools/pull/1305#issuecomment-538810632 [110] https://www.jaraco.com/ [111] https://reproducible-builds.org/docs/source-date-epoch/ [112] https://ltsp.github.io/ strip-nondeterminism & reprotest -------------------------------- strip-nondeterminism [113] is our tool to remove specific non- deterministic results from successful builds. This month, Chris Lamb made a number of changes including uploading version 1.6.1-1 was to Debian unstable [114]. This dropped a bug_803503.zip test fixture as it is no longer compatible with the latest version of Perl's Archive::Zip [115] module (#940973) [116]. 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, Iñaki Malerba updated our Salsa CI [117] scripts [118] as well as adding a --control-build parameter [119]. Holger Levsen uploaded the package as 0.7.10, bumping the Debian "standards version" [120] to 4.4.1 [121]. [113] https://tracker.debian.org/pkg/strip-nondeterminism [114] https://tracker.debian.org/news/1071922/accepted-strip-nondeterminism-161-1… [115] https://metacpan.org/pod/Archive::Zip [116] https://bugs.debian.org/940973 [117] https://salsa.debian.org [118] https://salsa.debian.org/reproducible-builds/reprotest/commit/a547967 [119] https://salsa.debian.org/reproducible-builds/reprotest/commit/52f6eeb [120] https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-standard… [121] https://salsa.debian.org/reproducible-builds/reprotest/commit/fa0e286 diffoscope ---------- diffoscope [123] is our in-depth and content-aware diff utility that can locate and diagnose reproducibility issues. It is run countless times a day on our testing infrastructure [124] and is essential for identifying fixes and causes of non-deterministic behaviour. [123] https://diffoscope.org [124] https://tests.reproducible-builds.org/debian/reproducible.html This month, Chris Lamb (*lamby*) made the following changes, including uploading versions 126, 127, 128 and 129 to the Debian *unstable* distribution: * Disassembling and reporting on files related to the R (programming language) [125]): * Expose an .rdb file's absolute paths in the semantic/human- readable output, not hidden deep in a hexdump. [126] * Rework and refactor the handling of .rdb files with respect to locating the parallel .rdx prior to inspecting the file to ensure that we do not add files to the user's filesystem in the case of directly comparing two .rdb files or — worse — overwriting a file in is place. [127] * Query the container for the full path of the parallel .rdx file to the .rdb file as well as looking in the same directory. This ensures that comparing two Debian packages shows any varying path. [128] * Correct the matching of .rds files by also detecting newer versions of this file format. [129] * Don't read the site and user environment when comparing .rdx, .rdb or .rds files by using Rscript's --vanilla option. [130][131] * Ensure all object names are displayed, including ones beginning with a fullstop (.) [132] and sort package fields when dumping data from .rdb files [133]. * Mask/hide standard error when processing .rdb files [134] and don't include useless/misleading NULL when dumping data from them. [135] * Format package contents as foo = bar rather than using ugly and misleading brackets, etc. [136] and include the object's type [137]. * Don't pass our long script to parse .rdb files via the command line; use standard input [138]) instead. [139] * Call the deparse function to ensure that we do not error out and revert to a binary diff when processing .rdb files with internal "vector" types; they do not automatically coerce to strings. [140] * Other misc/cosmetic changes. [141][142][143] * Output/logging: * When printing an error from a command, format the command for the user. [144] * Truncate very long command lines when displaying them as an external source of data. [145] * When formatting command lines ensure newlines and other metacharacters appear escaped as \n, etc. 146][147] * When displaying the standard error from commands, ensure we use the escaped version. [148] * Use "exit code" over "return code" terminology when referring to UNIX error codes in displayed differences. [149] * Internal API: * Add ability to pass bytestring [150] input to external commands. [151] * Split out command-line formatting into a separate utility function. [152] * Add support for easily masking the standard error of commands. [153][154] * To match the libarchive [155] container, raise a KeyError exception if we request an invalid member from a directory. [156] * Correct string representation output in the traceback when we cannot locate a specific item in a container. [157] * Misc: * Move build-dependency on python-argcomplete to its Python 3 equivalent to facilitate Python 2.x removal. (#942967 [158]) * Track and report on missing Python modules. (#72 [159]) * Move from deprecated $ADTTMP to $AUTOPKGTEST_TMP in the autopkgtests [160]. [161] * Truncate the tcpdump expected diff to 8KB (from ~600KB). [162] * Try and ensure that new test data files are generated dynamically, ie. at least no new ones are added without "good" reasons. [163] * Drop unused BASE_DIR global in the tests. [164] [125] https://en.wikipedia.org/wiki/R_(programming_language [126] https://salsa.debian.org/reproducible-builds/diffoscope/commit/f1e80ca [127] https://salsa.debian.org/reproducible-builds/diffoscope/commit/ea4c94a [128] https://salsa.debian.org/reproducible-builds/diffoscope/commit/322a568 [129] https://salsa.debian.org/reproducible-builds/diffoscope/commit/2c9fbc1 [130] https://salsa.debian.org/reproducible-builds/diffoscope/commit/b8236d4 [131] https://salsa.debian.org/reproducible-builds/diffoscope/commit/f8e436d [132] https://salsa.debian.org/reproducible-builds/diffoscope/commit/1f89609 [133] https://salsa.debian.org/reproducible-builds/diffoscope/commit/9f60724 [134] https://salsa.debian.org/reproducible-builds/diffoscope/commit/0092be0 [135] https://salsa.debian.org/reproducible-builds/diffoscope/commit/cb83076 [136] https://salsa.debian.org/reproducible-builds/diffoscope/commit/343d01d [137] https://salsa.debian.org/reproducible-builds/diffoscope/commit/895f398 [138] https://en.wikipedia.org/wiki/Standard_streams#Standard_input_(stdin [139] https://salsa.debian.org/reproducible-builds/diffoscope/commit/07a013f [140] https://salsa.debian.org/reproducible-builds/diffoscope/commit/91d7029 [141] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c23651e [142] https://salsa.debian.org/reproducible-builds/diffoscope/commit/face6fb [143] https://salsa.debian.org/reproducible-builds/diffoscope/commit/f23f2b4 [144] https://salsa.debian.org/reproducible-builds/diffoscope/commit/138aac1 [145] https://salsa.debian.org/reproducible-builds/diffoscope/commit/ecccd71 [146] https://salsa.debian.org/reproducible-builds/diffoscope/commit/691ce88 [147] https://salsa.debian.org/reproducible-builds/diffoscope/commit/338dbdf [148] https://salsa.debian.org/reproducible-builds/diffoscope/commit/bbfdb57 [149] https://salsa.debian.org/reproducible-builds/diffoscope/commit/6a8251d [150] https://docs.python.org/3/library/stdtypes.html#bytes [151] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c525ba9 [152] https://salsa.debian.org/reproducible-builds/diffoscope/commit/f784d2c [153] https://salsa.debian.org/reproducible-builds/diffoscope/commit/9b5c5fd [154] https://salsa.debian.org/reproducible-builds/diffoscope/commit/2e33ad6 [155] https://www.libarchive.org/ [156] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c98e40f [157] https://salsa.debian.org/reproducible-builds/diffoscope/commit/2478e9c [158] https://bugs.debian.org/942967 [159] https://salsa.debian.org/diffoscope/reproducible-builds/diffoscope [160] https://ci.debian.net/ [161] https://salsa.debian.org/reproducible-builds/diffoscope/commit/f06c44f [162] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c6517e6 [163] https://salsa.debian.org/reproducible-builds/diffoscope/commit/e83b360 [164] https://salsa.debian.org/reproducible-builds/diffoscope/commit/7b44c80 In addition, Mattia Rizzolo updated our tests to run against all supported Python versions [165] and to exit with a UNIX exit status [166] of 2 instead of 1 in case of running out of disk space [167]. Lastly Vagrant Cascadian updated diffoscope 126 [168] and 129 [169] in GNU Guix [170], and updated inputs for additional test suite coverage [171]. trydiffoscope [172] is the web-based version of diffoscope [173] and this month Chris Lamb migrated the tool to depend on the python3-docutils package over python-docutils to allow for Python 2.x removal (#943293 [174]) as well as updating the packaging to the latest Debian standards and conventions [175][176][177]. [165] https://salsa.debian.org/reproducible-builds/diffoscope/commit/23c6112 [166] https://en.wikipedia.org/wiki/Exit_status [167] https://salsa.debian.org/reproducible-builds/diffoscope/commit/59267e8 [168] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=c3704ecaa537f96dfca2f… [169] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=d332fd860f89ed426a2b0… [170] https://guix.gnu.org/ [171] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=36f5f23c1af640782aa47… [172] https://try.diffoscope.org [173] https://diffoscope.org [174] https://bugs.debian.org/943293 [175] https://salsa.debian.org/reproducible-builds/trydiffoscope/commit/75e8b14 [176] https://salsa.debian.org/reproducible-builds/trydiffoscope/commit/95d7faf [177] https://salsa.debian.org/reproducible-builds/trydiffoscope/commit/01df0a4 Project website --------------- URL: https://reproducible-builds.org/ There was yet more effort put into our our website this month, including Chris Lamb improving the formatting of reports [179][180][181][182][183] and tidying the new "Testing framework" [184] links [185], etc. In addition, Holger Levsen add the Tor Project's Reproducible Builds Manager [186] to our "Who is Involved? [187]" page and Mattia Rizzolo dropped a literal HTML element [188]. [179] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/db… [180] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/45… [181] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/f3… [182] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/46… [183] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/ad… [184] https://tests.reproducible-builds.org/debian/reproducible.html [185] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/13… [186] https://rbm.torproject.org/ [187] https://reproducible-builds.org/who/ [188] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/8b… 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: * Debian-specific changes: * Add a script to ease powercycling x86 and arm64 nodes. [192][193] * Don't create suite-based directories for buildinfos.debian.net [194]. [195] * Make all four suites being tested shown in a single row on the performance page. [196] * OpenWrt changes: * Only run jobs every third day. [198] * Create jobs to run the reproducible_openwrt_rebuild.py script today and in the future. [199] * Mattia Rizzolo: * Add some packages that were lost while updating to *buster*. [200] * Fix the auto-offline functionality by checking the content of the permalinks file instead of following the lastSuccessfulBuild that no longer being updated. [201] * Paul Spooren (OpenWrt [202]): * Add a reproducible_common utilities file. [203] * Update the openwrt-rebuild script to to use schroot. [204] * Use unbuffered [205] Python output [206] as well as fixing newlines [207][208] The usual node maintenance was performed by Holger Levsen [209][210], Mattia Rizzolo [211][212][213] and Vagrant Cascadian [214][215][216]. [192] https://salsa.debian.org/qa/jenkins.debian.net/commit/8a69efc8 [193] https://salsa.debian.org/qa/jenkins.debian.net/commit/64d87e9e [194] https://buildinfos.debian.net/ [195] https://salsa.debian.org/qa/jenkins.debian.net/commit/e4a15fc4 [196] https://salsa.debian.org/qa/jenkins.debian.net/commit/cd8f363f [198] https://salsa.debian.org/qa/jenkins.debian.net/commit/d75af2d4 [199] https://salsa.debian.org/qa/jenkins.debian.net/commit/fa9febb0 [200] https://salsa.debian.org/qa/jenkins.debian.net/commit/69c765d7 [201] https://salsa.debian.org/qa/jenkins.debian.net/commit/a395b84f [202] https://openwrt.org [203] https://salsa.debian.org/qa/jenkins.debian.net/commit/94dcfb4c [204] https://salsa.debian.org/qa/jenkins.debian.net/commit/f73cf72f [205] https://eklitzke.org/stdout-buffering [206] https://salsa.debian.org/qa/jenkins.debian.net/commit/e2630fb7 [207] https://salsa.debian.org/qa/jenkins.debian.net/commit/dcbacce5 [208] https://salsa.debian.org/qa/jenkins.debian.net/commit/0443a133 [209] https://salsa.debian.org/qa/jenkins.debian.net/commit/cfbc58fb [210] https://salsa.debian.org/qa/jenkins.debian.net/commit/5f9424da [211] https://salsa.debian.org/qa/jenkins.debian.net/commit/9d3df188 [212] https://salsa.debian.org/qa/jenkins.debian.net/commit/88db9f0a [213] https://salsa.debian.org/qa/jenkins.debian.net/commit/5cdad8fd [214] https://salsa.debian.org/qa/jenkins.debian.net/commit/974bca24 [215] https://salsa.debian.org/qa/jenkins.debian.net/commit/8d4b533c [216] https://salsa.debian.org/qa/jenkins.debian.net/commit/3da81a76 Getting in touch ================ If you are interested in contributing the Reproducible Builds project, please visit our *Contribute* [217] page on our website. However, you can get in touch with us via: * Mailing list: rb-general(a)lists.reproducible-builds.org [218] * IRC: #reproducible-builds on irc.oftc.net. * Twitter: @ReproBuilds / https://twitter.com/ReproBuilds [217] https://reproducible-builds.org/contribute/ [218] https://lists.reproducible-builds.org/listinfo/rb-general This month's report was written by Bernhard M. Wiedemann, Chris Lamb, Holger Levesen and Vagrant Cascadian. It was subsequently reviewed by a bunch of Reproducible Builds folks on IRC and the mailing list. Best wishes, -- o ⬋ ⬊ Chris Lamb o o reproducible-builds.org ⬊ ⬋ o

1 0

Bits from PureOS | Sharks!
by Jeremiah C. Foster 25 Oct '19

25 Oct '19

Hi, Summer is here on the East Coast of North America and that means another edition of Bits from PureOS. And no, I wasn't eaten by a shark last week on Cape Cod, but thanks for asking. To reiterate, the long-running topics we're responsible for are; 1. Reproducible builds 2. Supporting Pureboot and Purism hardware 3. Continuous delivery of PureOS 4. PureOS store (and application discovery) To that list I think we ought to add; 5. PureOS Security 6. Additional packages for PureOS We have already a security mailing list here: https://lists.puri.sm/listinfo/security We should likely develop a plan for its use. Other security topics perhaps ought to be discussed privately and I intend to kick off the topic with stakeholders. On the reproducible builds front you can follow the thread here; https://lists.puri.sm/pipermail/pureos-project/2019-July/000177.html What is happening is we're trying to adjust various time stamps that various tools insert into a given build. Those time stamps vary between builds (of course, because any two builds occur at different times). Lamby has patched many of the tools and I'm trying to find the right context to inform the tools that they're to use the standardised time stamp. Discussion with various folks has led us to cease maintaining PureBrowser. The reasons are pretty simple; we are investing in the GNOME ecosystem and GNOME web runs as a flatpak bringing in a bit of isolation to the browser which adds an additional layer of security. I think that we should make an announcement about this going forward in various places since there is often much discussion on browsers in our forums. Upcoming discussions on how to seed a build of PureOS for the L5 should be interesting, I plan to send out an invitation for discussing this in the next day or so. More info to come. Lastly, getting apps into PureOS needs to be better documented. I'm doing some packaging but am struggling with getting pbuilder to play nicely with my requests to pull in older versions of software. If we had clear instructions on how to build a PureOS image for pbuilder that would help me immensely. I'll reach out to folks regarding this since I'm certain that the knowledge needed is available. Also, uploads to Laniakea of certain packages are failing occasionally, something Guido has pointed out. We ought to speak with him to determine what the issues are and to smooth out the upload process. As always, feedback most welcome.

6 20

Lollypop in PureOS
by Andreas Ronnquist 07 Oct '19

07 Oct '19

I have uploaded new upstream versions of Lollypop to Debian unstable (1.1.14.16-4) and also I have uploaded release candidates (1.1.9*) to Debian experimental - I believe a stable upstream release of 1.2 is not far away now. How can I get these into Pureos? I believe the version in Pureos is way back at 1.1.14.11-1 (Thats what I can find on repo.pureos.net) - development in Lollypop upstream have been really intense lately, and I have tried my best to keep Debian up to date, at least in experimental when it comes to RC releases. Also, I am not really sure on how the different releases of PureOS is handled - I believe you have a special repository for the Phone OS, and keep non-phone OS separate from that? And lastly - This kind of question - maybe you would prefer this in tracker.pureos.net? Many thanks for all your work on free software stuff of all sorts - really appreciated! best regards -- Andreas Rönnquist mailinglists(a)gusnan.se andreas(a)ronnquist.net gusnan(a)debian.org [Please don't CC me, if I mail to a mailinglist, I am subscribed to it.]

2 1

PureOS 10 (Byzantium) is open!
by Matthias Klumpp 01 Oct '19

01 Oct '19

[ I messed up all version numbers in the previous mail, so here it is again, corrected ] Hi! As of now, PureOS 9 (Amber) is frozen, all future uploads to that suite will go to the respective "*-updates" pocket. This means that PureOS 11 (Byzantium) is now open for business! All uploads to "landing" will migrate to that suite, and so do all uploads to the "byzantium" suite. So, if you want to upload to the next PureOS development release, just put "byzantium" as suite name into your changelog file. If you want to switch to using byzantium, replace "amber" with "byzantium" in your PureOS sources.list. Please let me know if you experience any issues! Happy hacking! Matthias

2 2

PureOS 11 (Byzantium) is open!
by Matthias Klumpp 30 Sep '19

30 Sep '19

Hi! As of now, PureOS 10 (Amber) is frozen, all future uploads to that suite will go to the respective "*-updates" pocket. This means that PureOS 11 (Byzantium) is now open for business! All uploads to "landing" will migrate to that suite, and so do all uploads to the "byzantium" suite. So, if you want to upload to the next PureOS development release, just put "byzantium" as suite name into your sources.list Please let me know if you experience any issues! Happy hacking! Matthias

1 1

Bits from PureOS | Hephaestus
by Jeremiah C. Foster 27 Sep '19

27 Sep '19

Hello! If you didn't know - "Amber" is out! It's full name is "The new stable release of PureOS 9.0 Hephaestus codename Amber." Hopefully you didn't notice, although we've recently had a blog post.[0] If you didn't notice it is because the entire process was quite smooth. I firmly believe this stable release will help our customers. We need release notes for Amber, there have been a couple requests for them. I think that maybe we can do a high-level info page? Or something along the line of a "NEWS" page? Feedback most welcome. Also, you'll note that I said PureOS 9.0 above but that the actual ISOs say PureOS 8.0. What gives? Well the change will be made shortly as we update the myriad places we have the version number. Apropos downloads, we have a new mirror page[1] and new mirrors[2] as well as the requisite blog post.[3] We've had discussions about mirrors before but when the topic came up again on Riot there was an urgency that matched the need I think and slow downloads will only get slower as we add devices. I've put in a request to the FSF to add PureOS to their mirror[4] and while they're busy, the response was generally positive. There has been a bit of pause in forward movement of reproducible builds. This is largely due to the fact that the cron jobs needed updating since 'green' became 'amber' but that has been fixed and I believe we should have some good data to work with. The diffs from diffoscope have been shrinking in size but I worry that not all the software in our amber release, which is based on Buster, is patched to the latest versions needed for a "clean" diffoscope run. I'm also having trouble with diffoscope getting killed now, I'll document that in a bug report on squash and friends. We also run some tarballs of a minimal PureOS image through diffoscope and the diff is nice and small, but there needs to be some clean-up before that URL is ready. I'm working on the RYF application for the Librem Key. I've been in communcation with the FSF, hope to hear back soon. More soon, thanks for reading! Jeremiah 0. https://puri.sm/posts/pureos-rolls-on-as-stable/ 1. https://tracker.pureos.net/w/installation_guide/mirrors/ 2. https://mirrors.sonic.net/pureos/repo/ 3. https://puri.sm/posts/mirrors-for-speedier-downloads/ 4. https://mirror.fsf.org/

2 2

PureOS 9 (Amber) 2019/09/26 images ready for testing
by Matthias Klumpp 27 Sep '19

27 Sep '19

Hi! We have new images for testing. Things to look at, as always: * Does the image boot cleanly? * Does the Live installer work? * Does the OEM installer work? * Does the OEM initial setup work as expected? * Does the respective desktop function as expected? * Any noticeable bugs/regressions? You can find the images for the respective flavors here: GNOME Live: https://downloads.pureos.net/live/gnome/2019-09-26/ GNOME OEM: https://downloads.pureos.net/oem/gnome/2019-09-26/ Plasma Live: https://downloads.pureos.net/live/plasma/2019-09-26/ I already tested the images and found no noticeable issues, but having more eyes on them before we change the default download links is always good. Happy testing! Cheers, Matthias

2 1

2025

2024

2023

2022

2021

2020

2019

2018

PureOS-project