[blog] 01/01: Rework buildinfo.debian.net paragraph.

Chris Lamb chris at chris-lamb.co.uk
Mon Oct 24 21:21:32 UTC 2016


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

lamby pushed a commit to branch master
in repository blog.

commit a3b10be3760de41d5da155f2ba27bdf06e16723d
Author: Chris Lamb <lamby at debian.org>
Date:   Mon Oct 24 22:13:35 2016 +0100

    Rework buildinfo.debian.net paragraph.
---
 posts/78.mdwn | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/posts/78.mdwn b/posts/78.mdwn
index edd5283..358b768 100644
--- a/posts/78.mdwn
+++ b/posts/78.mdwn
@@ -18,9 +18,11 @@ Upcoming events
 buildinfo.debian.net
 --------------------
 
-To enable everyone to rebuild everything reproducibly, we have the concept of ``.buildinfo`` files which generally describe the environment used for a particular build; the inputs and the outputs and, in the Debian case, are available per per package/architecture/version tuple. We anticipate the next ``dpkg`` upload to sid will create such ``.buildinfo`` files by default  and while it's clear that we need to teach dak to deal with them (see [[!bug 763822]]), it's not actually clear how t [...]
+In order to build packages reproducibly, you not only need identical sources but also some external definition of the environment used for a particular build. This definition includes the inputs and the outputs and, in the Debian case, are available in a ``$package_$architecture_$version.buildinfo`` file.
 
-To this end, Chris Lamb has started development on an [highly proof-of-concept ``.buildinfo`` server](http://buildinfo.debian.net/) licensed under the GNU AGPLv3. [Source](https://github.com/lamby/buildinfo.debian.net)
+We anticipate the next ``dpkg`` upload to sid will create ``.buildinfo`` files by default. Whilst it's clear that we also need to teach dak to deal with them ([[!bug 763822]]) its not actually clear how to handle ``.buildinfo`` files after ``dak`` has processed them and how to make them available to the world.
+
+To this end, Chris Lamb has started development on a [proof-of-concept ``.buildinfo`` server](http://buildinfo.debian.net/) to see what issues arise. [Source](https://github.com/lamby/buildinfo.debian.net)
 
 
 Reproducible work in other projects

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



More information about the Reproducible-commits mailing list