[Git][reproducible-builds/reproducible-website][master] r-b summit 2026: make all those reports visible
Holger Levsen (@holger)
gitlab at salsa.debian.org
Fri Sep 25 12:05:31 UTC 2026
Holger Levsen pushed to branch master at Reproducible Builds / reproducible-website
Commits:
54ea9dae by Holger Levsen at 2026-09-25T14:05:26+02:00
r-b summit 2026: make all those reports visible
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
16 changed files:
- _events/gothenburg2026/agenda/d1-atproto.md
- _events/gothenburg2026/agenda/d1-badbuild.md
- _events/gothenburg2026/agenda/d1-imagebuilds.md
- _events/gothenburg2026/agenda/d1-longtail.md
- _events/gothenburg2026/agenda/d2-buildinfrastructure.md
- _events/gothenburg2026/agenda/d2-cross-distro.md
- _events/gothenburg2026/agenda/d2-nonreproducible.md
- _events/gothenburg2026/agenda/d2-rb-enforcement.md
- _events/gothenburg2026/agenda/d2-rb-security.md
- _events/gothenburg2026/agenda/d2-rb-social.md
- _events/gothenburg2026/agenda/d2-transparency-logging.md
- _events/gothenburg2026/agenda/d3-rb-ai.md
- _events/gothenburg2026/agenda/d3-rb-enforcement2.md
- _events/gothenburg2026/agenda/d3-rebuilderd.md
- _events/gothenburg2026/agenda/d3-sourcedateepoch.md
- _events/gothenburg2026/agenda/d3-trusting-trust.md
Changes:
=====================================
_events/gothenburg2026/agenda/d1-atproto.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 1 - Distributing metadata
+order: 10
+permalink: /events/gothenburg2026/agenda/d1-atproto.md
+---
- Headline: **Distributing metadata**.
- (transparency logs might be a topic related to this.)
- (Atproto: might be a vessel of this. And was the card on the board that got stickers for interest.)
=====================================
_events/gothenburg2026/agenda/d1-badbuild.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 1 - Bad builds
+order: 10
+permalink: /events/gothenburg2026/agenda/d1-badbuild.md
+---
Greg's work: uses stabilizer (these stabilizers guarantee removing non-malicious differences)
Signal APK: some part was ignored.
=====================================
_events/gothenburg2026/agenda/d1-imagebuilds.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 1 - Image builds
+order: 10
+permalink: /events/gothenburg2026/agenda/d1-imagebuilds.md
+---
## What was necessary for making Arch images reproducible:
- The goal is to make a rootfs that's reproducible
=====================================
_events/gothenburg2026/agenda/d1-longtail.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 1 - the long tail
+order: 10
+permalink: /events/gothenburg2026/agenda/d1-longtail.md
+---
## Problem
The Pareto principle applies to fixing r-b issues. 80% of the benefit need 20% of the work and what non-determinism remains becomes increasingly harder to make deterministic.
=====================================
_events/gothenburg2026/agenda/d2-buildinfrastructure.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - Build infrastructure
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-buildinfrastructure.md
+---
Improve serving and format of buildinfo files
- can we include hashes of build dependencies in buildinfo files?
=====================================
_events/gothenburg2026/agenda/d2-cross-distro.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - Cross-distro reproducibility
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-cross-distro.md
+---
## Cross-distro reproducibility
Things needed to get started as a new distribution:
=====================================
_events/gothenburg2026/agenda/d2-nonreproducible.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - the remaining 1%
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-nonreproducible.md
+---
## The remaining 1%
Which packages are not reproducible, and why?
=====================================
_events/gothenburg2026/agenda/d2-rb-enforcement.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - Enforcement
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-rb-enforcement.md
+---
## Enforcement
- At distro level, the gatekeeping is at entering the archive
=====================================
_events/gothenburg2026/agenda/d2-rb-security.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - Security and Reproducible Builds
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-rb-security.md
+---
# Security and RB
- Should we distinguish between using reproducibility to detect non-malicious vulnerabilities vs. malicious activity?
=====================================
_events/gothenburg2026/agenda/d2-rb-social.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - Social aspects of Reproducible Builds
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-rb-social.md
+---
## social
Android world: Users trust the developer more.
=====================================
_events/gothenburg2026/agenda/d2-transparency-logging.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 2 - Transparency logging
+order: 10
+permalink: /events/gothenburg2026/agenda/d2-transparency-logging.md
+---
## transparency-logging
why to use transparency logs for rb:
=====================================
_events/gothenburg2026/agenda/d3-rb-ai.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 3 - RB and AI
+order: 10
+permalink: /events/gothenburg2026/agenda/d3-rb-ai.md
+---
## Observed Benefits
* Extracts builds structures when vague
* (Build steps, tool versions, metadata)
=====================================
_events/gothenburg2026/agenda/d3-rb-enforcement2.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 3 - Enforcement, part 2
+order: 10
+permalink: /events/gothenburg2026/agenda/d3-rb-enforcement2.md
+---
Follow-up of a [session on day 2](d2-rb-enforcement.md)
- Distro policy, where reproducible builds block updating packages
=====================================
_events/gothenburg2026/agenda/d3-rebuilderd.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 3 - rebuilderd
+order: 10
+permalink: /events/gothenburg2026/agenda/d3-rebuilderd.md
+---
## rebuilderd
- different language ecosystems
=====================================
_events/gothenburg2026/agenda/d3-sourcedateepoch.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 3 - SOURCE_DATE_EPOCH
+order: 10
+permalink: /events/gothenburg2026/agenda/d3-sourcedateepoch.md
+---
- Bernhard proposed changes to the S_D_E spec on the rb-general list, which we discussed and found largely uncontroversial, so we went on to prepare actual MRs and propose them on the list:
- https://salsa.debian.org/reproducible-builds/specs/source-date-epoch-spec/-/merge_requests/8 links to all the others:
- https://salsa.debian.org/reproducible-builds/specs/source-date-epoch-spec/-/merge_requests/7
=====================================
_events/gothenburg2026/agenda/d3-trusting-trust.md
=====================================
@@ -1,3 +1,9 @@
+---
+layout: event_detail
+Gothenburg 2026 - Day 3 - Trusting trust
+order: 10
+permalink: /events/gothenburg2026/agenda/d3-trusting-trust.md
+---
- Well-known trusting trust problem:
- Fully recursive reproducible builds
- Beyond this, there are firmware and hardware dependencies that many manufacturers share (e.g. battery manufacturers)
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/54ea9daeb899244471b53cd71f62cd3eb12598b0
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/54ea9daeb899244471b53cd71f62cd3eb12598b0
You're receiving this email because of your account on salsa.debian.org. Manage all notifications: https://salsa.debian.org/-/profile/notifications | Help: https://salsa.debian.org/help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.reproducible-builds.org/pipermail/rb-commits/attachments/20260925/5ba07723/attachment.htm>
More information about the rb-commits
mailing list