Skip to content
GitLab
Commits (9)
Expand all Hide whitespace changes
Inline Side-by-side
_docs/source-date-epoch.md
View file @ aa0c8587
......@@ -4,7 +4,7 @@ layout: docs
permalink: /docs/source-date-epoch/
---
`SOURCE_DATE_EPOCH` (or `S_D_E`) [is a standardised environment variable](https://reproducible-builds.org/specs/source-date-epoch/) that distributions can set centrally and have build tools consume this in order to produce reproducible output.
`SOURCE_DATE_EPOCH` [is a standardised environment variable](https://reproducible-builds.org/specs/source-date-epoch/) that distributions can set centrally and have build tools consume this in order to produce reproducible output.
Before implementing this, you should scan through [our checklist](https://wiki.debian.org/ReproducibleBuilds/StandardEnvironmentVariables#Checklist) to see if you can avoid implementing it.
......@@ -16,7 +16,7 @@ Please read our [SOURCE_DATE_EPOCH specification](https://reproducible-builds.or
See [Standard Environment Variables](https://wiki.debian.org/ReproducibleBuilds/StandardEnvironmentVariables) for more detailed discussion of the rationales behind this mechanism.
Below we also have [[#More_detailed_discussion|more detailed discussion]] about this specific variable, as well as documentation on [[#history-and-alternatives|history and alternative proposals]].
Below we also have more detailed discussion about this specific variable, as well as documentation on history and alternative proposals.
## Setting the variable
......@@ -337,7 +337,7 @@ NOTE: faketime BREAKS builds on some archs, for example hurd. See #778462 for de
Sometimes developers of build tools do not want to support `SOURCE_DATE_EPOCH`, or they will tweak the suggestion to something related but different. We really do think the best approach is to use `SOURCE_DATE_EPOCH` exactly as-is described above in our proposal, without any variation. Here we explain our reasoning versus the arguments we have encountered.
(See [[ReproducibleBuilds/StandardEnvironmentVariables#more-detailed-discussion|Standard Environment Variables]] for general arguments.)
(See *Standard Environment Variables* for general arguments.)
### "Lying about the time" / "violates language spec"
......
_reports/2019-04.md
View file @ aa0c8587
......@@ -7,7 +7,7 @@ draft: false
published: 2019-05-05 17:08:27
---
**Welcome to the April 2019 report from the [Reproducible Builds](https://reproducible-builds.org) project!** In these now-monthly reports we will outline the most important things which have been up to in and around the world of reproducible builds & secure toolchains.
**Welcome to the April 2019 report from the [Reproducible Builds](https://reproducible-builds.org) project!** In these now-monthly reports we will outline the most important things which we have been up to in and around the world of reproducible builds & secure toolchains.
[![]({{ "/images/reports/2019-04/reproducible-builds.png#right" | prepend: site.baseurl }})](https://reproducible-builds.org/)
......
_reports/2019-05.md
View file @ aa0c8587
......@@ -9,7 +9,7 @@ published: 2019-06-06 12:50:39
[![]({{ "/images/reports/2019-05/reproducible-builds.png#right" | prepend: site.baseurl }})](https://reproducible-builds.org/)
**Welcome to the May 2019 report from the [Reproducible Builds](https://reproducible-builds.org) project!** In our reports we outline the most important things which have been up to in and around the world of reproducible builds & secure toolchains over the past month.
**Welcome to the May 2019 report from the [Reproducible Builds](https://reproducible-builds.org) project!** In our reports we outline the most important things which we have been up to in and around the world of reproducible builds & secure toolchains over the past month.
As a quick recap, whilst anyone can inspect the source code of free software for malicious flaws, almost all software is distributed to end users pre-compiled. The motivation behind reproducible builds effort is to ensure no malicious flaws have been introduced during this compilation process by promising identical results are always generated from a given source, thus allowing third-parties to come to a consensus on whether a build was compromised.
......@@ -192,7 +192,7 @@ Mattia Rizzolo [[...](https://salsa.debian.org/qa/jenkins.debian.net/commit/dd86
Chris Lamb added various fixes for larger/smaller screens [[...](https://salsa.debian.org/reproducible-builds/reproducible-website.git/commit/edef6f8)], added a logo suitable for printing physical pin badges [[...](https://salsa.debian.org/reproducible-builds/reproducible-website.git/commit/d78fd45)] and refreshed the opening copy text on our [`SOURCE_DATE_EPOCH`](https://reproducible-builds.org/docs/source-date-epoch) page.
Bernhard M. Wiedemann then [documented a more concise C code example](https://reproducible-builds.org/docs/source-date-epoch/#c) for parsing the `SOURCE_DATE_EPOCH` environment variable [[...](https://salsa.debian.org/reproducible-builds/reproducible-website/commit/547732f)][[...](https://salsa.debian.org/reproducible-builds/reproducible-website/commit/e1efd6f)] and Holger Levsen added a [link to a specific bug](https://bugzilla.opensuse.org/show_bug.cgi?id=1133809) blocking progress in [openSUSE](https://opensuse.org/) to our [*Who is involved?*](https://reproducible-builds.org/who/) page [[...](https://salsa.debian.org/reproducible-builds/reproducible-website/commit/d9f4bce)].
Bernhard M. Wiedemann then [documented a more concise C code example](https://reproducible-builds.org/docs/source-date-epoch/#c) for parsing the `SOURCE_DATE_EPOCH` environment variable [[...](https://salsa.debian.org/reproducible-builds/reproducible-website/commit/547732f)][[...](https://salsa.debian.org/reproducible-builds/reproducible-website/commit/e1efd6f)] and Holger Levsen added a [link to a specific bug](https://bugzilla.opensuse.org/show_bug.cgi?id=1133809) blocking progress in [openSUSE](https://opensuse.org/) to our [*Who is involved?*]({{ "/who/" | prepend: site.baseurl }}) page [[...](https://salsa.debian.org/reproducible-builds/reproducible-website/commit/d9f4bce)].
---
......
_reports/2019-06.md
View file @ aa0c8587
This diff is collapsed.
_reports/2019-07.md
View file @ aa0c8587
---
layout: new/report
layout: report
year: "2019"
month: "07"
month_name: "July"
......
bin/generate-draft
View file @ aa0c8587
......@@ -102,7 +102,7 @@ def get_data(year, month, max_age=3600):
data.update({
'projects': PROJECTS,
'title': month_start.strftime('Reproducible Builds in %B %Y'),
'month_year': month_start.strftime('%B %Y'),
'title_year': '{:04d}'.format(year),
'title_month': '{:02d}'.format(month),
})
......
bin/generate-draft.template
View file @ aa0c8587
......@@ -2,11 +2,11 @@
layout: report
year: "{{ title_year }}"
month: "{{ title_month }}"
title: "{{ title }}"
title: "Reproducible Builds in {{ month_year }}"
draft: true
---
**Welcome to the {{ title_month }} {{ title_year }} report from the [Reproducible Builds](https://reproducible-builds.org) project!** In our reports we outline the most important things which have been up to in and around the world of reproducible builds & secure toolchains over the past month.
**Welcome to the {{ month_year }} report from the [Reproducible Builds](https://reproducible-builds.org) project!** In our reports we outline the most important things which we have been up to in and around the world of reproducible builds & secure toolchains over the past month.
As a quick recap, whilst anyone can inspect the source code of free software for malicious flaws, almost all software is distributed to end users pre-compiled. The motivation behind reproducible builds effort is to ensure no flaws have been introduced during this compilation process by promising identical results are always generated from a given source, thus allowing multiple third-parties to come to a consensus on whether a build was compromised.
......@@ -19,20 +19,28 @@ In this month's report, we will cover:
* **Misc news** — *From our mailing list, etc.*
* **Getting in touch** — *How to contribute, etc*
If you are interested in contributing to our project, please visit our [*Contribute*](https://reproducible-builds.org/contribute/) page on our website.
---
## Media coverage
* FIXME
---
## Upstream news
* {{ packages_stats['added'] }} reviews of Debian packages were added, {{ packages_stats['updated'] }} were updated and {{ packages_stats['removed'] }} were removed this month, adding to [our knowledge about identified issues](https://tests.reproducible-builds.org/debian/index_issues.html). FIXME issue types have been updated: {% for _, xs in issues_yml.items()|sort %}{% for x in xs %}[{{ x['title'] }}](https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/{{ x['sha'] }}), {% endfor %}{% endfor %}
* FIXME
---
### Distribution work
In Debian, ...
* {{ packages_stats['added'] }} reviews of Debian packages were added, {{ packages_stats['updated'] }} were updated and {{ packages_stats['removed'] }} were removed this month, adding to [our knowledge about identified issues](https://tests.reproducible-builds.org/debian/index_issues.html). FIXME issue types have been updated: {% for _, xs in issues_yml.items()|sort %}{% for x in xs %}[{{ x['title'] }}](https://salsa.debian.org/reproducible-builds/reproducible-notes/commit/{{ x['sha'] }}), {% endfor %}{% endfor %}
---
## Software development
......@@ -50,7 +58,7 @@ In addition, build failure bugs were reported by:
* {{ k }} ({{ v|length }}){% endfor %}{% endif %}
{% for project in projects %}
### {{ project }}
#### {{ project }}
{% for x in uploads[project] %}
{{ project }} version `{{ x['version'] }}` was [uploaded to Debian {{ x['distribution'] }}](https://tracker.debian.org/pkg/{{ project }}?FIXME) by {{ x['signed_by_name'] }}. It [included contributions already covered in previous months](https://salsa.debian.org/reproducible-builds/{{ project }}/commits/{% if project != 'diffoscope' %}debian/{% endif %}{{ x['version'] }}) as well as new ones from:
......@@ -62,22 +70,20 @@ In addition, build failure bugs were reported by:
---
## **Misc news** — *From our mailing list, etc.*
## Misc news
* On [our mailing list](https://lists.reproducible-builds.org/pipermail/rb-general/) this month: FIXME
---
## Getting in touch
If you are interested in contributing the Reproducible Builds project, please visit our [Contribute](https://reproducible-builds.org/contribute/) page on our website. However, you can get in touch with us via:
* Mailing list: [`rb-general`](https://lists.reproducible-builds.org/listinfo/rb-general)
If you are interested in contributing the Reproducible Builds project, please visit our [*Contribute*](https://reproducible-builds.org/contribute/) page on our website. However, you can get in touch with us via:
* IRC: `#reproducible-builds` on `irc.oftc.net`.
* Twitter: [@ReproBuilds](https://twitter.com/ReproBuilds)
* Mailing list: [`rb-general@lists.reproducible-builds.org`](https://lists.reproducible-builds.org/listinfo/rb-general)
<br>
---
......
images/reports/2019-06/diffoscope.svg 0 → 100644
View file @ aa0c8587
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
version="1.1"
width="128"
height="128"
id="svg2">
<defs
id="defs4" />
<metadata
id="metadata7">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title></dc:title>
</cc:Work>
</rdf:RDF>
</metadata>
<g
transform="matrix(1.0692573,0,0,1.0692573,-328.34726,-503.5515)"
id="layer1">
<g
id="g5409">
<g
transform="translate(5.418238,0)"
id="g5386">
<rect
width="90.304001"
height="50.999996"
x="316.36414"
y="472.80621"
id="rect4667-3"
style="fill:none;stroke:none" />
<g
id="text4673-8"
style="font-size:64px;font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;text-align:start;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#008000;fill-opacity:1;stroke:none;font-family:Inconsolata;-inkscape-font-specification:Inconsolata Medium">
<path
d="m 316.36413,483.82622 0,3.968 26.304,0 0,-3.968"
id="path5371"
style="fill:#c00000;fill-opacity:1" />
<path
d="m 348.36413,483.82622 0,3.968 26.304,0 0,-3.968"
id="path5373"
style="fill:#c00000;fill-opacity:1" />
<path
d="m 380.36413,483.82622 0,3.968 26.304,0 0,-3.968"
id="path5375"
style="fill:#c00000;fill-opacity:1" />
</g>
<g
id="text5366"
style="font-size:64px;font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;text-align:start;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#008000;fill-opacity:1;stroke:none;font-family:Inconsolata;-inkscape-font-specification:Inconsolata Medium">
<path
d="m 327.69213,496.99019 0,10.88 -11.328,0 0,3.968 11.328,0 0,11.968 4.032,0 0,-11.968 10.944,0 0,-3.968 -10.944,0 0,-10.88 -4.032,0"
id="path5378" />
<path
d="m 359.69213,496.99019 0,10.88 -11.328,0 0,3.968 11.328,0 0,11.968 4.032,0 0,-11.968 10.944,0 0,-3.968 -10.944,0 0,-10.88 -4.032,0"
id="path5380" />
<path
d="m 391.69213,496.99019 0,10.88 -11.328,0 0,3.968 11.328,0 0,11.968 4.032,0 0,-11.968 10.944,0 0,-3.968 -10.944,0 0,-10.88 -4.032,0"
id="path5382" />
</g>
</g>
<use
id="use5399"
x="0"
y="0"
width="744.09448"
height="1052.3622"
xlink:href="#g5386" />
<use
transform="matrix(0.8,0,0,0.8,82.417275,133.65028)"
id="use5401"
style="opacity:0.85"
x="0"
y="0"
width="744.09448"
height="1052.3622"
xlink:href="#g5386" />
<use
transform="matrix(0.6,0,0,0.6,164.83455,260.05454)"
id="use5403"
style="opacity:0.7"
x="0"
y="0"
width="744.09448"
height="1052.3622"
xlink:href="#g5386" />
<use
transform="matrix(0.4,0,0,0.4,247.25182,379.25208)"
id="use5405"
style="opacity:0.55"
x="0"
y="0"
width="744.09448"
height="1052.3622"
xlink:href="#g5386" />
</g>
</g>
</svg>