[Git][reproducible-builds/reproducible-presentations][master] bornhack.dk talk, WIP. almost there

Holger Levsen (@holger) gitlab at salsa.debian.org
Sat Jul 18 13:48:28 UTC 2026



Holger Levsen pushed to branch master at Reproducible Builds / reproducible-presentations


Commits:
dd252e00 by Holger Levsen at 2026-07-18T15:46:50+02:00
bornhack.dk talk, WIP. almost there

Signed-off-by: Holger Levsen <holger at layer-acht.org>

- - - - -


1 changed file:

- 2026-07-18-reproduce.debian.net-reproducing_what_is_distributed_from_ftp.debian.org/index.html


Changes:

=====================================
2026-07-18-reproduce.debian.net-reproducing_what_is_distributed_from_ftp.debian.org/index.html
=====================================
@@ -621,9 +621,8 @@ Warpforge.
 		<li class="fragment">2015 - pacman records BUILDINFO</li> 
 		<li class="fragment">2017 - pacman S_D_E support & archlinux-repro</li> 
 		<li class="fragment">2019 - started archiving packages required for rebuilds</li> 
-		<li class="fragment">2020 - rebuilderd instance, [core] 86%</li> 
+		<li class="fragment">2020 - 1st rebuilderd instance, [core] 86%</li> 
 		<li class="fragment">2024 - reproducible minimal container userland</li> 
-		<li class="fragment">2025 - 12% left to make reproducible (4 for minimal bootable install)</li>
 	</ul>
       </section>                                                                                                                             
       <section data-background="images/archlinux.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
@@ -650,30 +649,29 @@ Warpforge.
       <section data-background="images/nixos.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
         <h3>NixOS</h3>
 	<ul>
-		<li>Talk yesterday in the <em>Nix and NixOS</em> track:<br> https://fosdem.org/2025/schedule/event/fosdem-2025-4430-how-reproducible-is-nixos-/
+		<li>Talk at FOSDEM 25 in the <em>Nix and NixOS</em> track:<br> https://fosdem.org/2025/schedule/event/fosdem-2025-4430-how-reproducible-is-nixos-/
 	</ul>
         <img src="images/nixos-reproducibility-overall-absolute.png" style="height: 400px;">
      </section>
 
-      <section data-background="images/freebsd.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
-        <h3>FreeBSD</h3>
+     <section data-background="images/fedora.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
+        <h3>Fedora</h3>
 	<ul>
-		<li>Talk at FOSDEM 2016 by Baptiste Daroussin: Reproducible builds in FreeBSD packages</li>
-		<li class="fragment">FreeBSD base system continously tested on jenkins.debian.net since 2015. Just as NetBSD is :)</li>
-		<li> </li>
-		<li> </li>
-		<li> </li>
-		<li> </li>
+		<li>https://fedoraproject.org/wiki/Changes/Package_builds_are_expected_to_be_reproducible</li>
+		<li>The goal is to have no fewer than 99% of package builds reproducible.</li>
+		<li>Targeted release: Fedora 45</li>
+		<li class="fragment">No easy fixes for: haskell, minggw, golang, kernel & secureboot
 	</ul>
      </section>
 
+
       <section data-background="images/freebsd.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
         <h3>FreeBSD</h3>
 	<ul>
 		<li>Talk at FOSDEM 2016 by Baptiste Daroussin: Reproducible builds in FreeBSD packages</li>
 		<li>FreeBSD base system continously tested on tests.reproducible-builds.org since 2015. Just as NetBSD is :)</li>
 		<li class="fragment">In 2016 there was WIP for reproducing ports and achieved 80%. And then this efford got stalled...</li>
-		<li class="fragment">until now: https://freebsdfoundation.org/blog/zero-trust-builds-for-freebsd/</li>
+		<li class="fragment">until: https://freebsdfoundation.org/blog/zero-trust-builds-for-freebsd/</li>
 	</ul>
      </section>
 
@@ -845,10 +843,10 @@ Warpforge.
         <h2>Debian policy</h2>
         <ul>
         <li>2017: packages <em>should</em> build reproducibly.</li>
