[Git][reproducible-builds/reproducible-presentations][master] toulouse talk: wip, polishing
Holger Levsen (@holger)
gitlab at salsa.debian.org
Fri Nov 15 22:11:22 UTC 2024
Holger Levsen pushed to branch master at Reproducible Builds / reproducible-presentations
Commits:
374bc66c by Holger Levsen at 2024-11-15T23:11:15+01:00
toulouse talk: wip, polishing
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
2 changed files:
- 2024-11-16-R-B-rebuilding-what-is-distributed-from-ftp.debian.org/index.html
- 2024-11-16-R-B-rebuilding-what-is-distributed-from-ftp.debian.org/todo
Changes:
=====================================
2024-11-16-R-B-rebuilding-what-is-distributed-from-ftp.debian.org/index.html
=====================================
@@ -890,7 +890,7 @@ Warpforge.
</section>
<section data-background="images/Capitole_du_libre_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
- <h3>future reproducibility of Debian amd64</h3>
+ <h3>the path to 100%</h3>
<table>
<tr><th>suite</th><th>reproducible</th><th style="color: #ff0000">unreproducible</th></tr>
<tr style="font-size: 60%">
@@ -933,28 +933,30 @@ Warpforge.
</section>
<section data-background="images/Capitole_du_libre_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
- <h3>Theory vs Praxis</h3>
+ <h3>Theory vs Practice</h3>
<ul>
<li>In theory, we are done. In practice, we have shown that reproducible builds can be done in theory.</li>
- <li class="fragment">For Debian we now need to setup rebuilders (!= CI builders) and we need to store the results somewhere and we need to define criterias how tools should treat that data, and then we need those tools...</li>
- <li class="fragment">And those missing 5% are also crucial however, or at least 1% of them. For Debian, 1% means 300 softwares...</li>
+ <li class="fragment">Now we need to close the gap between theory and practice.</li>
+ <li class="fragment">For Debian we now also need to setup more rebuilderd instances, for all architectures (hardware and admins wanted!), and we need rebuilderd to deal with several architectures and then feed that data to <code>brittney</code>.
+ <li class="fragment">And those missing 4-5% in CI are also crucial however, or at least 1% of them. For Debian, 1% means 300 softwares...</li>
</ul>
</section>
- <section data-background="images/Capitole_du_libre_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
- <img src="images/ccc2014-13.png">
- </section>
-
<section data-background="images/Capitole_du_libre_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
<h3>Summary, looking forward</h3>
<ul>
<li>Many projects support or aim for reproducible builds today. This is a huge success.</li>
<li class="fragment">Next: finish those last 1-5% upstream. (And there are some dragons too, eg PGO.)</li>
- <li class="fragment">Next: create infrastructure, processes and tools to use those results...</li>
+ <li class="fragment">Next: create infrastructure, processes and tools to use those results.</li>
<li class="fragment">Also crucial: project-level consensus and commitment to reproducible builds in practice.</li>
</ul>
</section>
+ <section data-background="images/Capitole_du_libre_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
+ <img src="images/ccc2014-13.png">
+ </section>
+
+
<section data-background="images/Capitole_du_libre_logo.png" data-background-size="10%" data-background-position="93% 9%" data-transition="none">
<img src="images/lunar2.jpg" style="height: 350px;">
<h2>
=====================================
2024-11-16-R-B-rebuilding-what-is-distributed-from-ftp.debian.org/todo
=====================================
@@ -1,7 +1,7 @@
thanks: tell people how awesome they are while they are alive.
last three slides need some more love
-also explain why we are at 33% only now (missing snapshots, fakeroot, snapshot still a bit flaky)
+explain why we are at 33% only now (missing snapshots, fakeroot, snapshot still a bit flaky)
explain how we were at 20% 2 weeks or so
@@ -10,21 +10,5 @@ explain how we were at 20% 2 weeks or so
<Oejet> 159 `^debsnap failed$` out of latest 1000 logs.
<jochensp> | h01ger: most (all?) of the 404 I saw where due to infrastructure and worked when retried
-mention kp is funded by rb now too
-ask people for $arch hardware to setup rebuilderd instances
-mention riscv64 nodes
-different "Summary, looking forward"
-'Short summary of Reproducible Debian' is also not the best title
-
-
-out of scope: ?
- mention potential debian.tests.r-b.o, archlinux.t.r-b.o, though atm tests.r-b.o points to ci tests, thats confusing
- Today many projects support reproducible builds, but it's often still unclear what that means in detail, how it's enforced and how users can know and be confident. I call it reproducible in theory or in CI. This is a massive success! This was thought impossible not long ago!
-
-
-rebuilderd packaging status:
-[21:28] < kpcyrd> e9cd56f7a33d96681d68f5302fedd6d129062191e461b7ad4aa45e8188a41cd4 2029260 rebuildctl_0.20.0-1_amd64.deb
-[21:29] < kpcyrd> it builds but there's some polishing I still need to do
-[21:31] < kpcyrd> for rebuilderd-worker I'm probably going to strip in-toto support for now, and rebuilderd itself needs some work to rewrite from diesel 1.0 to 2.0, and from actix to warp
-[21:31] < kpcyrd> packaging actix would be quite a bit of work and warp is already in Debian
+mention riscv64 nodes?
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/374bc66c593c6eaa5ea83ef602c8b1123644bb39
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-presentations/-/commit/374bc66c593c6eaa5ea83ef602c8b1123644bb39
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/20241115/24671f0b/attachment.htm>
More information about the rb-commits
mailing list