[Git][reproducible-builds/reproducible-website][master] _reports/2022-01.md: update status of reproducible installations

[Chris Lamb (@lamby)]

Chris Lamb pushed to branch master at Reproducible Builds / reproducible-website


Commits:
808f8b2d by Johannes Schauer Marin Rodrigues at 2022-02-01T17:19:27+00:00
_reports/2022-01.md: update status of reproducible installations

- - - - -


1 changed file:

- _reports/2022-01.md


Changes:

=====================================
_reports/2022-01.md
=====================================
@@ -41,4 +41,13 @@ draft: true
 
 * https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JCM3YKDLS6XVE3H2TFZKKXZX3WBSNCM2/
 
-* FIXME: josch wrote a summary of fixed upstream issues: https://salsa.debian.org/debian/dash/-/merge_requests/9
+## Reproducible Debian installations
+
+Using [`mmdebstrap`](https://tracker.debian.org/pkg/mmdebstrap) it is possible to create a bit-by-bit reproducible chroot when `SOURCE_DATE_EPOCH` is set. As of Debian 11 Bullseye, this works well for all variants except for the variant that includes all `Priority:standard` packages where fontconfig caches, `*.pyc` files and man-db `index.db` are unreproducible. These issues have been addressed in [Tails](https://tails.boum.org/) and live-build by [removing](https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-hooks/99-remove_pyc) [`*.pyc` files](https://salsa.debian.org/live-team/live-build/-/blob/master/share/hooks/normal/0170-remove-python-py.hook.chroot) [as well as](https://gitlab.tails.boum.org/tails/tails/-/blob/stable/config/chroot_local-hooks/99-zzzzzz_reproducible-builds-post-processing#L28) [`index.db`](https://salsa.debian.org/live-team/live-build/-/blob/master/share/hooks/normal/0190-remove-temporary-files.hook.chroot#L6). While `index.db` can be regenerated, there is no simple way to re-create `*.pyc` files and the resulting installation will suffer from reduced performance of Python scripts. Ideally, no removal would be necessary as all files would be created reproducibly in the first place. This January, all three issues are either already fixed or have tested patches filed with the respective packages:
+
+ * [`fontconfig`](https://tracker.debian.org/pkg/fontconfig) cache files are now reproducible in unstable as of the resolution of [#864082](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864082).
+ * [#1004558](https://bugs.debian.org/1004557) filed against [`man-db`](https://tracker.debian.org/pkg/man-db), then reassigned to [`dpkg`](https://tracker.debian.org/pkg/dpkg).
+ * [#1004558](https://bugs.debian.org/1004558) filed against [`python3.10`](https://tracker.debian.org/pkg/python3.10).
+ * [MR !9](https://salsa.debian.org/debian/dash/-/merge_requests/9) filed against [`dash`](https://tracker.debian.org/pkg/dash)
+
+For full Debian desktop live images, remaining issues are collected [here](https://wiki.debian.org/ReproducibleInstalls/LiveImages).



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

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/808f8b2db45b15eb45d7349c68d962422b08b7c5
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/20220201/c3211890/attachment.htm>