On Tue, May 17, 2016 at 11:07:22PM +0200, Johannes Schauer wrote: > Quoting Geert Stappers (2016-05-17 21:20:25) > > On Tue, May 17, 2016 at 08:57:30PM +0200, Geert Stappers wrote: > > > > > > 5. Finished > > > The user should now be able to run sbuild. > > > > > > $ sbuild ... > > > > > > > > > It would be nice that manual page get a testdrive example > > > > > > > It is about knowing that a fresh sbuild setup works. > > I do not understand yet what exactly this bug is asking for. Could you > elaborate a bit more? >
Short: What should go on the dots of '> > > $ sbuild ...' Long: Being new to sbuild is some what frightening. All the actions involved for setup of sbuild, result only in having sbuild setup. Next is using sbuild. From the manual page: SYNOPSIS sbuild [-h|--help | -V|--version] [-v|--verbose | -q|--quiet] [-D|--debug] [-A|--arch-all] [--archive=archive] [-d|--dist=distribution] [-c|--chroot=chroot] [--arch=archi- tecture] [--build=architecture] [--host=architecture] [--pro- files=profile[,...]] [-s|--source] [--force-orig-source] [--make-binNMU=changelog-entry] [--binNMU=NMU-version] [--append-to-version=string] [--add-depends=dependency] [--add-conflicts=dependency] [--add-depends-arch=dependency] [--add-conflicts-arch=dependency] [--add-depends-indep=depen- dency] [--add-conflicts-indep=dependency] [-m|--main- tainer=maintainer] [-e|--uploader=uploader] [-k|--keyid=key- id] [-j|--jobs=n] [--debbuildopt=option] [--debbuil- dopts=options] [--dpkg-source-opt=options] [--dpkg-source- opts=options] [-p|--purge=purge-mode] [--purge-build=purge- mode] [--purge-deps=purge-mode] [--purge-session=purge-mode] [-b|--batch] [-n|--nolog] [--run-lintian] [--no-run-lintian] [--lintian-opt=options] [--lintian-opts=options] [--run-piu- parts] [--no-run-piuparts] [--piuparts-opt=options] [--piu- parts-opts=options] [--piuparts-root-arg=options] [--piu- parts-root-args=options] [--pre-build-commands=string] [--chroot-setup-commands=string] [--starting-build-com- mands=string] [--finished-build-commands=string] [--chroot-cleanup-commands=string] [--post-build-com- mands=string] [--log-external-command-output] [--log-exter- nal-command-error] [--setup-hook=hook-script] [--build-dep-resolver=resolver] [--resolve-alterna- tives|--no-resolve-alternatives] [--extra-package=pack- age.deb] [--extra-repository=spec] [PACKAGE[.dsc]] Which looks scary. Doing cd ~/src debcheckout sbuild cd sbuild sbuild results in tail: cannot open '/home/stappers/src/sbuild/debian/changelog' for reading: No such file or directory dpkg-parsechangelog: error: tail of /home/stappers/src/sbuild/debian/changelog gave error exit status 1 E: Could not parse /home/stappers/src/sbuild/debian/changelog Cause is having No debian directory after `debcheckout` Doing cd ~/src debcheckout postfix cd postfix sbuild results in test -f debian/rules dh_clean build test ! -d debian/postfix || rm -rf debian/postfix /usr/bin/make tidy make[1]: Entering directory '/home/stappers/src/postfix' /usr/bin/make -f Makefile.in MAKELEVEL= Makefiles make: Entering directory '/home/stappers/src/postfix' (echo "# Do not edit -- this file documents how Postfix was built for your machine."; /bin/sh makedefs) >makedefs.tmp No <db.h> include file found. Install the appropriate db*-devel package first. See the RELEASE_NOTES file for more information. Makefile.in:22: recipe for target 'Makefiles' failed make: *** [Makefiles] Error 1 make: Leaving directory '/home/stappers/src/postfix' Makefile:21: recipe for target 'Makefiles' failed make[1]: *** [Makefiles] Error 2 make[1]: Leaving directory '/home/stappers/src/postfix' debian/rules:208: recipe for target 'clean-preunpatch' failed make: *** [clean-preunpatch] Error 2 E: Failed to clean source directory /home/stappers/src/postfix (/home/stappers/src/postfix_2.8.5-2.dsc) Is that a FTBFS or me not being able to use sbuild? Documenting how to testdrive a sbuild setup, will answer that question. thanks Groeten Geert Stappers -- Leven en laten leven
signature.asc
Description: Digital signature