[Git][reproducible-builds/reproducible-presentations][master] fosdem 2024: some more finetuning
Holger Levsen (@holger)
gitlab at salsa.debian.org
Sun Feb 4 21:28:45 UTC 2024
Holger Levsen pushed to branch master at Reproducible Builds / reproducible-presentations
Commits:
6c234311 by Holger Levsen at 2024-02-04T22:28:33+01:00
fosdem 2024: some more finetuning
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
2 changed files:
- 2024-02-03-R-B-the-first-10-years/index.html
- 2024-02-03-R-B-the-first-10-years/todo
Changes:
=====================================
2024-02-03-R-B-the-first-10-years/index.html
=====================================
@@ -571,8 +571,8 @@
<h3>We need you!<br> Please support these efforts</h3>
<ul>
<li>Do you think reproducible builds should happen?<br> If so, please help. We need your help and support.</li>
- <span class="fragment"><li>The goals of this talk it to recap what we have done and to celebrate 10 years of awesomeness of <b>many</b> with the aim to get you informed, excited & involved.<br>And to explain that a lot of work and support is still needed, despite all the progress and successes so far!<br> We are still far from being done.</li>
- <li>We can do it! 💪</li></span>
+ <span class="fragment"><li>The goals of this talk it to recap what we have done and to celebrate 10 years of awesomeness of <b>many</b> with the aim to get you informed, excited & involved.<br>And to explain that a lot of work and support is still needed. We are still far from being done, despite all the progress and successes so far!</li>
+ <li class="fragment">And: it's doable, we can do it together! 💪</li></span>
</ul>
</section>
@@ -592,7 +592,7 @@
</section>
<section data-background="images/FOSDEM_logo.svg" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
- <h2>Ancient history (>10 years ago)</h2>
+ <h2>some ancient history (>10 years ago)</h2>
<ul>
<li class="fragment">Thread on debian-devel at lists.debian.org from 2007. Deemed undoable by many.</li>
</ul>
@@ -613,7 +613,7 @@
<h2>Ancient history (>10 years ago)</h2>
<ul>
<li>Thread on debian-devel at lists.debian.org from 2007. Deemed undoable by many.</li>
- <li class="fragment">Though the idea initially appeared in 2000 on debian-devel at l.d.o.</li>
+ <li class="fragment">Before that a similar idea appeared in 2000 on debian-devel at l.d.o.</li>
<li class="fragment">And then in 2017 we learned from John Gilmore on rb-general at lists.reproducible-builds.org that GCC was reproducible in the early 1990s on several architectures!</li>
</ul>
</section>
@@ -665,8 +665,9 @@
</section>
<section data-background="images/FOSDEM_logo.svg" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
+ <h4>By 2024 Reproducible Builds has been widely understood:</h4>
<ul>
- <li> By 2024 Reproducible Builds has been widely understood:
+ <li>
<br><span class="fragment" style="font-size: 100%">https://reproducible-builds.org/resources/
<br>https://reproducible-builds.org/docs/
<br>https://reproducible-builds.org/docs/publications/</span></li>
@@ -701,7 +702,7 @@
<h2>How did we <i>really</i> get there?</h2>
<li>Money / Bitcoin</li>
<li>Edward Snowden / Torbrowser</li>
- <li class="fragment">...and a LOT of work by MANY people over MANY years</li>
+ <li class="fragment">...and a LOT of work by MANY people over MANY years.</li>
</section>
<section data-background-color="white">
@@ -836,12 +837,12 @@
<section data-background="images/FOSDEM_logo.svg" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
<h2>Ressources about unreproducibilities:</h2>
<ul>
- <li>422 known issue types in reproducible-notes.git<li>
- <li>https://reproducible-builds.org/docs/</li>
- <li>Lunar's talk at CCCamp 2015</li>
+ <li>https://reproducible-builds.org/docs/</li>
+ <li class="fragment">422 known issue types in reproducible-notes.git<li>
+ <li class="fragment">Lunar's talk at CCCamp 2015</li>
<span class="fragment">
- <li>It's much easier to show common pitfalls making a package unreproducible than the opposite:</li>
- <li>https://github.com/bmwiedemann/theunreproduciblepackage</li>
+ <li>It's much easier to show common pitfalls making a package unreproducible than the opposite:<ul>
+ <li style="font-size: 85%">https://github.com/bmwiedemann/theunreproduciblepackage</li></ul></li</ul></li>
</ul>
</span>
</section>
@@ -956,7 +957,7 @@ Warpforge.
<h2>Detour: more unexpected benefits of reproducible builds</h2>
<ul>
<li class="fragment">https://bootstrappable.org began as breakout session at the Reproducible Builds Summit 2016 in Berlin.</li>
- <li class="fragment"><em>as I understand it</em> is about bootstrapping toolchain binaries from sources <em>only</em>, so starting from around 500 handwritten bytes of machine code, a very simple assembler is build and then assembled some more, until it can build mes, which can build tinyCC, which can build an ancient GCC which then can build another ancient GCC, which then can be used to build modern GCC and the rest of the universe.</li>
+ <li class="fragment"><em>as I understand it</em> is about bootstrapping toolchain binaries from sources <em>only</em>, except starting from around 500 handwritten bytes of machine code, a very simple assembler is build and then assembled some more, until it can build mes, which can build tinyCC, which can build an ancient GCC which then can build another ancient GCC, which then can be used to build modern GCC and the rest of the universe.</li>
</ul>
</section>
@@ -1084,8 +1085,8 @@ Warpforge.
<ul>
<li>2017: packages <em>should</em> build reproducibly.</li>
<li class="fragment">2025? reproducible packages <em>must not</em> regress.</li>
- <li class="fragment">2025? NEW packages <em>must</em> build reproducibly (to be allowed into <code>testing</code> and therefore into <code>stable</code>).</li>
- <li class="fragment">2027? packages <em>must</em> build reproducibly (to be allowed into <code>testing</code> and <code>stable</code>).</li>
+ <li class="fragment">2025? NEW packages <em>must</em> build reproducibly.</li>
+ <li class="fragment">2027? packages <em>must</em> build reproducibly.</li>
</ul>
</section>
@@ -1102,13 +1103,13 @@ Warpforge.
<section data-background="images/FOSDEM_logo.svg" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
<h2>Debian <em>testing</em> migration</h2>
<ul style="font-size: 94%">
- <li>since the end of 2023, CI reproducible-builds results are included in the excuses output for Debian testing migration, but there is no penalty nor bonus yet.</li>
- <li>in 2025 for Debian 14 "<em>forky</em>" however there should penalties for violating:
+ <li>Since the end of 2023, CI reproducible-builds results are included in the excuses output for Debian testing migration, but there is no penalty nor bonus yet.</li>
+ <li>In 2025 for Debian 14 "<em>forky</em>" however there should penalties for violating:
<ul>
- <li class="fragment">reproducible packages <em>must not</em> regress.</li>
+ <li class="fragment">reproducible packages <em>must not</em> regress (to be allowed into <code>testing</code> and therefore into <code>stable</code>).</li>
<li class="fragment">NEW packages <em>must</em> build reproducibly (to be allowed into <code>testing</code> and therefore into <code>stable</code>).</li>
</ul>
- <li class="fragment">in 2025 this better would have whitelisting for some needed packages, but less in 2027 and eventually we can stop those exceptions.</li>
+ <li class="fragment">At first there could be whitelisting of some needed packages, but less over time until we can drop those exceptions.</li>
</ul>
</section>
@@ -1177,6 +1178,7 @@ Warpforge.
<li class="fragment">so <em>debrebuild</em> can use <em>debootsnap</em> together with <em>metasnap</em> to establish trust.</li>
<li class="fragment">one blocking bug currently: issue #40</li>
<li class="fragment">hopefully usable RSN. Many thanks to lynxis and josch!</li>
+ <li class="fragment">also: snapshot.d.o is still awesome, despite it's flaws today. We need (to fix) it! Many thanks weasel & DSA!</li>
</ul>
</section>
@@ -1185,7 +1187,7 @@ Warpforge.
<ul>
<li>testing migration can and will be used to enforce policy also in regards of reproducible builds (probably only enforcing for real in 2025...)</li>
<li class="fragment">for a sensible setup of that, we need real rebuilders, aiming to rebuild what Debian distributes.</li>
- <li class="fragment">for that, we need a working snapshot.d.o, which with rebuilder-snapshot now finally is there.</li>
+ <li class="fragment">for that, we need a better working snapshot.d.o, which with rebuilder-snapshot finally is there.</li>
<li class="fragment">CI builds will stay, to find issues. Rebuilders are needed to show the absence of issues.</li>
</ul>
</section>
=====================================
2024-02-03-R-B-the-first-10-years/todo
=====================================
@@ -1,3 +1,4 @@
+forky in the table with 42 unreproducible packages?
missing a bit in talk & slides: snapshot.d.o is awesome, and not only buggy. and we need it.
the end could be a bit clearer...
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/6c234311e86fc0ac40be94268052a1e88d93f28b
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/6c234311e86fc0ac40be94268052a1e88d93f28b
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/20240204/591153cf/attachment.htm>
More information about the rb-commits
mailing list