[Git][reproducible-builds/reproducible-website][master] fix: minor typo and link URL

[Mattia Rizzolo (@mattia)]

Mattia Rizzolo pushed to branch master at Reproducible Builds / reproducible-website


Commits:
7f3e9550 by Pol Dellaiera at 2023-10-29T22:38:39+01:00
fix: minor typo and link URL

- - - - -


2 changed files:

- _blog/posts/90.md
- _docs/environment_variations.md


Changes:

=====================================
_blog/posts/90.md
=====================================
@@ -124,7 +124,7 @@ of them in time for Debian stable, though we will see how that goes in the end
 - Maria Glukhova:
   - [Add image metadata comparison.](https://salsa.debian.org/reproducible-builds/diffoscope/commit/06e4ca7)
   - [Zipinfo included in APK files comparison.
-    (Closes: #850502)](https://anonscm.debian.org/git/reroducible/diffoscope.git/commit/?id=9749aa9)
+    (Closes: #850502)](https://anonscm.debian.org/git/reproducible-builds/diffoscope.git/commit/?id=9749aa9)
   - [Remove archive name from apktool.yml and rename it.
     (Closes: #850501)](https://salsa.debian.org/reproducible-builds/diffoscope/commit/b85e785)
 - Chris Lamb:


=====================================
_docs/environment_variations.md
=====================================
@@ -4,7 +4,7 @@ layout: docs
 permalink: /docs/env-variations/
 ---
 
-We identify 16 variations in the environment variables that might lead to unreroducible builds. Each environment variable serves as a valuable resource for understanding and addressing the challenges associated with achieving reproducible builds.
+We identify 16 variations in the environment variables that might lead to unreproducible builds. Each environment variable serves as a valuable resource for understanding and addressing the challenges associated with achieving reproducible builds.
 
 Archive Metadata
 ----------------
@@ -46,7 +46,7 @@ Build Timestamp
 
 The [build timestamp]({{ "/docs/timestamps/" | relative_url }}) refers to the information associated with the date and time of a specific build execution. It is important to consider that during the build process, any files that are generated, modified, or accessed may embed compile-time timestamps in the form of logs within the resulting build artifacts. These timestamps can lead to differences in the content of the build artifacts when distinct builds are performed due to changes in build time.
 
-However, it is essential to recognize that relying solely on timestamps provides limited insight into the software build itself. This is because builds can be executed on an older version of the software while still having a more recent timestamp. 
+However, it is essential to recognize that relying solely on timestamps provides limited insight into the software build itself. This is because builds can be executed on an older version of the software while still having a more recent timestamp.
 
 An example of a timestamp variation would be the [C pre-defined macros](https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_from_cpp_macros_issue.html) such as `_Date_` and `_Time_` are utilized to output the current time. It is important to note that when these macros are invoked by distinct build systems, different timestamps are incorporated into the compiled code, resulting in variations in the generated build artifacts.
 
@@ -120,7 +120,7 @@ For instance, the `ldaptor` package relies on a python module called [weakref](h
 Snippet Encoding
 ----------------
 
-Snippet Encoding is the process of encoding strings or specific segments of a file using random numbers. These random numbers, functioning as security keys, are utilized to encode data and prevent unauthorized usage. Within the build execution, these randomized digits are incorporated into the resulting artifacts. Since distinct build systems generate different sets of randomized digits, the resulting build artifacts exhibit varying content. 
+Snippet Encoding is the process of encoding strings or specific segments of a file using random numbers. These random numbers, functioning as security keys, are utilized to encode data and prevent unauthorized usage. Within the build execution, these randomized digits are incorporated into the resulting artifacts. Since distinct build systems generate different sets of randomized digits, the resulting build artifacts exhibit varying content.
 
 For instance, during the execution of distinct builds, the usage of the `srandom` utility has been observed to introduce unreproducibility. This utility is employed to provide a seed value to the randomization function, ensuring randomness in the generated output. However, it was found that the seed value stored in the resulting build artifact differed for each build, leading to unreproducible outcomes as seen [here](https://tests.reproducible-builds.org/debian/issues/unstable/markdown_random_email_address_html_entities_issue.html).
 



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

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