[Git][reproducible-builds/reproducible-website][master] 2022-11: -1 typo

[Bernhard M. Wiedemann (@bmwiedemann-guest)]

Bernhard M. Wiedemann pushed to branch master at Reproducible Builds / reproducible-website


Commits:
89c32167 by Bernhard M. Wiedemann at 2022-12-08T07:54:49+01:00
2022-11: -1 typo

- - - - -


1 changed file:

- _reports/2022-11.md


Changes:

=====================================
_reports/2022-11.md
=====================================
@@ -62,7 +62,7 @@ Elsewhere in academia, Beatriz Michelson Reichert and Rafael R. Obelheiro have p
 
 [![]({{ "/images/reports/2022-11/golang.png#right" | relative_url }})](https://go.dev/)
 
-* A change was proposed for the [Go programming language](https://go.dev/) to [enable reproducible builds when Link Time Organisation (LTO) is enabled](https://go-review.googlesource.com/c/go/+/413974). As mentioned in the changelog, Morten Linderud's patch fixes two issues when the linker used in conjunction with the `-flto` option: the first involves solving an issue related to [seeded random numbers](https://en.wikipedia.org/wiki/Random_seed); and the second involved the binary embedding the current working directory in compressed sections of the LTO object. Both of these issues made the build unreproducible.
+* A change was proposed for the [Go programming language](https://go.dev/) to [enable reproducible builds when Link Time Optimisation (LTO) is enabled](https://go-review.googlesource.com/c/go/+/413974). As mentioned in the changelog, Morten Linderud's patch fixes two issues when the linker used in conjunction with the `-flto` option: the first involves solving an issue related to [seeded random numbers](https://en.wikipedia.org/wiki/Random_seed); and the second involved the binary embedding the current working directory in compressed sections of the LTO object. Both of these issues made the build unreproducible.
 
 * In the [.NET framework ecosystem](https://en.wikipedia.org/wiki/.NET), a wiki page for the [Roslyn .NET C# and Visual Basic compiler](https://learn.microsoft.com/en-gb/dotnet/csharp/roslyn-sdk/) was uncovered this month that [details its attempts to ensure end-to-end reproducible builds](https://github.com/dotnet/roslyn/blob/main/docs/compilers/Deterministic%20Inputs.md) by focusing on the definition on what are 'considered inputs to the compiler for the purpose of determinism'. This is a spiritual followup to a 2016 blog post by Microsoft developer [Jared Parsons](https://blog.paranoidcoding.com/) on '[Deterministic builds in Roslyn](https://blog.paranoidcoding.com/2016/04/05/deterministic-builds-in-roslyn.html)' which starts: 'It seems silly to celebrate features which should have been there from the start.'
 



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

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/89c32167a9674d3aec3b72fc5cdf416e31d05f1f
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/20221208/573eca08/attachment.htm>