[reproducible-website] 01/01: rws3: liberate notes about .buildinfo files

Holger Levsen holger at layer-acht.org
Mon Dec 18 09:32:30 UTC 2017


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

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

commit dcc36bd446b47df232c97231b0546d00098c8bcf
Author: Holger Levsen <holger at layer-acht.org>
Date:   Mon Dec 18 09:32:15 2017 +0000

    rws3: liberate notes about .buildinfo files
    
    Signed-off-by: Holger Levsen <holger at layer-acht.org>
---
 .../ReproducibleSummitIIIEventDocumentation.md     | 50 ----------------------
 _events/berlin2017/agenda.md                       |  7 ++-
 _events/berlin2017/statusbuildinfofiles.md         | 34 +++++++++++++++
 3 files changed, 37 insertions(+), 54 deletions(-)

diff --git a/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md b/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md
index 49935ab..f255d0d 100644
--- a/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md
+++ b/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md
@@ -100,56 +100,6 @@ Working sessions I
 === Working sessions I ===
 
 
-==== {{anchor|RefHeadingToc4084118152727}} Discussing the current status of .buildinfo files ====
-
-
-
-build info craziness
-
-
-- Limitations Debian implem of build info
-
-+ no checksum of dependencies in build info, deb limitation: #802241 (debian bug) 
-
-+ no checksum of the source code. 
-
-+ no architecture of the installed dependencies (e.g arm installed on x86_64, cross-compilation, multi arch binaries, ...)
-
-- no actual specification of build info, only a man page of the debian implementation
-
-+ other implementation: archlinux, OBS (open build service -- openSUSE). Need to follow-up on openSUSE buildenv.
-
-+ man pages missing some information
-
-+ Lot of things called build info but not necessary build info.
-
-- what is debian specific in build info?
-
-+ None of the field is debian specific
-
-+ But format might be
-
-- do we want to have a single format for all distribution?
-
-+ Not essential...
-
-+ But ease the adoption of repro build: easier to compare, easier to share tooling, ...
-
-+ Maybe they want to use something that feel native to them
-
-
-- Build info specification on the debian wiki 
-
-+ Do we need to have a repro-build level specification? (in https://reproducible-build.org/specs)
-
-
-We narrowly avoided an argument about csh
-
-
-- Build info file for ISO distribution, what format would that be? 
-
-+ A separate topic that other people might want to discuss? Not a topic for us now.
-
 ==== {{anchor|RefHeadingToc4086118152727}} What is the ecosystem around rpm? ====
 
 
diff --git a/_events/berlin2017/agenda.md b/_events/berlin2017/agenda.md
index b4105a9..f037de7 100644
--- a/_events/berlin2017/agenda.md
+++ b/_events/berlin2017/agenda.md
@@ -7,8 +7,6 @@ permalink: /events/berlin2017/agenda/
 ---
 
 
-= Agenda =
-
 Day 1 – Tuesday, October 31
 
 9:45 Opening session (No notes taken in this session)
@@ -30,8 +28,9 @@ Participants generated a list of topics and questions that they wanted to discus
 12:45 Lunch
 
 13:45 Working sessions I
-*[Reviewing existing reproducible builds tools]({{ "/events/berlin2017/existingtools/" | prepend: site.baseurl }}) – Chris
-* Discussing the current status of .buildinfo files – Mattia
+
+* [Reviewing existing reproducible builds tools]({{ "/events/berlin2017/existingtools/" | prepend: site.baseurl }}) – Chris
+* [Discussing the current status of .buildinfo files]({{ "/events/berlin2017/statusbuildinfofiles/" | prepend: site.baseurl }}) – Mattia
 * What is the ecosystem around rpm? – Bernhard
 * End user tools: What does exist, what is still needed – dkg
 
diff --git a/_events/berlin2017/statusbuildinfofiles.md b/_events/berlin2017/statusbuildinfofiles.md
new file mode 100644
index 0000000..0398a63
--- /dev/null
+++ b/_events/berlin2017/statusbuildinfofiles.md
@@ -0,0 +1,34 @@
+---
+layout: event_detail
+title: Discussing the current status of .buildinfo files
+event: berlin2017
+order: 40
+permalink: /events/berlin2017/statusbuildinfofiles/
+---
+
+build info craziness
+--------------------
+
+- Limitations Debian implem of build info
++ no checksum of dependencies in build info, deb limitation: #802241 (debian bug) 
++ no checksum of the source code. 
++ no architecture of the installed dependencies (e.g arm installed on x86_64, cross-compilation, multi arch binaries, ...)
+- no actual specification of build info, only a man page of the debian implementation
++ other implementation: archlinux, OBS (open build service -- openSUSE). Need to follow-up on openSUSE buildenv.
++ man pages missing some information
++ Lot of things called build info but not necessary build info.
+- what is debian specific in build info?
++ None of the field is debian specific
++ But format might be
+- do we want to have a single format for all distribution?
++ Not essential...
++ But ease the adoption of repro build: easier to compare, easier to share tooling, ...
++ Maybe they want to use something that feel native to them
+- Build info specification on the debian wiki 
++ Do we need to have a repro-build level specification? (in https://reproducible-build.org/specs)
+
+We narrowly avoided an argument about csh
+
+- Build info file for ISO distribution, what format would that be? 
++ A separate topic that other people might want to discuss? Not a topic for us now.
+

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



More information about the Reproducible-commits mailing list