Here's another patch that resets what should be used as the default chroot name. I don't think it's necessary to change the chroot name based off of if a directory or file type chroot is made.
This patch should be applied after the other patches are applied. -- Regards, Andres
From 7ea3e8f7abb4b33dc70bccc9417b6f5bf8cb2168 Mon Sep 17 00:00:00 2001 From: Andres Mejia <[email protected]> Date: Sat, 12 Sep 2009 15:49:19 -0400 Subject: [PATCH] Reset chroot name writtin for chroot config back to suite-arch-sbuild. --- bin/sbuild-createchroot | 7 +------ 1 files changed, 1 insertions(+), 6 deletions(-) diff --git a/bin/sbuild-createchroot b/bin/sbuild-createchroot index 75b82fa..c428828 100755 --- a/bin/sbuild-createchroot +++ b/bin/sbuild-createchroot @@ -256,12 +256,7 @@ dump_file("${target}/etc/apt/sources.list"); print "I: Please add any additional APT sources to ${target}/etc/apt/sources.list\n"; # Write out schroot chroot configuration. -my $chrootname; -if ($conf->get('MAKE_TARBALL')) { - $chrootname = "${suite}-" . $conf->get('ARCH') . "-file-sbuild"; -} else { - $chrootname = "${suite}-" . $conf->get('ARCH') . "-directory-sbuild"; -} +my $chrootname = "${suite}-" . $conf->get('ARCH') . "-sbuild"; # Determine the schroot chroot configuration to use. my $config_entry; -- 1.6.3.3
