[Git][reproducible-builds/reproducible-website][master] Interview Jochen: comments from Max

[Jochen Sprickerhof (@jspricke)]

Jochen Sprickerhof pushed to branch master at Reproducible Builds / reproducible-website


Commits:
953236c7 by Jochen Sprickerhof at 2026-08-26T11:42:21+02:00
Interview Jochen: comments from Max

- - - - -


1 changed file:

- _posts/2026-08-25-supporter-spotlight-jochen-sprickerhof.md


Changes:

=====================================
_posts/2026-08-25-supporter-spotlight-jochen-sprickerhof.md
=====================================
@@ -36,9 +36,9 @@ bit reproduce the packages distributed by Debian.
   reproducible-builds?**
 
 **Jochen:**
-I started my Debian journey as a pupil, converting my school to Debian
+I started my Debian journey as a teenager, converting my school to Debian
 and serving as it's system administrator for 13 years. After studying
-applied system science I joined the universities robotics labs where I
+applied system science I joined the university's robotics labs where I
 worked on the robot operating system ROS and the point cloud library
 PCL. In the end I enjoyed programming more then writing papers so I
 eventually left academia for a robotics startup. Some years ago I
@@ -148,7 +148,7 @@ $ history | cut -d' ' -f1 | sort | uniq -c | sort -nr | head -10
   used to...**
 
 **Jochen:**
-You can check for yourself, it is last time I did:
+You can check for yourself - it was last time I did:
 [reproduce.debian.net/excuses.html?source_name=fish](https://reproduce.debian.net/excuses.html?source_name=fish) But looking
 through the other commands, neovim sadly is not:
 [reproduce.debian.net/excuses.html?source_name=neovim](https://reproduce.debian.net/excuses.html?source_name=neovim) I hope we
@@ -183,13 +183,13 @@ to get the sources and all the tools I mentioned above.
 Right now reproduce.debian.net shows over 98% reproducibility though
 there are still over 650 package left and some will probably need a
 lot of work. But actually I think making packages reproducible is just
-the first step. For me this is a project to gain trust into the
+the first step. For me this is a project to build confidence in the
 system. To reproduce a package we have two parts: The source of the
 package and the build environment. Fixing the packages means gaining
-trust into the first part but we still rely on the individual build
+confidence in the first part but we still rely on the individual build
 environments for each package, as we need to use the same compiler
 that was used when the package was build initially. So we have to keep
-around all historical versions of all toolchain packages. I really
+around every historical version of all toolchain packages. I really
 would like to remove this extra archive which means we would have to rebuild
 all of Debian around release time. I am dreaming of a Debian release
 where you could bit by bit reproduce every package just from the



View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/953236c7a7ce9c3701ef284501468d35635a00b5

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/953236c7a7ce9c3701ef284501468d35635a00b5
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/20260826/8af85986/attachment.htm>