[Git][reproducible-builds/reproducible-website][scm.uri] 4 commits: fix typos in Paris report

Arnout Engelen gitlab at salsa.debian.org
Sun Feb 17 17:00:01 CET 2019


Arnout Engelen pushed to branch scm.uri at Reproducible Builds / reproducible-website


Commits:
909cd60d by Jelle van der Waa at 2019-02-17T11:17:45Z
fix typos in Paris report

- - - - -
5e13fd3d by Arnout Engelen at 2019-02-17T15:59:59Z
Clarify source.scm.uri is the developerConnection

- - - - -
3e9361cd by Arnout Engelen at 2019-02-17T15:59:59Z
clarify source.scm.uri is not necessarily a url

- - - - -
82b0f9e7 by Arnout Engelen at 2019-02-17T15:59:59Z
Leave it up to the impl to choose which scm uri to use

- - - - -


2 changed files:

- _docs/jvm.md
- _events/paris2018/report.md


Changes:

=====================================
_docs/jvm.md
=====================================
@@ -38,8 +38,8 @@ version=<version as in pom.xml>
 # source information, as source tarball artifact in repository and/or url and/or scm coordinates
 source.artifact=<groupId>:<artifactId>:<version>:<classifier>:<extension>
 source.url=<url where to download official source tarball>
-source.scm.uri=<source control management url as in pom.xml>
-source.scm.tag=<source control management tag as in pom.xml>
+source.scm.uri=<source control uri, typically corresponding to the project.scm.developerConnection or project.scm.connection in the pom.xml>
+source.scm.tag=<source control tag as in pom.xml>
 
 # build instructions
 build-tool=<mvn|sbt|...>


=====================================
_events/paris2018/report.md
=====================================
@@ -753,7 +753,7 @@ Sources
 
 Trust & Delivery
 
--   What constitutes a proff of reproducibility?
+-   What constitutes a proof of reproducibility?
 
 -   How do we distinguish or attest that an artifact was built on
     trusted hardware or in a trusted environment?
@@ -1490,7 +1490,7 @@ Hash of package? buildinfo?
 
 Not all projects have buildinfo files
 
-Are .buildinfo files without binary checksums useless? (Archlinux has
+Are .buildinfo files without binary checksums useless? (Arch Linux has
 those)
 
 Is it enough / useful if rebuilders publish a stripped down version of
@@ -2046,7 +2046,7 @@ become a problem
 <a name="Toc11382_331763073"></a>
 #### Cross distribution participation
 
-representatives from Archlinux, openSUSE, Guix, Nix, Alpine Linux,
+representatives from Arch Linux, openSUSE, Guix, Nix, Alpine Linux,
 Debian
 
 "package finder tool\" interface for searching infomation about



View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/compare/d8bf4e03b917d60f3ca251388ba092a345976f83...82b0f9e7b7c607b88b7ad7b6c65a4a9891779e2b

-- 
View it on GitLab: https://salsa.debian.org/reproducible-builds/reproducible-website/compare/d8bf4e03b917d60f3ca251388ba092a345976f83...82b0f9e7b7c607b88b7ad7b6c65a4a9891779e2b
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/20190217/9efed94a/attachment.html>


More information about the rb-commits mailing list