Hi, Quoting Geert Stappers (2016-05-17 20:57:30) > It would be nice that manual page get a testdrive example
I still don't fully understand what you find lacking, but would the following
section in the sbuild man page fix this bug:
EXAMPLES
Before you use sbuild for the first time, you have to do some setup de‐
pending on the chroot backend you are using. The default backend is sch‐
root. To use sbuild with the schroot backend, you need to add your user
to the sbuild group and create a schroot chroot. The latter can be ac‐
complished by using sbuild-createchroot(8). If the chroot contains a De‐
bian derivative with apt (<< 0.8.16~exp3), or a Debian release before
Wheezy, then it is also required to create gpg key pairs using sbuild-
update --keygen. After this one time setup, you can now use sbuild to
build packages like this:
% sbuild -d unstable bash
Or on a .dsc:
% sbuild -d unstable bash.dsc
Or from within an unpacked source package (the -d parameter is not nec‐
essary here because the distribution is inferred from debian/copyright):
% sbuild
Thanks!
cheers, josch
signature.asc
Description: signature
