Reproducible Builds in February 2025🔹
Chris Lamb
chris at reproducible-builds.org
Wed Mar 5 14:20:49 UTC 2025
--------------------------------------------------------------------
o
⬋ ⬊ February 2025 in Reproducible Builds
o o
⬊ ⬋ https://reproducible-builds.org/reports/2025-02/
o
--------------------------------------------------------------------
Welcome to the second report in 2025 from the Reproducible Builds
project!
Our monthly reports outline what we've been up to over the past
month, and highlight items of news from elsewhere in the
increasingly-important area of software supply-chain security. As
usual, however, if you are interested in contributing to the
Reproducible Builds project, please visit the "Contribute" [0] page
on our website.
[0] https://reproducible-builds.org/contribute/
§
Table of contents:
* Reproducible Builds at FOSDEM 2025
* Reproducible Builds at PyCascades 2025
* Does Functional Package Management Enable Reproducible Builds at Scale?
* reproduce.debian.net updates
* Upstream patches
* Distribution work
* diffoscope & strip-nondeterminism
* Website updates
* Reproducibility testing framework
§
Reproducible Builds at FOSDEM 2025
----------------------------------
Similar to last year's event, there was considerable activity
regarding Reproducible Builds at FOSDEM 2025 [2], held on on 1st and
2nd February this year in Brussels, Belgium. We count at least four
talks related to reproducible builds. (You can also read our news
report from last year's event [3] in which Holger Levsen presented
in the main track.)
[2] https://fosdem.org/2025/
[3] https://reproducible-builds.org/news/2024/02/08/reproducible-builds-at-fosdem-2024/
Jelle van der Waa, Holger Levsen and kpcyrd presented in the
"Distributions" track on "A Tale of several distros joining forces
for a common goal" [4]. In this talk, three developers from two
different Linux distributions (Arch Linux and Debian), discuss
this goal — which is, of course, reproducible builds. The presenters
discuss both what is shared and different between the two efforts,
touching on the history and future challenges alike. The slides of
this talk [5] are available to view, as is the full video [6]
(30m02s). The talk was also discussed on Hacker News [7].
[4] https://fosdem.org/2025/schedule/event/fosdem-2025-6479-a-tale-of-several-distros-joining-forces-for-a-common-goal-reproducible-builds/
[5] https://reproducible-builds.org/_lfs/presentations/2025-02-02-a-tale-of-several-distros-joining-forces-for-a-common-goal-reproducible-builds/
[6] https://video.fosdem.org/2025/h1302/fosdem-2025-6479-a-tale-of-several-distros-joining-forces-for-a-common-goal-reproducible-builds.av1.webm
[7] https://news.ycombinator.com/item?id=42982270
Zbigniew Jędrzejewski-Szmek presented in the ever-popular "Python"
track a on "Rewriting .pyc files for fun and reproducibility" [8],
i.e. the bytecode files generated by Python in order to speed up
module imports: "It's been known for a while that those are not
reproducible: on different architectures, the bytecode for exactly
the same sources ends up slightly different." The slides of this
talk [9] are available, as is the full video [10] (28m32s).
[ 8] https://fosdem.org/2025/schedule/event/fosdem-2025-4072-rewriting-pyc-files-for-fun-and-reproducibility//
[ 9] https://fosdem.org/2025/events/attachments/fosdem-2025-4072-rewriting-pyc-files-for-fun-and-reproducibility/slides/238866/rewriting_V75oWEe.pdf
[10] https://fosdem.org/2025/schedule/event/fosdem-2025-4072-rewriting-pyc-files-for-fun-and-reproducibility/
In the "Nix and NixOS" track, Julien Malka presented on the Saturday
asking "How reproducible is NixOS" [11]: "We know that the NixOS ISO
image is very close to be perfectly reproducible thanks to
reproducible.nixos.org [12], but there doesn't exist any monitoring
of Nixpkgs as a whole. In this talk I'll present the findings of a
project that evaluated the reproducibility of Nixpkgs as a whole by
mass rebuilding packages from revisions between 2017 and 2023 and
comparing the results with the NixOS cache." Unfortunately, no video
of the talk is available, but there is a blog [13] and article [14]
on the results.
[11] https://fosdem.org/2025/schedule/event/fosdem-2025-4430-how-reproducible-is-nixos-/
[12] https://reproducible.nixos.org/
[13] https://luj.fr/blog/is-nixos-truly-reproducible.html
[14] https://hal.science/hal-04430009
Lastly, Simon Tournier presented in the "Open Research" track on the
confluence of GNU Guix [15] and Software Heritage [16]: "Source Code
Archiving to the Rescue of Reproducible Deployment" [17]. Simon's
talk "describes design and implementation we came up and reports on
the archival coverage for package source code with data collected
over five years. It opens to some remaining challenges toward a
better open and reproducible research." The slides for the talk [18]
are available, as is the full video [19] (23m17s).
[15] https://guix.gnu.org/
[16] https://www.softwareheritage.org/
[17] https://fosdem.org/2025/schedule/event/fosdem-2025-5897-guix-software-heritage-source-code-archiving-to-the-rescue-of-reproducible-deployment/
[18] https://fosdem.org/2025/events/attachments/fosdem-2025-5897-guix-software-heritage-source-code-archiving-to-the-rescue-of-reproducible-deployment/slides/237921/FOSDEM25-_lctdtLk.pdf
[19] https://fosdem.org/2025/schedule/event/fosdem-2025-5897-guix-software-heritage-source-code-archiving-to-the-rescue-of-reproducible-deployment/
§
Reproducible Builds at PyCascades 2025
--------------------------------------
Vagrant Cascadian presented at this year's PyCascades [20]
conference which was held on February 8th and 9th February in
Portland, OR, USA. PyCascades is a regional instance of PyCon [21]
held in the Pacific Northwest. Vagrant's talk, entitled
"Re-Py-Ducible Builds" [22] caught the audience's attention with the
following abstract:
> Crank your Python best practices up to 11 with Reproducible
> Builds! This talk will explore Reproducible Builds by
> highlighting issues identified in Python projects, from the simple
> to the seemingly inscrutable. Reproducible Builds is basically the
> crazy idea that when you build something, and you build it again,
> you get the exact same thing... or even more important, if someone
> else builds it, they get the exact same thing too.
More info is available on the talk's page [22].
[20] https://2025.pycascades.com/
[21] https://pycon.org/
[22] https://2025.pycascades.com/program/talks/re-py-ducible-builds/
§
"Does Functional Package Management Enable Reproducible Builds at Scale?"
-------------------------------------------------------------------------
On our mailing list [24] last month, Julien Malka, Stefano
Zacchiroli and Théo Zimmermann of Télécom Paris’ in-house research
laboratory, the Information Processing and Communications Laboratory
[25] (LTCI) announced that they had published an article asking the
question, "Does Functional Package Management Enable Reproducible
Builds at Scale?" [26] (PDF [27]).
This month, however, Ludovic Courtès followed up to the original
announcement on our mailing list [28] mentioning, amongst other
things, the Guix Data Service [29] and how that it shows the
reproducibility of GNU Guix [30] over time, as described in a GNU
Guix blog [31] back in March 2024.
[24] https://lists.reproducible-builds.org/listinfo/rb-general/
[25] https://www.telecom-paris.fr/en/research/labs/information-processing-ltci
[26] https://hal.science/hal-04913007
[27] https://hal.science/hal-04913007v1/file/2025-MSR-reproducibility.pdf
[28] https://lists.reproducible-builds.org/pipermail/rb-general/2025-January/003653.html
[29] https://data.guix.gnu.org/
[30] https://guix.gnu.org/
[31] https://guix.gnu.org/en/blog/2024/adventures-on-the-quest-for-long-term-reproducible-deployment/
§
reproduce.debian.net updates
----------------------------
The last few months have seen the introduction of
reproduce.debian.net [33]. Announced first at the recent Debian
MiniDebConf in Toulouse [34], reproduce.debian.net is an instance of
"rebuilderd" [35] operated by the Reproducible Builds project.
Powering this work rebuilderd, our server which monitors the
official package repositories of Linux distributions and attempt to
reproduce the observed results there. This month, however, Holger
Levsen:
* Split packages that are not specific to any architecture away from
amd64.reproducible.debian.net service into a new
all.reproducible.debian.net [36] page.
* Increased the number of riscv64 nodes to a total of 4, and added a
new amd64 node added thanks to our (now 10-year sponsor), IONOS
[37].
* Discovered an issue in the Debian build service [38] where some
new 'incoming' build-dependencies do not end up historically
archived [39].
* Uploaded the devscripts [40] package, incorporating changes from
Jochen Sprickerhof to the debrebuild script — specifically to fix
the handling the Rules-Requires-Root header in Debian source
packages.
* Uploaded a number of Rust dependencies of rebuilderd (rust-
libbz2-rs-sys, rust-actix-web, rust-actix-server, rust-actix-http,
rust-actix-server, rust-actix-http, rust-actix-web-codegen and
rust- time-tz) after they were prepared by kpcyrd:
[32] https://reproduce.debian.net/
[33] https://reproduce.debian.net
[34] https://toulouse2024.mini.debconf.org/
[35] https://github.com/kpcyrd/rebuilderd
[36] https://all.reproduce.debian.net/
[37] https://ionos.com
[38] https://buildd.debian.org/
[39] https://bugs.debian.org/1096129
[40] https://salsa.debian.org/debian/devscripts
Jochen Sprickerhof also updated the sbuild package to:
* Obey requests from the user/developer for a different
temporary directory.
* Use the root/superuser for some values of Rules-Requires-Root.
* Don't pass --root-owner-group to old versions of dpkg [41].
… and additionally requested that many Debian packages are rebuilt
by the build servers [42] in order to work around bugs found on
reproduce.debian.net [43]. [44][45][46]
[41] https://wiki.debian.org/Teams/Dpkg
[42] https://wiki.debian.org/binNMU
[43] https://reproduce.debian.net/
[44] https://bugs.debian.org/1096112
[45] https://bugs.debian.org/1092482
[46] https://bugs.debian.org/1093902
Lastly, kpcyrd has also worked towards getting rebuilderd packaged
in NixOS [47], and Jelle van der Waa picked up the existing pull
request for Fedora support within in rebuilderd [48] and made it
work with the existing Koji rebuilderd script [49]. The server is
being packaged for Fedora in an unofficial 'copr' repository [50]
and in the official repositories after all the dependencies are
packaged.
[47] https://github.com/NixOS/nixpkgs/pull/343334
[48] https://github.com/kpcyrd/rebuilderd/pull/141
[49] https://github.com/keszybz/fedora-repro-build
[50] https://copr.fedorainfracloud.org/coprs/jelly/rebuilderd/packages/
§
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:
* Andrea Manzini:
* rust-i8n [51] (random HashMap order)
* starship/shadow [52]
[51] https://github.com/longbridge/rust-i18n/pull/104
[52] https://github.com/starship/starship/issues/6599
* Andreas Stieger:
* tucnak [53]
[53] https://build.opensuse.org/request/show/1247238
* Bernhard M. Wiedemann:
* aioquic [54]
* built [55]
* difftastic [56]
* ghostscript [57]
* gputils/sdcc [58]
* hdf5 [59]
* html5ever [60] (fixed upstream [61])
* khal [62]
* lkl [63]
* neovim [64]
* nlopt [65]
* nushell [66]
* palo [67]
* python-numpy [68]
* schismtracker [69]
* sequoia [70] (2 [71])
* tvm [72]
* uhd [73]
* wsjtx [74]
* xmlgraphics-fop [75]
* zig [76]
[54] https://github.com/aiortc/aioquic/issues/557
[55] https://github.com/lukaslueg/built/issues/80
[56] https://github.com/Wilfred/difftastic/pull/813
[57] https://build.opensuse.org/request/show/1243016
[58] https://sourceforge.net/p/gputils/bugs/328/
[59] https://build.opensuse.org/request/show/1242841
[60] https://github.com/servo/html5ever/issues/573
[61] https://github.com/servo/string-cache/pull/290
[62] https://github.com/pimutils/khal/pull/1390
[63] https://build.opensuse.org/request/show/1247659
[64] https://github.com/neovim/neovim/issues/32429
[65] https://build.opensuse.org/request/show/1244447
[66] https://build.opensuse.org/request/show/1247347
[67] https://build.opensuse.org/request/show/1247180
[68] https://build.opensuse.org/request/show/1245435
[69] https://src.opensuse.org/jengelh/schismtracker/pulls/1
[70] https://gitlab.com/sequoia-pgp/sequoia-sq/-/issues/535
[71] https://gitlab.com/sequoia-pgp/sequoia-sq/-/merge_requests/554
[72] https://bugzilla.opensuse.org/show_bug.cgi?id=1237607
[73] https://build.opensuse.org/request/show/1243555
[74] https://sourceforge.net/p/wsjt/wsjtx/merge-requests/20/
[75] https://bugzilla.opensuse.org/show_bug.cgi?id=1237094
[76] https://github.com/ziglang/zig/issues/22839
* Chris Lamb:
* #1095209 [77] filed against python-assertpy [78].
* #1096188 [79] filed against terminaltables3 [80].
* #1098249 [81] filed against acme.sh [82].
* #1098251 [83] filed against node-svgdotjs-svg.js [84].
* #1098253 [85] filed against onevpl-intel-gpu [86].
* #1098350 [87] filed against rocdbgapi [88].
* #1098895 [89] filed against siege [90].
* #1098945 [91] filed against pkg-rocm-tools [92].
[77] https://bugs.debian.org/1095209
[78] https://tracker.debian.org/pkg/python-assertpy
[79] https://bugs.debian.org/1096188
[80] https://tracker.debian.org/pkg/terminaltables3
[81] https://bugs.debian.org/1098249
[82] https://tracker.debian.org/pkg/acme.sh
[83] https://bugs.debian.org/1098251
[84] https://tracker.debian.org/pkg/node-svgdotjs-svg.js
[85] https://bugs.debian.org/1098253
[86] https://tracker.debian.org/pkg/onevpl-intel-gpu
[87] https://bugs.debian.org/1098350
[88] https://tracker.debian.org/pkg/rocdbgapi
[89] https://bugs.debian.org/1098895
[90] https://tracker.debian.org/pkg/siege
[91] https://bugs.debian.org/1098945
[92] https://tracker.debian.org/pkg/pkg-rocm-tools
* Christian Goll:
* warewulf4 [93] (embeds CPU core count)
[93] https://build.opensuse.org/request/show/1248768
* Jay Adddison:
* linux-docs [94]
[94] https://lore.kernel.org/linux-doc/20250226203516.334067-2-jvanderw@redhat.com/
* Jochen Sprickerhof:
* #1098867 [95] filed against spdlog [96].
[95] https://bugs.debian.org/1098867
[96] https://tracker.debian.org/pkg/spdlog
* kpcyrd:
* perl [97] (hostname)
* pam [98] (timestamp)
[97] https://gitlab.archlinux.org/archlinux/packaging/packages/perl/-/commit/b2ac4e7b8d71463f8e2944693b5f27640d88b444
[98] https://gitlab.archlinux.org/archlinux/packaging/packages/pam/-/commit/bc4528c28672fe75a1378e4834bf58ae7889caee
* Leonidas Spyropoulos:
* curl [99]
[99] https://gitlab.archlinux.org/archlinux/packaging/packages/curl/-/commit/cb7452f4c8dfb3a88b9732d45c359a7a118ec907
* Robin Candau (Antiz):
* highlight [101] (timestamp)
* arch-wiki-lite [102] (timestamp)
* f3d [103] (timestamp)
* jacktrip [104] (timestamp)
* prometheus [105] (timestamp)
[101] https://gitlab.com/saalen/highlight/-/merge_requests/151
[102] https://gitlab.archlinux.org/grawlinson/arch-wiki-lite/-/merge_requests/2
[103] https://github.com/f3d-app/f3d/pull/1982
[104] https://github.com/jacktrip/jacktrip/pull/1394
[105] https://github.com/prometheus/prometheus/pull/16035
* Wolfgang Frisch:
* bcc [106] (instruct Lua to be deterministic)
* crash [107] (Makefile race)
[106] https://build.opensuse.org/request/show/1245248
[107] https://github.com/crash-utility/crash/pull/200
* Hongxu Jia:
* go [108] (clear GOROOT for func ldShared when -trimpath is used)
[108] https://go-review.googlesource.com/c/go/+/653895
§
Distribution work
-----------------
There as been the usual work in various distributions this month...
In Debian, 17 reviews of Debian packages were added, 6 were updated
and 8 were removed this month adding to our knowledge about
identified issues [109].
[109] https://tests.reproducible-builds.org/debian/index_issues.html
Fedora [110] developers Davide Cavalca and Zbigniew
Jędrzejewski-Szmek gave a talk on "Reproducible Builds in Fedora"
[111] (PDF), touching on SRPM [112]-specific issues as well as the
current status and future plans.
[110] https://fedoraproject.org/
[111] https://cfp.fedoraproject.org/media/flock-2024/submissions/SKWEXP/resources/Reproducible_builds_in_Fedora_Flock_2024_Iiyoq3s.pdf
[112] https://en.wikipedia.org/wiki/RPM_Package_Manager#SRPM
Thanks to an investment from the Sovereign Tech Agency [113], the
FreeBSD [114] project's work on unprivileged and reproducible builds
continued this month. Notable fixes include:
* pkg [115] (hash ordering)
* makefs [116] (source filesystem inode number leakage)
* FreeBSD base system packages [117] (timestamp)
[113] https://freebsdfoundation.org/blog/zero-trust-builds-for-freebsd/
[114] https://www.freebsd.org/
[115] https://github.com/freebsd/pkg/commit/ea82e1d6df919714a2e3472c7561f53a2dde69d1
[116] https://cgit.freebsd.org/src/commit/usr.sbin/makefs/cd9660?id=518cdd344ec51584478f39b9a9cac77fc0766ce1
[117] https://cgit.freebsd.org/src/commit/?id=8a3537aaf7c19f7331fcc160ab42e36fc79e408a
The Yocto Project [118] has been struggling to upgrade to the latest
Go [119] and Rust [120] releases due to reproducibility problems in
the newer versions. Hongxu Jia tracked down the issue with Go which
meant that the project could upgrade from the 1.22 series to 1.24,
with the fix being submitted upstream for review (see above). For
Rust, however, the project was significantly behind, but has made
recent progress after finally identifying the blocking
reproducibility issues. At time of writing, the project is at Rust
version 1.82, with patches under review for 1.83 and 1.84 and fixes
being discussed with the Rust developers. The project hopes to
improve the tests for reproducibility in the Rust project itself in
order to try and avoid future regressions.
Yocto continues to maintain its ability to binary reproduce all of
the recipes in OpenEmbedded-Core [121], regardless of the build host
distribution or the current build path.
[118] https://yoctoproject.org/
[119] https://go.dev/
[120] https://www.rust-lang.org/
[121] https://www.yoctoproject.org/reproducible-build-results/
Finally, Douglas DeMaio published an article on the openSUSE blog
[122] on announcing that the ["Reproducible-openSUSE (RBOS) Project
Hits [a Significant] Milestone"](https://news.opensuse.org/2025/02/18/rbos-
project-hits-milestone/). In particular:
> The Reproducible-openSUSE (RBOS) [123] project, which is a
> proof-of- concept fork of openSUSE, has reached a significant
> milestone after demonstrating a usable Linux distribution can be
> built with 100% bit- identical packages.
This news was also announced on our mailing list [124] by Bernhard
M. Wiedemann, who also published another report [125] for openSUSE
as well.
[122] https://news.opensuse.org/
[123] https://en.opensuse.org/openSUSE:Reproducible_openSUSE
[124] https://lists.reproducible-builds.org/pipermail/rb-general/2025-February/003661.html
[125] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/3VT2UY7YUIM3AP3XIQAYO32VT7KZ7FBK/
§
diffoscope & strip-nondeterminism
---------------------------------
diffoscope [127] is our in-depth and content-aware diff utility that
can locate and diagnose reproducibility issues. This month, Chris
Lamb made the following changes, including preparing and uploading
versions 288 and 289 to Debian:
* Add asar to "DIFFOSCOPE_FAIL_TESTS_ON_MISSING_TOOLS" in order to
address Debian bug #1095057 [128]) [129]
* Catch a CalledProcessError when calling html2text. [130]
* Update the minimal Black [131] version. [132]
[127] https://diffoscope.org
[128] https://bugs.debian.org/1095057
[129] https://salsa.debian.org/reproducible-builds/diffoscope/commit/79ff322e
[130] https://salsa.debian.org/reproducible-builds/diffoscope/commit/e470ee25
[131] https://black.readthedocs.io/en/stable/
[132] https://salsa.debian.org/reproducible-builds/diffoscope/commit/c5aa1ff5
Additionally, Vagrant Cascadian updated diffoscope in GNU Guix [133]
to version 287 [134][135] and 288 [136][137] as well as submitted a
patch to update to 289 [138]. Vagrant also fixed an issue that was
breaking reprotest on Guix [139][140].
[133] https://guix.gnu.org/
[134] https://debbugs.gnu.org/76080
[135] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=27c2b2f1a6f48f238030893b6d0ebc9c2bc68b12
[136] https://debbugs.gnu.org/76122
[137] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=d304311a3949795659bf08d9409ddf86481dcc36
[138] https://debbugs.gnu.org/76599
[139] https://debbugs.gnu.org/76602
[140] https://git.savannah.gnu.org/cgit/guix.git/commit/?id=2558392803663f4381fa9c09a53d329b719152bd
strip-nondeterminism [141] is our sister tool to remove specific
non- deterministic results from a completed build. This month
version 1.14.1-2 was uploaded to Debian unstable [142] by Holger
Levsen.
[141] https://salsa.debian.org/reproducible-builds/strip-nondeterminism
[142] https://tracker.debian.org/news/1614424/accepted-strip-nondeterminism-1141-2-source-into-unstable/
§
Website updates
---------------
There were a large number of improvements made to our website this
month, including:
* Bernhard M. Wiedemann fixed an issue on the "Commandments of
reproducible builds" [143] fixing a link to the readdir [144]
component of Bernhard's own Unreproducible Package [145]. [146]
[143] https://reproducible-builds.org/docs/commandments/
[144] https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/readdir
[145] https://github.com/bmwiedemann/theunreproduciblepackage
[146] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/bf9274a0
* Holger Levsen clarified the name of a link to our old Wiki pages on
the "History" [147] page [148] and added a number of new links to the
"Talks & Resources" [149][150][151].
[147] https://reproducible-builds.org/docs/history/
[148] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/0fb66ed9
[149] https://reproducible-builds.org/resources/
[150] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/33b9594d
[151] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/f7e5a9c9
* James Addison update the website's own README [152] file to
document a couple of additional dependencies [153][154], as well
as did more work on a future "Getting Started" guide page [155][156].
[152] https://salsa.debian.org/reproducible-builds/reproducible-website#readme
[153] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/308373c2
[154] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/ceee7b28
[155] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/61d6ab62
[156] https://salsa.debian.org/reproducible-builds/reproducible-website/commit/23f28585
§
Reproducibility testing framework
---------------------------------
The Reproducible Builds project operates a comprehensive testing
framework running primarily at tests.reproducible-builds.org [157]
in order to check packages and other artifacts for reproducibility.
In January, a number of changes were made by Holger Levsen,
including:
* reproduce.debian.net [158]-related:
* Add a helper script to manually schedule
packages. [159][160][161][162][163]
* Fix a link in the website footer. [164]
* Strip the "💠🍥♻" emojis from package names on the manual rebuilder
in order to ease copy-and-paste. [165]
* On the various statistics pages, provide the number of affected
source packages [166][167] as well as provide various
totals [168][169].
* Fix graph labels for the various architectures [170][171] and
make them clickable too [172][173][174].
* Break the displayed HTML in blocks of 256 packages in order to
address rendering issues. [175][176]
* Add monitoring jobs for riscv64 archicture nodes and integrate
them elsewhere in our infrastructure. [177][178]
* Add riscv64 architecture nodes. [179][180][181][182][183]
* Update much of the documentation. [184][185][186]
* Make a number of improvements to the layout and
style. [187][188][189][190][191][192][193]
* Remove direct links to JSON and database backups. [194]
* Drop a Blues Brothers [195] reference from frontpage. [196]
[157] https://tests.reproducible-builds.org
[158] https://reproduce.debian.net
[159] https://salsa.debian.org/qa/jenkins.debian.net/commit/2a0687142
[160] https://salsa.debian.org/qa/jenkins.debian.net/commit/cb69118bc
[161] https://salsa.debian.org/qa/jenkins.debian.net/commit/30f376fbf
[162] https://salsa.debian.org/qa/jenkins.debian.net/commit/fc11778d8
[163] https://salsa.debian.org/qa/jenkins.debian.net/commit/871d7c509
[164] https://salsa.debian.org/qa/jenkins.debian.net/commit/1e4731b40
[165] https://salsa.debian.org/qa/jenkins.debian.net/commit/bdaeaf460
[166] https://salsa.debian.org/qa/jenkins.debian.net/commit/d6538620d
[167] https://salsa.debian.org/qa/jenkins.debian.net/commit/daabe3cf6
[168] https://salsa.debian.org/qa/jenkins.debian.net/commit/f6f2be8e0
[169] https://salsa.debian.org/qa/jenkins.debian.net/commit/4a622a4f5
[170] https://salsa.debian.org/qa/jenkins.debian.net/commit/be76b69dd
[171] https://salsa.debian.org/qa/jenkins.debian.net/commit/cb3d39cf0
[172] https://salsa.debian.org/qa/jenkins.debian.net/commit/0f141d2e1
[173] https://salsa.debian.org/qa/jenkins.debian.net/commit/8a610a2eb
[174] https://salsa.debian.org/qa/jenkins.debian.net/commit/bed9b4e31
[175] https://salsa.debian.orgqa/jenkins.debian.net/commit/0fa4fc68f
[176] https://salsa.debian.org/qa/jenkins.debian.net/commit/fe9d6a854
[177] https://salsa.debian.org/qa/jenkins.debian.net/commit/675f6a11b
[178] https://salsa.debian.org/qa/jenkins.debian.net/commit/a486b7447
[179] https://salsa.debian.org/qa/jenkins.debian.net/commit/5fd63d56a
[180] https://salsa.debian.org/qa/jenkins.debian.net/commit/f5c3650eb
[181] https://salsa.debian.org/qa/jenkins.debian.net/commit/a7d52658e
[182] https://salsa.debian.org/qa/jenkins.debian.net/commit/e703fe971
[183] https://salsa.debian.org/qa/jenkins.debian.net/commit/156a0c6c8
[184] https://salsa.debian.org/qa/jenkins.debian.net/commit/557979a6e
[185] https://salsa.debian.org/qa/jenkins.debian.net/commit/ec9b33414
[186] https://salsa.debian.org/qa/jenkins.debian.net/commit/4f0f31b36
[187] https://salsa.debian.org/qa/jenkins.debian.net/commit/a52fa4e2c
[188] https://salsa.debian.org/qa/jenkins.debian.net/commit/c6b096ef7
[189] https://salsa.debian.org/qa/jenkins.debian.net/commit/4419a6619
[190] https://salsa.debian.org/qa/jenkins.debian.net/commit/39ee08ebe
[191] https://salsa.debian.org/qa/jenkins.debian.net/commit/f2826eb71
[192] https://salsa.debian.org/qa/jenkins.debian.net/commit/908c5b967
[193] https://salsa.debian.org/qa/jenkins.debian.net/commit/966a2860a
[194] https://salsa.debian.org/qa/jenkins.debian.net/commit/5bf4c02f5
[195] https://en.wikipedia.org/wiki/The_Blues_Brothers
[196] https://salsa.debian.org/qa/jenkins.debian.net/commit/e1a06c522
* Debian [197]-related:
* Deal with /boot/vmlinuz* being called vmlinux* on the riscv64
architecture. [198]
* Add a new ionos17 node. [199][200][201][202][203]
* Install debian-repro-status on all Debian trixie and unstable
jobs. [204]
[197] https://debian.org/
[198] https://salsa.debian.org/qa/jenkins.debian.net/commit/ebe31528a
[199] https://salsa.debian.org/qa/jenkins.debian.net/commit/05ce176a2
[200] https://salsa.debian.org/qa/jenkins.debian.net/commit/f63f2bcc1
[201] https://salsa.debian.org/qa/jenkins.debian.net/commit/4e223a51c
[202] https://salsa.debian.org/qa/jenkins.debian.net/commit/4d405000b
[203] https://salsa.debian.org/qa/jenkins.debian.net/commit/f455f7963
[204] https://salsa.debian.org/qa/jenkins.debian.net/commit/8d3f6120f
* FreeBSD [205]-related:
* Switch to run latest branch of FreeBSD. [206]
[205] https://www.freebsd.org/
[206] https://salsa.debian.org/qa/jenkins.debian.net/commit/384e1ea79
* Misc:
* Fix /etc/cron.d and /etc/logrotate.d permissions for Jenkins
nodes. [207]
* Add support for riscv64 architecture nodes. [208][209]
* Grant Jochen Sprickerhof access to the o4 node. [210]
* Disable the janitor-setup-worker. [211][212]
[207] https://salsa.debian.org/qa/jenkins.debian.net/commit/b4c4c10f4
[208] https://salsa.debian.org/qa/jenkins.debian.net/commit/4779831fc
[209] https://salsa.debian.org/qa/jenkins.debian.net/commit/7ec069881
[210] https://salsa.debian.org/qa/jenkins.debian.net/commit/ca539b3cf
[211] https://salsa.debian.org/qa/jenkins.debian.net/commit/4d6156e3d
[212] https://salsa.debian.org/qa/jenkins.debian.net/commit/b6a514ea0
In addition:
* kpcyrd fixed the /all/api/ API endpoints on reproduce.debian.net
[213] by altering the nginx [214] configuration. [215]
[213] https://reproduce.debian.net
[214] https://nginx.org/
[215] https://salsa.debian.org/qa/jenkins.debian.net/commit/e62b098f4
* James Addison updated reproduce.debian.net [216] to display the so-
called 'bad' reasons hyperlink inline [217] and merged the
"Categorized issues" links into the "Reproduced builds" column [218].
[216] https://reproduce.debian.net
[217] https://salsa.debian.org/qa/jenkins.debian.net/commit/e5a9e8749
[218] https://salsa.debian.org/qa/jenkins.debian.net/commit/f4d2cc828
* Jochen Sprickerhof also made some reproduce.debian.net [219]
-related changes, adding support for detecting a bug in the
mmdebstrap [220] package [221] as well as updating some
documentation [222].
[219] https://reproduce.debian.net
[220] http://bugs.debian.org/1094165
[221] https://salsa.debian.org/qa/jenkins.debian.net/commit/53d49a31a
[222] https://salsa.debian.org/qa/jenkins.debian.net/commit/eda9b4f37
* Roland Clobus continued their work on reproducible 'live' images for
Debian, making changes related to new clustering of jobs in openQA
[223]. [224]
[223] https://open.qa/
[224] https://salsa.debian.org/qa/jenkins.debian.net/commit/aafcf255e
And finally, both Holger Levsen [225][226][227] and Vagrant Cascadian
performed significant node maintenance. [228][229][230][231][232]
[225] https://salsa.debian.org/qa/jenkins.debian.net/commit/042c2ec6c
[226] https://salsa.debian.org/qa/jenkins.debian.net/commit/2a7d73ef9
[227] https://salsa.debian.org/qa/jenkins.debian.net/commit/3346f409e
[228] https://salsa.debian.org/qa/jenkins.debian.net/commit/5be92d0ff
[229] https://salsa.debian.org/qa/jenkins.debian.net/commit/26b34a93e
[230] https://salsa.debian.org/qa/jenkins.debian.net/commit/e74e53f71
[231] https://salsa.debian.org/qa/jenkins.debian.net/commit/b2c55e610
[232] https://salsa.debian.org/qa/jenkins.debian.net/commit/58ae0663f
§
If you are interested in contributing to the Reproducible Builds
project, please visit the "Contribute" [233] page on our website.
However, you can get in touch with us via:
* IRC: #reproducible-builds on irc.oftc.net.
* Mailing list: rb-general at lists.reproducible-builds.org [235]
* Twitter/X: @ReproBuilds [236]
[233] https://reproducible-builds.org/contribute/
[235] https://lists.reproducible-builds.org/listinfo/rb-general
[236] https://twitter.com/ReproBuilds
--
o
⬋ ⬊
o o reproducible-builds.org 💠
⬊ ⬋
o
More information about the rb-general
mailing list