[Git][reproducible-builds/reproducible-website][master] Change 7 words towards standard terms

[Bernhard M. Wiedemann]

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


Commits:
e815b1d5 by Bernhard M. Wiedemann at 2019-07-12T09:40:57Z
Change 7 words towards standard terms

- - - - -


4 changed files:

- _events/athens2015/benefits.md
- _events/berlin2016/agendabrainstorming.md
- _events/berlin2017/existingtools.md
- _events/paris2018/report.md


Changes:

=====================================
_events/athens2015/benefits.md
=====================================
@@ -14,7 +14,7 @@ What came during the discussion:
 
  * Faster development times:
    + Through caching of intermediate build products.
-   + In FreeBSD packages are rebuilt weekly and non-reproducible packages get reuploaded every time.
+   + In FreeBSD packages are rebuilt weekly and unreproducible packages get reuploaded every time.
  * Investigate whether the source changes are reflected in associated changes in the binary.
  * Validation of cross compilers (slow arches can be cross compiled).
  * Recreation of debug symbols at later times.


=====================================
_events/berlin2016/agendabrainstorming.md
=====================================
@@ -28,7 +28,7 @@ REPRODUCIBLE FILESYSTEM IMAGES (SEE ALSO: SQUASHFS)
  - Figure out how to build _ext4 images_ reproducibly (in a VM for extra credit) (2)
  - How do we reproduce higher level artifacts, livecds, containers, installers, etc. (2)
  - Determine relevance of reproducibility for non-executable file formats (1)
- - Brainstorm about non-reproducible VCS->tarball steps (e.g. autoconf, etc.)
+ - Brainstorm about unreproducible VCS->tarball steps (e.g. autoconf, etc.)
  - What do we use for base images? (2)
 
 BUILDINFO (GENERAL, DOC, ADVOCACY)


=====================================
_events/berlin2017/existingtools.md
=====================================
@@ -19,7 +19,7 @@ stripnondeterminism
 -------------------
 
 - runs after the build
-- remove known causes of non-reproducible
+- remove known causes of nondeterminism
 - e.g. jar's aren't reproducible and make it reproducible
 - remove several timestamp
 - should not exist by designed
@@ -104,9 +104,9 @@ reproshilds.io??
 - create a feedback api.
 - get badges
 
-The unreproducible packages
+The unreproducible package
 --------------------------
-have a package full of non-reproducible things
+have a package full of unreproducible things
 
 next sessions
 ------------


=====================================
_events/paris2018/report.md
=====================================
@@ -3333,7 +3333,7 @@ tl;dr;
 <a name="Toc11440_331763073"></a>
 #### Debugging for reproducibility issues
 
-We discussed the 10 known sources of indeterminism documented in
+We discussed the 10 known sources of nondeterminism documented in
 [github.com/bmwiedemann/theunreproduciblepackage/](https://github.com/bmwiedemann/theunreproduciblepackage/)
 
 and covered Bernhard's how-to-debug list:
@@ -3353,7 +3353,7 @@ and covered Bernhard's how-to-debug list:
     Makefile
 
 -   use difflog to see if something interesting happens related to
-    indeterministic files
+    nondeterministic files
 
 -   review relevant files (configure, Makefile,
     CMakeLists.txt, setup.py)



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

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/commit/e815b1d5c12e94fd86a8929fedc4a480b1b03ec5
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/20190712/b5e9cf78/attachment.html>