[reproducible-website] 01/01: rws3: liberate notes about existing tools
Holger Levsen
holger at layer-acht.org
Sun Dec 17 11:04:32 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 9a4c6933d11b14ba753595efd5299ddedc26c1f1
Author: Holger Levsen <holger at layer-acht.org>
Date: Sun Dec 17 11:04:24 2017 +0000
rws3: liberate notes about existing tools
Signed-off-by: Holger Levsen <holger at layer-acht.org>
---
.../ReproducibleSummitIIIEventDocumentation.md | 248 +--------------------
_events/berlin2017/agenda.md | 14 +-
_events/berlin2017/existingtools.md | 115 ++++++++++
3 files changed, 123 insertions(+), 254 deletions(-)
diff --git a/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md b/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md
index a3f86f5..49935ab 100644
--- a/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md
+++ b/_events/berlin2017/ReproducibleSummitIIIEventDocumentation.md
@@ -17,9 +17,10 @@ Session Notes - Day 1
[Agenda brainstorming]({{ "/events/berlin2017/agendabrainstorming/" | prepend: site.baseurl }})
-::[[#RefHeadingToc4080118152727|Working sessions I]]
+Working sessions I
-:::[[#RefHeadingToc4082118152727|Reviewing existing reproducible builds tools]]
+[Agenda brainstorming]({{ "/events/berlin2017/agendabrainstorming/" | prepend: site.baseurl }})
+[Reviewing existing reproducible builds tools]({{ "/events/berlin2017/existingtools/" | prepend: site.baseurl }})
:::[[#RefHeadingToc4084118152727|Discussing the current status of .buildinfo files]]
@@ -94,246 +95,9 @@ Session Notes - Day 1
[Brainstorming the reproducible builds logo design]({{ "/events/berlin2017/logodesign/" | prepend: site.baseurl }})
-= {{anchor|RefHeadingToc57621733262122}} Session Notes =
-
-
-
-== {{anchor|RefHeadingToc21601733262122}} Day 1 ==
-
-
-=== {{anchor|RefHeadingToc4080118152727}} Working sessions I ===
-
-
-
-==== {{anchor|RefHeadingToc4082118152727}} Reviewing existing reproducible builds tools ====
-
-
-
-diffoscope
-
-<nowiki>----------</nowiki>
-
-
-- diff two artefacts and check if they are the same.
-
-- if not, it will open artefact and will try to find out what's wrong.
-
-- it does this recursetly
-
-- e.g. a zip file, will be open and it will identify which file within
-
-the archive is different.
-
-- e.g. a elf file will be opened and the section is being identified.
-
-
-stripnondeterminism
-
-<nowiki>-------------------</nowiki>
-
-
-- runs after the build
-
-- remove known causes of non-reproducible
-
-- e.g. jar's aren't reproducible and make it reproducible
-
-- remove several timestamp
-
-- should not exist by designed
-
-- but upstream is hard or take a lot of time. it's an intermediate
-
-solution
-
-
-disorderfs
-
-<nowiki>----------</nowiki>
-
-
-- fuse filesystem
-
-- has different modes
-
-- e.g. random
-
-- ls -f / `can return every time a difference`
-
-- e.g. invert
-
-- invert the listing
-
-- e.g. order
-
-- will order mode
-
-Good practices:
-
-- runs once in "order" mode
-
-- runs second in invert mode to have a deterministic non-deterministic
-
-way.
-
-
-trydiffoscope.org
-
-<nowiki>-----------------</nowiki>
-
-
-- web service
-
-- you don't have to install diffoscope with the lots of dependencies
-
-- written in django
-
-- cmdline client to avoid main diffoscope install
-
-- upload
-
-- diff on the server
-
-- create a link to be shared into the bug report
-
-
-reprotest
-
-<nowiki>---------</nowiki>
-
-
-- tool to run the a build run twice
-
-- can use container
-
-- reprotest `make` will run it twice. but changing the environemnt like
-
-TZ
-
-
-tests.reproducible-builds.org
-
-<nowiki>-----------------------------</nowiki>
-
-
-- based jenkins
-
-- doesn't run reprotest
-
-- is running bunch of scripts to do the build twice
-
-- is legacy, but moving to reprotest, isn't going to happen,
-
-as long reprotest is still under development
-
-
-squashfs-tools
-
-<nowiki>--------------</nowiki>
-
-
-- the
-
-- upstream is not reproducible
-
-- lots of distribution patches
-
-- unclear if the reproducible patches gonna accepted
-
-- lynxis will do a fork because the maintainer isn't
-
-- not reproducible becaues of timestamps and scheduling problems
-
-
-guix
-
-<nowiki>-----</nowiki>
-
-
-- packages manager guarantees reproducibility
-
-- guix challenge compares difference sources of a binary
-
-
-reproducibleopensuse
-
-<nowiki>--------------------</nowiki>
-
-
-can test a packages which has been uploaded to opensuse build system.
-
-varies:
-
-- hostname
-
-- date
-
-
-tool request
-
-<nowiki>------------</nowiki>
-
-
-- to make javascript reproducible, there should be a `npm-ls`
-
-to get all the npm packages.
-
-
-- someone created a cross-ecosystem scraper to scrape npm, pypi
-
-- prevent build systems to talk to the internet
-
-- run a tcpdump on the system. if the .pcap file is greater than 0, you
-
-know the build talked to the internet. It helps create a good bug
-
-report to know, to which server it talks and what.
-
-
-Put the "is the build talking to the internet" feature into the build
-
-system.
-
-- call `runc` without network
-
-- create a namespace without network
-
-
-
-
-Feedback results to the community
-
-
-reproshilds.io??
-
-<nowiki>--------------</nowiki>
-
-
-- travis-ci integration
-
-- create a tool to integrate it into their build process
-
-- create a feedback api.
-
-- get badges
-
-
-The unreproducible packages
-
-<nowiki>--------------------------</nowiki>
-
-
-have a package full of non-reproducible things
-
-
-next sessions
-
-<nowiki>------------</nowiki>
-
-
-- squashfs forking session
-
-- reprotest
+= Session Notes =
+== Day 1 ==
+=== Working sessions I ===
==== {{anchor|RefHeadingToc4084118152727}} Discussing the current status of .buildinfo files ====
diff --git a/_events/berlin2017/agenda.md b/_events/berlin2017/agenda.md
index e9c406f..b4105a9 100644
--- a/_events/berlin2017/agenda.md
+++ b/_events/berlin2017/agenda.md
@@ -9,38 +9,28 @@ permalink: /events/berlin2017/agenda/
= Agenda =
-
-
Day 1 – Tuesday, October 31
-
9:45 Opening session (No notes taken in this session)
The Summit started with participant introductions, a welcome message from the event co-organizers, and an overview of the meeting agenda.
-
10:10 Sharing knowledge about reproducible builds (No notes taken in this session)
Participants gathered in small groups. The talking points suggested for their discussion were:* If you attended one or both of the two previous Summits, which were your experience and takeaways?
* Ask Me Anything: Ask any question you have about repoducible builds
* How do you think reproducible builds are already working well today, and where do you see that there is still work to be done?
-
-
-
-
11:00 Break
-
11:15 [Agenda brainstorming]({{ "/events/berlin2017/agendabrainstorming/" | prepend: site.baseurl }})
Participants generated a list of topics and questions that they wanted to discuss at the meeting. The result of the brainstorming was then taken into account to identify the working sessions that had emerged as the most compelling for those in attendance.
-
12:45 Lunch
-
-13:45 Working sessions I (Session notes start on page 17)* Reviewing existing reproducible builds tools – Chris
+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
* What is the ecosystem around rpm? – Bernhard
* End user tools: What does exist, what is still needed – dkg
diff --git a/_events/berlin2017/existingtools.md b/_events/berlin2017/existingtools.md
new file mode 100644
index 0000000..886d642
--- /dev/null
+++ b/_events/berlin2017/existingtools.md
@@ -0,0 +1,115 @@
+---
+layout: event_detail
+title: Reviewing existing reproducible builds tools
+event: berlin2017
+order: 30
+permalink: /events/berlin2017/existingtools/
+---
+
+diffoscope
+----------
+
+- diff two artefacts and check if they are the same.
+- if not, it will open artefact and will try to find out what's wrong.
+- it does this recursetly
+- e.g. a zip file, will be open and it will identify which file within the archive is different.
+- e.g. a elf file will be opened and the section is being identified.
+
+stripnondeterminism
+-------------------
+
+- runs after the build
+- remove known causes of non-reproducible
+- e.g. jar's aren't reproducible and make it reproducible
+- remove several timestamp
+- should not exist by designed
+- but upstream is hard or take a lot of time. it's an intermediate solution
+
+disorderfs
+----------
+
+- fuse filesystem
+- has different modes
+- e.g. random
+- ls -f / `can return every time a difference`
+- e.g. invert
+- invert the listing
+- e.g. order
+- will order mode
+
+Good practices:
+- runs once in "order" mode
+- runs second in invert mode to have a deterministic non-deterministic way.
+
+trydiffoscope.org
+-----------------
+
+- web service
+- you don't have to install diffoscope with the lots of dependencies
+- written in django
+- cmdline client to avoid main diffoscope install
+- upload
+- diff on the server
+- create a link to be shared into the bug report
+
+reprotest
+---------
+- tool to run the a build run twice
+- can use container
+- reprotest `make` will run it twice. but changing the environemnt like TZ
+
+tests.reproducible-builds.org
+-----------------------------
+- based jenkins
+- doesn't run reprotest
+- is running bunch of scripts to do the build twice
+- is legacy, but moving to reprotest, isn't going to happen, as long reprotest is still under development
+
+squashfs-tools
+--------------
+- the upstream is not reproducible
+- lots of distribution patches
+- unclear if the reproducible patches gonna accepted
+- lynxis will do a fork because the maintainer isn't
+- not reproducible becaues of timestamps and scheduling problems
+
+guix
+-----
+- packages manager guarantees reproducibility
+- guix challenge compares difference sources of a binary
+
+reproducibleopensuse
+--------------------
+can test a packages which has been uploaded to opensuse build system.
+varies:
+- hostname
+- date
+
+tool request
+------------
+- to make javascript reproducible, there should be a `npm-ls` to get all the npm packages.
+- someone created a cross-ecosystem scraper to scrape npm, pypi
+- prevent build systems to talk to the internet
+- run a tcpdump on the system. if the .pcap file is greater than 0, you know the build talked to the internet. It helps create a good bug report to know, to which server it talks and what.
+- Put the "is the build talking to the internet" feature into the build system.
+- call `runc` without network
+- create a namespace without network
+
+Feedback results to the community
+
+reproshilds.io??
+--------------
+- travis-ci integration
+- create a tool to integrate it into their build process
+- create a feedback api.
+- get badges
+
+The unreproducible packages
+--------------------------
+have a package full of non-reproducible things
+
+next sessions
+------------
+- squashfs forking session
+- reprotest
+
--
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