[Git][reproducible-builds/reproducible-website][master] 201907 report: Fix typo
Daniel Shahaf
gitlab at salsa.debian.org
Sun Aug 4 23:16:18 UTC 2019
Daniel Shahaf pushed to branch master at Reproducible Builds / reproducible-website
Commits:
76589296 by Daniel Shahaf at 2019-08-04T23:16:04Z
201907 report: Fix typo
- - - - -
1 changed file:
- _reports/2019-07.md
Changes:
=====================================
_reports/2019-07.md
=====================================
@@ -70,7 +70,7 @@ There were naturally almost-countless discussions regarding Reproducible Builds
[![]({{ "/images/reports/2019-07/debian.png#center" | prepend: site.baseurl }})](https://debian.org/)
-The release of Debian 10 *buster* has also meant the release cycle for the next release (codenamed *bullseye*) has just begun. As part of this, the [Release Team recently announced](https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html) that Debian will no-longer allow binaries built and uploaded by maintainers on their own machines to be part of the upcoming release. This is great news not only for toolchain security in general but also in that it will ensure that all binaries that will form part of this release will likely have a `.buildinfo` file and metadata that could be used by others to reproduce the builds.
+The release of Debian 10 *buster* has also meant the release cycle for the next release (codenamed *bullseye*) has just begun. As part of this, the [Release Team recently announced](https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html) that Debian will no longer allow binaries built and uploaded by maintainers on their own machines to be part of the upcoming release. This is great news not only for toolchain security in general but also in that it will ensure that all binaries that will form part of this release will likely have a `.buildinfo` file and metadata that could be used by others to reproduce the builds.
Holger Levsen [filed a bug against the underlying tool](https://bugs.debian.org/932849) that maintains the Debian archive ("[dak](https://wiki.debian.org/DebianDak)) after he noticed that `.buildinfo` metadata files were not being automatically propagated if packages had to be manually approved or processed in the so-called "[NEW queue](https://ftp-master.debian.org/new.html)". After it was pointed out that the files were being retained in a separate location, Benjamin Hof [proposed a potential patch](https://bugs.debian.org/932849#22) for the issue which is pending review.
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/commit/7658929610a64dbe6fb9a7f5e0341e4aa51dcd11
--
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/commit/7658929610a64dbe6fb9a7f5e0341e4aa51dcd11
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/20190804/28e301bd/attachment.html>
More information about the rb-commits
mailing list