[Reproducible-commits] [blog] 01/01: Draft of reprotest week 3 report

[Ceridwen]

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

ceridwen-guest pushed a commit to branch master
in repository blog.

commit 9b9bdea7f00ca473a71b8c365f88d5931122f2c6
Author: Ceridwen <ceridwenv at gmail.com>
Date:   Mon Jun 13 23:31:14 2016 -0400

    Draft of reprotest week 3 report
---
 drafts/people/ceridwen/reprotest_week3.mdwn | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/drafts/people/ceridwen/reprotest_week3.mdwn b/drafts/people/ceridwen/reprotest_week3.mdwn
new file mode 100644
index 0000000..3096caa
--- /dev/null
+++ b/drafts/people/ceridwen/reprotest_week3.mdwn
@@ -0,0 +1,28 @@
+[[!meta title="Reprotest has a preliminary CLI and configuration file handling"]]
+[[!meta date="Mon, 13 Jun 2016 18:15:13 -0400"]]
+[[!tag reproducible_builds Debian reprotest Outreachy]]
+Author: ceridwen
+
+The first, very-alpha release of reprotest is now out at TODO.  While
+it only builds on an existing system, it can now check its own
+reproducibility, which it does in its own tests, both using setuptools
+and debuild.  Unfortunately, setuptools seems to generate
+file-order-dependent binaries, meaning setuptools bdist creates
+unreproducible binaries.  With debuild, reprotest probably would be
+reproducible with the [modified
+packages](https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain#Modified_packages)
+from the Reproducible Builds project, though I haven't tested that
+yet.  It tests 'captures_environment', 'fileordering' (renamed from
+'filesystem'), 'home', 'kernel', 'locales', 'path', 'time',
+'timezone', and 'umask'.  The other variations require superuser
+privileges and modifications that would be unsafe to make to a running
+system, so they will only be enabled in the containers.
+
+The next major part of the project is integrating autopkgtests's
+container management system into reprotest.  For the curious,
+autopkgtest is composed of a main program, `adt-run`, which then calls
+other command-line programs, `adt-virt-chroot, `adt-virt-lxd`,
+`adt-virt-schroot`, `adt-virt-null`, `adt-virt-schroot`, and
+`adt-virt-qemu`, that communicate with the containers.  I think this
+is a bit of an odd design but it works well for my purposes since the
+container programs already have existing CLIs that reprotest can use.

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