madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://"]
  insteadOf = madduck:

add readme
authormartin f. krafft <>
Thu, 24 Apr 2008 18:31:15 +0000 (20:31 +0200)
committermartin f. krafft <>
Thu, 24 Apr 2008 18:31:15 +0000 (20:31 +0200)
README [new file with mode: 0644]

diff --git a/README b/README
new file mode 100644 (file)
index 0000000..4d9e40c
--- /dev/null
+++ b/README
@@ -0,0 +1,23 @@
+mbuild README
+The general idea of mbuild is that it's called for new *_source.changes files
+that accompany source-only uploads (dpkg-buildpackage -S). Based on the target
+suite, it then figures out which architectures reprepro wants and which sbuild
+provides (this is to be implemented yet) and fires off sbuild for each.
+When the builds have finished, the source package is handed over to reprepro,
+and then each of the binary changes files in turn.
+Finally, a bundle is built with the binary packages from one arch, and the
+source package, with changes files merged. The idea is that this bundle can
+now be downloaded, inspected, tested, and finally, when it's ready for upload,
+the changes file signed and uploaded.
+Right now, no authentication is done on the signature on the *_source.changes
+file and the *.dsc file, but that could be hacked in with dscverify.
+All this is very hackish and beta; if you want to hack along:
+ -- martin f. krafft <>  Thu, 24 Apr 2008 20:30:51 +0200