[Git][reproducible-builds/reproducible-website][master] history: expand on 2016, 2018, 2019, 2020, 2023, 2024, 2025

kpcyrd (@kpcyrd) gitlab at salsa.debian.org
Sun Aug 17 00:27:35 UTC 2025



kpcyrd pushed to branch master at Reproducible Builds / reproducible-website


Commits:
26771307 by kpcyrd at 2025-08-17T02:12:53+02:00
history: expand on 2016, 2018, 2019, 2020, 2023, 2024, 2025

- - - - -


1 changed file:

- _docs/history.md


Changes:

=====================================
_docs/history.md
=====================================
@@ -283,9 +283,13 @@ mailinglists, new irc channel, an even wider community has started to
 grow,
 [website](https://reproducible-builds.org/events/athens2015/).
 
-## 2016 and 2017 and beyond
+## 2016
 
-Are largely missing here, we should fix this, rather sooner than later.
+In early 2016, Arch Linux started recording the build environment of packages
+in embedded `.BUILDINFO` files that were introduced in [pacman
+5.0.0](https://gitlab.archlinux.org/pacman/pacman/-/blob/v5.0.0/NEWS?ref_type=tags#L50).
+
+## 2017
 
 In January 2017 we learned, that John Gilmore [wrote an interesting
 mail about how Cygnus.com worked on reproducible builds in the early
@@ -302,10 +306,78 @@ On October 16th 2017 intrigeri reported successes in reproducing [Tails](https:/
 and shared blueprints with goals and scopes plus verification
 instructions for the first time in [a post to our general mailinglist](https://lists.reproducible-builds.org/pipermail/rb-general/2017-October/000656.html).
 
+## 2018
+
+In May 2018, official reproducible-builds support was [announced for
+pacman](https://web.archive.org/web/20180617120321/http://allanmcrae.com/2018/05/pacman-5-1-dont-use-the-force-luke/)
+in the 5.1.0 release.
+
+## 2019
+
+In November 2019 the [first version of
+archlinux-repro](https://github.com/archlinux/archlinux-repro/releases/tag/20191113)
+has been released, allowing independently reproducing official Arch Linux
+binary packages from source code.
+
+Initial development of [rebuilderd](https://github.com/kpcyrd/rebuilderd) has
+started during [Marrakesh
+2019](https://reproducible-builds.org/events/Marrakesh2019/) in December.
+
+## 2020
+
+In April 2020, Arch Linux announced their official [reproducible.archlinux.org rebuilderd
+instance](https://reproducible-builds.org/reports/2020-04/) and [reached
+out](https://lists.reproducible-builds.org/pipermail/rb-general/2020-April/001905.html)
+for community-ran instances to double-check their reported results.
+
+A workshop about [reproducing official Arch Linux packages from source
+code](https://lists.reproducible-builds.org/pipermail/rb-general/2020-April/001892.html)
+has been held at Chaos Computer Club's [DiVOC](https://di.c3voc.de/) during
+Spring.
+
+## 2023
+
+In May 2023, problems with Linux' build-time generated module signing keys were
+[raised on the reproducible-builds mailing
+list](https://lists.reproducible-builds.org/pipermail/rb-general/2023-May/002991.html).
+
+In July 2023 kpcyrd [announced
+repro-env](https://lists.reproducible-builds.org/pipermail/rb-general/2023-July/003026.html)
+for documented Linux build environments (with support for Arch Linux and
+Debian), intended for use by vendors that aren't Linux distributions.
+
+In August 2023 a [regression was fixed in
+pacman](https://gitlab.archlinux.org/pacman/pacman/-/commit/843bf21e794c79c5b3bcf8a57e45ef9c62312fee),
+making debug symbol detachment deterministic. This problem was present since
+[February
+2022](https://lists.reproducible-builds.org/pipermail/rb-general/2024-March/003291.html),
+but many packages could still be reproduced after multiple retries.
+
 ## 2024
 
-In 2024, Bernhard M. Wiedemann worked several months full-time on [R-B-OS](https://news.opensuse.org/2025/02/18/rbos-project-hits-milestone/) - a 100% bit-reproducible fork of openSUSE.
+In January 2024 [Arch Linux
+backported](https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/64b011a89951a796de4282ee38ab0c05424ec159)
+the reproducible-builds fix for debuginfo processing, that was later released
+in `pacman 6.0.2-9`.
+
+In February 2024, Bernhard M. Wiedemann worked several months full-time on [R-B-OS](https://news.opensuse.org/2025/02/18/rbos-project-hits-milestone/), a 100% bit-reproducible fork of openSUSE.
+
+In March 2024, [Arch Linux reported a 100% reproducible container
+userland](https://lists.reproducible-builds.org/pipermail/rb-general/2024-March/003301.html).
+
+In September 2024, module signing in the Linux kernel was discussed again on
+the reproducible-builds mailing list, also [suggesting a hashset based
+approach](https://lists.reproducible-builds.org/pipermail/rb-general/2024-September/003530.html)
+for module authentication, to avoid the need for build secrets.
+
+In November 2024, [reproduce.debian.net was
+announced](https://reproducible-builds.org/reports/2024-11/).
+
+## 2025
 
+In August 2025, the [Debian 13 release
+notes](https://www.debian.org/News/2025/20250809) explicitly mention
+reproducible builds, reproduce.debian.net and debian-repro-status.
 
 ## ToDo
 



View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/2677130753780d3ef6260eeb6111d38aca445d48

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/2677130753780d3ef6260eeb6111d38aca445d48
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20250817/6296c337/attachment.htm>


More information about the rb-commits mailing list