[Git][reproducible-builds/reproducible-website][master] 2022-12: fix broken go.dev link, remove 2 duplicate links

[FC Stegerman (@obfusk)]

FC Stegerman pushed to branch master at Reproducible Builds / reproducible-website


Commits:
c8857d6c by FC Stegerman at 2023-01-05T13:04:00+01:00
2022-12: fix broken go.dev link, remove 2 duplicate links

- - - - -


1 changed file:

- _reports/2022-12.md


Changes:

=====================================
_reports/2022-12.md
=====================================
@@ -25,13 +25,13 @@ We plan to spend three days continuing to the grow of the Reproducible Builds ef
 
 [![]({{ "/images/reports/2022-12/nixos.png#right" | relative_url }})](https://remy.grunblatt.org/nix-and-nixos-my-pain-points.html)
 
-[Rémy Grünblatt](https://remy.grunblatt.org/), an associate professor in the [Télécom Sud-Paris](https://telecom-sudparis.eu/) engineering school wrote up his ["pain points" of using Nix and NixOS](https://remy.grunblatt.org/nix-and-nixos-my-pain-points.html). Although some of the points do not touch on reproducible builds, Rémy touches on problems he has encountered with the different kinds of reproducibility that these distributions appear to promise including configuration files affecting the behaviour of systems, the fragility of upstream sources as well as the conventional idea of binary reproducibility. [[...](https://remy.grunblatt.org/nix-and-nixos-my-pain-points.html)]
+[Rémy Grünblatt](https://remy.grunblatt.org/), an associate professor in the [Télécom Sud-Paris](https://telecom-sudparis.eu/) engineering school wrote up his ["pain points" of using Nix and NixOS](https://remy.grunblatt.org/nix-and-nixos-my-pain-points.html). Although some of the points do not touch on reproducible builds, Rémy touches on problems he has encountered with the different kinds of reproducibility that these distributions appear to promise including configuration files affecting the behaviour of systems, the fragility of upstream sources as well as the conventional idea of binary reproducibility.
 
 ---
 
 [![]({{ "/images/reports/2022-12/golang.png#right" | relative_url }})](https://go.dev/)
 
-Morten Linderud reported that he is quietly optimistic that if [Go programming language](https://go.dev]) resolves all of its issues with reproducible builds ([tracking issue](https://github.com/golang/go/issues/57120)) then the Go binaries distributed from Google and by [Arch Linux](https://archlinux.org/) may be bit-for-bit identical. "It's just a bit early to sorta figure out what roadblocks there are. [But] Go bootstraps itself every build, so in theory I think it should be possible."
+Morten Linderud reported that he is quietly optimistic that if [Go programming language](https://go.dev) resolves all of its issues with reproducible builds ([tracking issue](https://github.com/golang/go/issues/57120)) then the Go binaries distributed from Google and by [Arch Linux](https://archlinux.org/) may be bit-for-bit identical. "It's just a bit early to sorta figure out what roadblocks there are. [But] Go bootstraps itself every build, so in theory I think it should be possible."
 
 
 ---
@@ -50,7 +50,7 @@ A number of changes were made to the Reproducible Builds website and documentati
 
 ---
 
-On [our mailing list](https://lists.reproducible-builds.org/listinfo/rb-general/) this month, James Addison asked a question about whether there has been any effort to trace the files used by a build system in order to identify the corresponding build-dependency packages. [[...](https://lists.reproducible-builds.org/pipermail/rb-general/2022-December/002779.html)] In addition, Bernhard M. Wiedemann then posed a thought-provoking question asking "[How to talk to skeptics?](https://lists.reproducible-builds.org/pipermail/rb-general/2022-December/002782.html)", which was occasioned by a colleague who had [published a blog post in May 2021 skeptical of reproducible builds](https://fy.blackhats.net.au/blog/html/2021/05/12/compiler_bootstrapping_can_we_trust_rust.html). The thread generated a number of replies. [[...](https://lists.reproducible-builds.org/pipermail/rb-general/2022-December/002782.html)]
+On [our mailing list](https://lists.reproducible-builds.org/listinfo/rb-general/) this month, James Addison asked a question about whether there has been any effort to trace the files used by a build system in order to identify the corresponding build-dependency packages. [[...](https://lists.reproducible-builds.org/pipermail/rb-general/2022-December/002779.html)] In addition, Bernhard M. Wiedemann then posed a thought-provoking question asking "[How to talk to skeptics?](https://lists.reproducible-builds.org/pipermail/rb-general/2022-December/002782.html)", which was occasioned by a colleague who had [published a blog post in May 2021 skeptical of reproducible builds](https://fy.blackhats.net.au/blog/html/2021/05/12/compiler_bootstrapping_can_we_trust_rust.html). The thread generated a number of replies.
 
 ---
 



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

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