wanna-build-mail(1) wanna-build mail interface


wanna-build-mail package
wanna-build-catgdbm package
wanna-build-catmldbm package


This man page documents the packaged version of wanna-build. This version is maintained by the buildd-tools project developers on Alioth (https://alioth.debian.org/projects/buildd-tools/).

There is also a version maintained by Ryan Murray which is adapted to build daemon needs, with similar functionality. This version should be equally capable of working in a buildd setup, but has a number of enhancements aimed at making it suitable for use by end-users.


wanna-build-mail is used to drive wanna-build though an email interface. Set up wanna-build-mail as the mail filter for the wanna-build user on your system, then when you send this user mail, wanna-build-mail will run to process the mail and query the database with the commands you specify in the mail.

The mail processor sends a reply mail with all the program output to the address the request came from (From: header). Alternatively, it obeys a Reply-To: header if present.


The email subject does not matter. The body must be signed with PGP, with a key registered in /var/lib/wanna-build/mail-keyring.pgp. Only these keys are authorised to use the mail interface. Additionally, the file mail-users in the same directory is used to map PGP-key names to user names.

In the body (the PGP-signed part), you can write commands like:

wanna-build hello_1.0-1
uploaded tst1_1.0 tst2_0.99a
info hello
list needs-build failed


The commands below are available. All be be abbreviated to their first letter and must start in column 0. An argument package_version is the package name and its version number, as usual with wanna-build.
wanna-build package_version
uploaded-build package_version
failed-build package_version
The failed-build command also needs a failing message. You put this message in the lines after the command, each line with some whitespace at the start. This whitespace is stripped for the message actually passed to failed-build. The first line without whitespace is treated as the next command.
infopackage1 [ package2 [ packagen]]
Get package information. No version number is required.
list state1 [ state2 [ staten]]
List packages in given states. Valid states are installed, needs-build, building, uploaded, failed, not-for-us, and additionally all (for any state).
vlist state1 [ state2 [ staten]]
vlist is the same as list, but includes a -v option, so that previous states and old failing messages are printed, too.


Database files.
PGP keys of users authorised to use the mail interface.
Mapping between PGP keys and system usernames.


Roman Hodek <[email protected]>, Ryan Murray <rmu[email protected]>, and Roger Leigh <[email protected]>.