[reproducible-website] 01/01: berlin 2016: turn some URLs into links

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository reproducible-website.

commit f8e18b67fe1bb35e065137bb3cc3f4233239df77
Author: Holger Levsen <holger at layer-acht.org>
Date:   Sat Mar 18 11:35:49 2017 +0100

    berlin 2016: turn some URLs into links
    
    Signed-off-by: Holger Levsen <holger at layer-acht.org>
---
 _events/berlin2016/FAQfeedback.md | 17 +++++++++--------
 _events/berlin2016/RPM.md         |  2 +-
 _events/berlin2016/RPMII.md       |  5 +++--
 3 files changed, 13 insertions(+), 11 deletions(-)

diff --git a/_events/berlin2016/FAQfeedback.md b/_events/berlin2016/FAQfeedback.md
index ccddf74..ff466f2 100644
--- a/_events/berlin2016/FAQfeedback.md
+++ b/_events/berlin2016/FAQfeedback.md
@@ -13,7 +13,7 @@ FAQ QUESTIONS
 
 ## What are reproducible builds?
  *  -> Link to definition?
- *  https://pad.riseup.net/p/reproduciblebuildsII-reprobuildsdefinitionII
+ *  see [Defining Reproducible Builds definition II]({{ "/events/berlin2016/reproduciblebuildsdefinitionII/" | prepend: site.baseurl }}) session
 
 ## Why should I care?
  *  -> Give one example for each persona (user, dev/packager, non-technical ppl) and link to [buy-in](/docs/buy-in/) for details.
@@ -93,21 +93,22 @@ Most multi-threaded software provides non predictable output which results in no
 
 # I'm a developer of a distribution and would like to make my distribution reproducible. - FAQ
 * sign up for the the mailing list:
-    * https://lists.reproducible-builds.org/listinfo/rb-general
+    * [https://lists.reproducible-builds.org/listinfo/rb-general](https://lists.reproducible-builds.org/listinfo/rb-general)
+
 * talk to us on irc:
     irc.oftc.net #reproducible-builds
 * link to documentation:
-    * https://reproducible-builds.org/docs/
+    * [https://reproducible-builds.org/docs/](https://reproducible-builds.org/docs/)
 * link to tools:
-    * https://reproducible-builds.org/tools/
+    * [https://reproducible-builds.org/tools/](https://reproducible-builds.org/tools/)
     ** update to be non-debian-specific links
 * documented known issues, bugs, etc. (currently very debian, plans to generalize for cross-distro)
-    * https://anonscm.debian.org/cgit/reproducible/notes.git/
+    * [https://anonscm.debian.org/cgit/reproducible/notes.git](https://anonscm.debian.org/cgit/reproducible/notes.git)
 
 
 # I'm interested in creating a build farm that tests the reproducibility of my distribution/project - FAQ
 * how to best run the tests (parallelized?)
-  * example of some imperfect helper scripts https://github.com/bmwiedemann/reproducibleopensuse
+  * example of some imperfect helper scripts [https://github.com/bmwiedemann/reproducibleopensuse](https://github.com/bmwiedemann/reproducibleopensuse)
 * where to report results, in what format?
 * how frequent should tests be?
 * Which parts of the build environment should be varied between builds?
@@ -160,6 +161,6 @@ set up website mirror on github:
  * create account on github for automatic pushes from alioth
  * setup post-receive hook to push to github mirror
    * include username/password of auto-push account
- * push to https://github.com/reproducible-builds/website
- * https://www.chiliproject.org/projects/chiliproject/wiki/howto_mirror_your_git_repository_on_github
+ * push to [https://github.com/reproducible-builds/website](https://github.com/reproducible-builds/website)
+ * [https://www.chiliproject.org/projects/chiliproject/wiki/howto_mirror_your_git_repository_on_github](https://www.chiliproject.org/projects/chiliproject/wiki/howto_mirror_your_git_repository_on_github)
 
diff --git a/_events/berlin2016/RPM.md b/_events/berlin2016/RPM.md
index 505530f..8f23c8e 100644
--- a/_events/berlin2016/RPM.md
+++ b/_events/berlin2016/RPM.md
@@ -7,7 +7,7 @@ permalink: /events/berlin2016/RPM/
 ---
 
 ### brainstorming notes:
-- Open build service ( http://openbuildservice.org/ ) that runs various configuration for RPM. Vary environment / ... easy.
+- Open build service ( [http://openbuildservice.org/](http://openbuildservice.org/) ) that runs various configuration for RPM. Vary environment / ... easy.
 - Build service sign the binaries that get published to the mirror infrastructure
 - Discussion point: signatures, you can copy signatures to on the newly built package to obtain the same package.
 - OpenSUSE might still have MD5 in some places, Fedora has switched to SHA-256.
diff --git a/_events/berlin2016/RPMII.md b/_events/berlin2016/RPMII.md
index c540d34..893977d 100644
--- a/_events/berlin2016/RPMII.md
+++ b/_events/berlin2016/RPMII.md
@@ -38,7 +38,7 @@ for var in LANG LC_ALL SOURCE_DATE_EPOCH ; do
   eval value=\$$var
   [ -n "$value" ] && echo " $var=\"$value\""
 done
-# whitelist in dpkg: https://anonscm.debian.org/git/dpkg/dpkg.git/tree/scripts/Dpkg/Build/Info.pm#n50
+# whitelist in dpkg: [https://anonscm.debian.org/git/dpkg/dpkg.git/tree/scripts/Dpkg/Build/Info.pm#n50](https://anonscm.debian.org/git/dpkg/dpkg.git/tree/scripts/Dpkg/Build/Info.pm#n50)
 
 function getos
 {
@@ -67,10 +67,11 @@ Architecture: $(rpm -q --queryformat '%{arch}' -p "$srcrpm")
 </pre>
 
 ### other:
+[https://anonscm.debian.org/git/dpkg/dpkg.git/tree/scripts/Dpkg/Checksums.pm](https://anonscm.debian.org/git/dpkg/dpkg.git/tree/scripts/Dpkg/Checksums.pm)
+
 <pre>
 Checksum-*: ... sha256sum $rpm $specfile $srcrpm # and rpm size # omit MD5+SHA1 because nobody should use that anymore
 size=$(stat -c '%s' $rpm)
-# https://anonscm.debian.org/git/dpkg/dpkg.git/tree/scripts/Dpkg/Checksums.pm
 
 Build-Path: $(rpm --eval '%{_builddir}')
 </pre>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git