[Reproducible-commits] [blog] 01/01: Publish reprotest week 6 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 0abc1603f1a37cd4de33e6529b2ad77f571cc0f9
Author: Ceridwen <ceridwenv at gmail.com>
Date:   Fri Jul 8 10:05:09 2016 -0400

    Publish reprotest week 6 report
---
 {drafts => posts}/people/ceridwen/reprotest_week6.mdwn | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/drafts/people/ceridwen/reprotest_week6.mdwn b/posts/people/ceridwen/reprotest_week6.mdwn
similarity index 90%
rename from drafts/people/ceridwen/reprotest_week6.mdwn
rename to posts/people/ceridwen/reprotest_week6.mdwn
index 4aec6d5..5c98c3b 100644
--- a/drafts/people/ceridwen/reprotest_week6.mdwn
+++ b/posts/people/ceridwen/reprotest_week6.mdwn
@@ -1,11 +1,11 @@
 [[!meta title="Managing container and environment state"]]
-[[!meta date=""]]
+[[!meta date="Fri, 08 Jul 2016 09:58:01 -0400"]]
 [[!tag reproducible_builds Debian reprotest Outreachy]]
 Author: ceridwen
 
 With some more help from Martin Pitt, it became clear to me that my
-mental model of how autopkgtest works is very different from how it
-does work.  I'll illustrate by borrowing my [previous
+previous mental model of how autopkgtest worked is very different from
+how it does work.  I'll illustrate by borrowing my [previous
 example](https://reproducible.alioth.debian.org/blog/posts/people/ceridwen/reprotest_week5/).
 I know that schroot has the following behavior:
 
@@ -84,3 +84,10 @@ to me, and I think I can use it to avoid writing my own shell AST
 library.  It has a
 [method](https://plumbum.readthedocs.io/en/latest/api/commands.html#plumbum.commands.base.BaseCommand.formulate)
 that converts the Python representation of a shell script into a string that can be passed to `Testbed.command()`.  Integrating Plumbum to generate the necessary scripts is where I'm going in the next week.
+
+Any feedback on any of this is welcome.  I'm also curious what other
+projects are using autopkgtest code.  [Holger](http://layer-acht.org/)
+brought to my attention
+[piuparts](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815084),
+which brings the list up to four that I'm aware of, autopkgtest
+itself, sbuild, piuparts, and now reprotest.
\ No newline at end of file

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