-        <li class="fragment">2026? reproducible packages <em>must not</em> regress.</li>
-        <li class="fragment">2026? NEW packages <em>must</em> build reproducibly.</li>
-        <li class="fragment">2027? packages <em>must</em> build reproducibly.</li>
-        <li class="fragment">In practice the release team will enforce this before it becomes policy. ☺️ </li>
+        <li class="fragment">202? reproducible packages <em>must not</em> regress.</li>
+        <li class="fragment">202? NEW packages <em>must</em> build reproducibly.</li>
+        <li class="fragment">202? packages <em>must</em> build reproducibly.</li>
+        <li class="fragment">In practice the release team enforces this before it becomes policy. ☺️ </li>
         </ul>
       </section>
 
@@ -859,12 +857,12 @@ Warpforge.
         <li>2026 reproducible packages <em>must not</em> regress.</li>
         <li>2026 NEW packages <em>must</em> build reproducibly.</li>
         <li>2026 packages <em>must</em> build reproducibly.</li>
-        <li>In practice the release team will enforce this before it becomes official Debian policy. ☺️ </li>
+        <li>In practice the release team enforces this before it becomes official Debian policy. ☺️ </li>
         </ul>
       </section>
 
       <section data-background="images/rb-logo.svg" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
-        <h3>and then at the MiniDebConf Hamburg 2025</h3>
+        <h3>at the MiniDebConf Hamburg 2025</h3>
         <ul>
         <li>Paul (elbrus) and me talked about <code>forky</code> in future...
         <img src="images/forky-toy-story-4.rhorizontal.w700.jpg" class="fragment">
@@ -874,7 +872,7 @@ Warpforge.
       <section data-background="images/minidebconfhh2026-logo.svg" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
         <h3>...so for forky...!</h3>
         <ul>
-        <li>britney now finally <i>has been</i> configured to not let (most) unreproducible packages migrate to testing!
+        <li>britney in 2026 finally <i>has been</i> configured to not let (most) unreproducible packages migrate to testing!
         <h2 class="fragment">🥳 🤗 🫠 🥳 </h2>
         </ul>
         </section>
@@ -905,20 +903,8 @@ Warpforge.
         </ul>
         </section>
 
-      <section data-background="images/debian_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
-        <h2>Debian's release team policy</h2>
-        <ul>
-        <li>2017: packages <em>should</em> build reproducibly.</li>
-        <li>2026 reproducible packages <em>must not</em> regress.</li>
-        <li>2026 NEW packages <em>must</em> build reproducibly.</li>
-        <li>2026 packages <em>must</em> build reproducibly.</li>
-        <li>In practice the release team will enforce this before it becomes official Debian policy. ☺️ </li>
-        </ul>
-      </section>
-
 
-
-      <section data-background="images/debian_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
+      <!-- section data-background="images/debian_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
         <h3>The <i>old</i> path to 100% (using old CI numbers...)</h3>
                 <table>
                 <tr><th>suite</th><th>reproducible</th><th style="color: #ff0000">unreproducible</th></tr>
@@ -972,7 +958,7 @@ Warpforge.
         <li>has everything (=<code>main</code> and <code>non-free-firmware</code>) since <code>trixie</code>, IOW, we have:<br> <code>experimental</code>, <code>unstable</code>, <code>forky</code>, <code>trixie</code>,  <code>trixie-security</code>,  <code>trixie-updates</code>, <code>trixie-proposed-updates</code>, <code>trixie-backports</code>
         <li class='fragment'>has all archs except <code>s390x</code>  and <code>loong64</code>. </small>(We do have <code>armel</code> for <code>trixie</code>.)</small>
         <li class='fragment'>once <code>trixie</code> becomes LTS, we'll add <code>trixie</code> LTS.
-      </section>
+      </section -->
 
  <section data-background="images/debian_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
         <h3><code>https://reproduce.debian.net</code></h3>
@@ -1126,8 +1112,8 @@ Warpforge.
         <h3>duke nukem?!?</h3>
         <ul>
         <li>for forky we will be rather liberal with accepting unreproducible packages.</li>
-        <li class="fragment">but for duke... shall we get more ambitious and more aggressive?</li>
-        <li class="fragment">we could declare <i>zero unreproducible packages in <code>main</code></i> as our goal for duke. shall we?</li>
+        <li class="fragment">but for duke... we shall become more ambitious and more aggressive:</li>
+        <li class="fragment">we should declare <i>zero unreproducible packages in <code>main</code></i> as our goal for duke.</li>
         </ul>
         </section>
 



View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/dd252e00df8a9c4276e593bdedf7109193dfd8b4

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/dd252e00df8a9c4276e593bdedf7109193dfd8b4
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/20260718/bcf9b95a/attachment.htm>


More information about the rb-commits mailing list