Martin Michlmayr <[EMAIL PROTECTED]> writes: > You get no error message at all when sbuild cannot find the chroot: > > > 2973:[EMAIL PROTECTED]: ~/build] sbuild -d unstable2 dadadodo_1.04-3 > zsh: exit 2 sbuild -d unstable2 dadadodo_1.04-3 > > 2974:[EMAIL PROTECTED]: ~/build] sbuild -v -d unstable2 dadadodo_1.04-3 > unstable2 chroot does not exist and in chroot only mode -- exiting > zsh: exit 2 sbuild -v -d unstable2 dadadodo_1.04-3
If -v is not specified, there is no logging of any messages at all
(stdout and stderr are both redirected to the build log file very
early on).
It might do to make "-v" the default if not being used in a buildd
situation.
> Also, I think the code to find chroots which don't follow the name of
> an official suite is busted. ~/build/chroot-unstable2 did exist when
> I ran this command. It seems sbuild only accepts
> ~/build/chroot-<official suite name> rather than actually checking for
> ~/build/chroot-<whatever you gave it>.
This is hard-coded in %main::dist_order when using "split"
chroot_mode. If you use schroot, it picks it up automatically from
the list of available chroots.
--
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
pgpqNTUnzq7G9.pgp
Description: PGP signature
