[Git][reproducible-builds/reproducible-website][master] Interview Jochen: annotate links, minor wording fixes

Wed Aug 26 07:29:40 UTC 2026


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


Commits:
9205418e by Jochen Sprickerhof at 2026-08-26T09:28:57+02:00
Interview Jochen: annotate links, minor wording fixes

- - - - -


1 changed file:

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


Changes:

=====================================
_posts/2026-08-25-supporter-spotlight-jochen-sprickerhof.md
=====================================
@@ -22,12 +22,12 @@ one of the newer members of the Reproducible Builds project core team.
   of things do you work on?**
 
 **Jochen Sprickerhof:**
-I am a freelance programmer working on Open Source. Mainly doing Debian,
-F-Droid and some smaller software projects. In general I made it a
+I am a freelance programmer working on Open Source. Mainly doing [Debian](https://debian.org),
+[F-Droid](https://f-droid.org) and some smaller software projects. In general I made it a
 habit to look into every software I use and try to fix bugs or add
 features I need. In Debian I maintain about 180 packages with topics
 from home banking over build systems to robotics. Most of my time I
-currently work on reproduce.debian.net where we try to bit by
+currently work on [reproduce.debian.net](https://reproduce.debian.net) where we try to bit by
 bit reproduce the packages distributed by Debian.
 
 <br>
@@ -52,14 +52,14 @@ lots of fun with.
 **Vagrant: What projects did you recently make big progress on?**
 
 **Jochen:**
-A recent example is metasnap.debian.net. It is a meta archive of
-snapshot.debian.org that is an archive of all packages in Debian. Let
+A recent example is [metasnap.debian.net](https://metasnap.debian.net). It is a meta archive of
+[https://snapshot.debian.org](snapshot.debian.org) that is an archive of all packages in Debian. Let
 me explain it the other way round. With reproduce.debian.net we try to
 reproduce the packages as they are distributed by the Debian
-archive. That means we need the same build environment (compilers,
+archive. For that we need the same build environment (compilers,
 build tools..) as was used by Debian back when the original package
 was compiled. Luckily snapshot.debian.org has all those but they are not
-easily accessible via apt. So metasnap.debian.net provides a mapping from a
+easily accessible via apt, Debians package manager. So metasnap provides a mapping from a
 package name and version to the apt repo on snapshot.debian.org to download
 it from. It was created by josch some time ago and is an awesome
 work. But when we tried to reproduce more and more packages on
@@ -91,7 +91,7 @@ release team and reproducible builds sat together and decided that the
 overall state is good enough and now packages that regress on
 reproducibility are blocked from entering the next Debian release. But
 that does not mean all the work is on the shoulders of the Debian
-package maintainers. Since I have been constantly looking at the
+package maintainers. Since then I have been constantly looking at the
 migration tooling to spot regressions and provide fixes. Also a couple
 of maintainers reached out to us for help and I hope more will do so
 in future.
@@ -106,7 +106,7 @@ The central tool to reproduce Debian packages is debrebuild, also written
 by josch. Currently it has two ways to retrieve the build dependencies of
 a package. Either it uses metasnap.debian.net as explained above or it can
 access the Debian unstable apt archive directly. This allows to test packages
-locally before everything is indexed on metasnap.debian.net by compiling
+locally before everything is indexed on metasnap by compiling
 against against unstable. But actually there are many other apt repositories
 to query, like Debian stable or even derivatives. Adding support for an
 optional list of apt repositories in debrebuild would be great. That would
@@ -120,7 +120,7 @@ also be a big step to support reproducing other Debian distributions.
 It would be great to integrate metasnap.debian.net into
 snapshot.debian.org. There is some discussion on it already in
 
-https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650783
+[bugs.debian.org650783](https://bugs.debian.org/650783)
 
 <br>
 
@@ -150,9 +150,9 @@ $ history | awk '{print $1}' | sort  | uniq --count | sort --numeric-sort --reve
 
 **Jochen:**
 You can check for yourself, it is last time I did:
-https://reproduce.debian.net/excuses.html?source_name=fish But looking
+[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:
-https://reproduce.debian.net/excuses.html?source_name=neovim I hope we
+[reproduce.debian.net/excuses.html?source_name=neovim](https://reproduce.debian.net/excuses.html?source_name=neovim) I hope we
 can fix that at some point
 
 <br>
@@ -161,7 +161,7 @@ can fix that at some point
   you can just pass the source package name to check the current results?**
 
 **Jochen:**
-Yes. An other one is https://udd.debian.org/reproducibility/ where you
+Yes. An other one is [https://udd.debian.org/reproducibility/](https://udd.debian.org/reproducibility/) where you
 can list all packages of a Debian maintainer. It also lists source
 reproducibility and has nice filter.
 
@@ -191,14 +191,14 @@ trust into 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
-would like to cut down this tree which means we would have to rebuild
+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
 released versions. Due to how Debian works this is not a trivial
 rebuild but will need some work on the infrastructure. By the way,
 initially there was a third component to pay attention to: any
 connection to the outside world during the build. Luckily we fixed the
-Debian buildds to not allow network connections during the build some
+Debian build daemons to not allow network connections during the build some
 time ago.
 
 <br>



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

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/9205418e23ad6e448861a867cfe59529bc08ddaf
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/e6f3acdb/attachment.htm>
