[Git][reproducible-builds/reproducible-presentations][master] minidebconf berlin 2024 preserving artifacts, final version
Holger Levsen (@holger)
gitlab at salsa.debian.org
Sun May 19 10:11:26 UTC 2024
Holger Levsen pushed to branch master at Reproducible Builds / reproducible-presentations
Commits:
1130f234 by Holger Levsen at 2024-05-19T12:11:13+02:00
minidebconf berlin 2024 preserving artifacts, final version
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
5 changed files:
- − 2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_20240201.png
- + 2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_20240519.png
- + 2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_armhf_20240519.png
- 2024-05-19-preserving-other-build-artifacts/index.html
- 2024-05-19-preserving-other-build-artifacts/todo
Changes:
=====================================
2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_20240201.png deleted
=====================================
Binary files a/2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_20240201.png and /dev/null differ
=====================================
2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_20240519.png
=====================================
Binary files /dev/null and b/2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_20240519.png differ
=====================================
2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_armhf_20240519.png
=====================================
Binary files /dev/null and b/2024-05-19-preserving-other-build-artifacts/images/stats_pkg_state_trixie_armhf_20240519.png differ
=====================================
2024-05-19-preserving-other-build-artifacts/index.html
=====================================
@@ -141,7 +141,7 @@
2024-05-19, C-Base, Berlin
</small>
</h6>
- <img src="images/berlin2024.svg" style="height: 70px;">
+ <img src="images/berlin2024.svg" style="height: 140px;">
</section>
<section>
@@ -161,7 +161,7 @@
2024-05-19, C-Base, Berlin
</small>
</h6>
- <img src="images/berlin2024.svg" style="height: 70px;">
+ <img src="images/berlin2024.svg" style="height: 100px;">
</section>
@@ -262,12 +262,20 @@
<img src="images/stats_pkg_state_20150131.png">
</section>
+ <section data-background="images/berlin2024.svg" data-background-size="15%" data-background-position="93% 9%" data-transition="none">
+ <h3>CI results for Debian trixie, 20240519</h3>
+ <img src="images/stats_pkg_state_trixie_20240519.png">
+ </section>
+ <section data-background="images/berlin2024.svg" data-background-size="15%" data-background-position="93% 9%" data-transition="none">
+ <h3>btw, kudos on t64 transition progress!</h3>
+ <img src="images/stats_pkg_state_trixie_armhf_20240519.png">
+ </section>
<section data-background="images/berlin2024.svg" data-background-size="15%" data-background-position="93% 9%" data-transition="none">
- <h3>CI results for Debian trixie, 20240201</h3>
- <img src="images/stats_pkg_state_trixie_20240201.png">
+ <h3>CI results for Debian trixie, 20240519</h3>
+ <img src="images/stats_pkg_state_trixie_20240519.png">
</section>
<section data-background="images/berlin2024.svg" data-background-size="15%" data-background-position="93% 9%" data-transition="none">
@@ -385,7 +393,7 @@
<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 class="fragment">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 (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>
@@ -412,14 +420,15 @@
<li class="fragment">We need to change <code>debian-policy</code>!</li>
<li class="fragment">We can work around 'must-have-offenders' using whitelists in the beginning.</li>
<li class="fragment">The goal is still 100%, whitelists are just a way to achieve that goal eventually.</li>
+ <li class="fragment">Whitelists are delays but no fixes. Fixes are either fixes or removals.</li>
</ul>
</section>
<section data-background="images/berlin2024.svg" data-background-size="15%" data-background-position="93% 9%" data-transition="none">
- <h2>Other build artifacts (and other significant problems)</h2>
+ <h2>Other build artifacts</br> (and other significant problems)</h2>
<ul>
- <li class="fragment">I'll ignore other significant problems today, but they exists: eg signed shim and modules, which rebuilders to trust, etc</h3>
- <li class="fragment">but let's get to those <i>other</i> build artifacts finally.</li>
+ <li class="fragment">I'll ignore <i>other</i> significant problems today, but they exist: eg signed shim and modules, which rebuilders to trust, etc</h3>
+ <li class="fragment">So let's get to those <i>other</i> build artifacts finally.</li>
</ul>
</section>
@@ -428,7 +437,7 @@
<ul>
<li>.deb files (and .changes and .buildinfo)</li>
<li>the one and only build logfile</li>
- <li class="fragment">nothing else, so people invented unreproducible work arounds and store these build artifacts in .deb files.</li>
+ <li class="fragment">nothing else, so people who need those artifacts invented unreproducible work arounds and store these build artifacts in .deb files.</li>
</ul>
</section>
@@ -437,7 +446,7 @@
<ul>
<li>.deb files (and .changes and .buildinfo)</li>
<li>the one and only build logfile</li>
- <li>nothing else, so people invented unreproducible work arounds and store these build artifacts in .deb files.</li>
+ <li>nothing else, so people who need those artifacts invented unreproducible work arounds and store these build artifacts in .deb files.</li>
</ul>
</section>
@@ -450,18 +459,19 @@
<ul>
<li><code>src:binutils</code></li>
<li><code>src:gcc-X</code></li>
- <li class="fragment">We cannot whitelist those packages forever, at least I don't want to. And I want 100% reproducible packages in Debian <code>testing</code> and <code>stable</code> eventually!</li>
- <li class="fragment">The wiki page has more usage examples.</li>
- <li class="fragment">Many thanks to Matthias Klose for writing it.</li>
+ <li class="fragment">We cannot whitelist those packages forever, if we want 100% reproducible packages in Debian <code>testing</code> and <code>stable</code> eventually!</li>
+ <li class="fragment">The wiki page has more usage examples, eg verbose build logs from GNOME packages. prepocessed sources in /tmp/cc*.out </li>
+ <li class="fragment">Many thanks to Matthias Klose for writing it. I do trust him that those artifacts are essential for maintaining those packages.</li>
</ul>
</section>
<section data-background="images/berlin2024.svg" data-background-size="15%" data-background-position="93% 9%" data-transition="none">
<h2>Preserving build artifacts </small></h2>
<ul>
- <li class="fragment">dpkg-distaddfile can be used to add files to debian/files so that they are referenced in the .changes files and thus included in upload. (Thanks to Julien Cristau for pointing thos out.)</li>
+ <li class="fragment">dpkg-distaddfile can be used to add files to debian/files so that they are referenced in the .changes files and thus included in upload. (Thanks to Julien Cristau for pointing this out.)</li>
<li class="fragment">Now we only need <code>dak</code> to accept those files and make them available somewhere. </li>
- <li class="fragment">Profit.🥳🍾👍</li>
+ <li class="fragment">Easy.🥳🍾👍</li>
+ <li class="fragment">(Though this doesn't work for failed builds. But then we have nothing for those now neither.)</li>
</ul>
</section>
@@ -471,7 +481,7 @@
<li>So we only need <code>dak</code> to accept those files and make them available somewhere... 💅</li>
<li class="fragment">Sounds like an easy plan and almost to good to be true.</li>
<li class="fragment">I'll send a mail to debian-devel at l.d.o with a links to that wiki URL and this talk, to continue the discussion on the mailing list.</li>
- <li class="fragment">I've also submitted another workshop on this topic for DebConf24 ad both Matthias and myself will be there. But AIUI this (best) needs the FTP team too.<li>
+ <li class="fragment">I've also submitted another workshop on this topic for DebConf24 and both Matthias and myself will be there. AIUI this really needs the FTP team too.<li>
</ul>
</section>
=====================================
2024-05-19-preserving-other-build-artifacts/todo
=====================================
@@ -1,3 +1 @@
-update graphs and numbers
-show armhf trixie / t64 migration
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/1130f234bb9fe8543114a95b23288d337074f162
--
This project does not include diff previews in email notifications.
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/1130f234bb9fe8543114a95b23288d337074f162
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/20240519/48cca532/attachment.htm>
More information about the rb-commits
mailing list