[buildd-tools-devel] Bug#634287: sbuild-update --arch=i386 -ud sid fails for i386 chroot on amd64 host

[Johannes Schauer]

Control: tag -1 + unreproducible moreinfo

Hi,

On Mon, 18 Jul 2011 15:15:25 +0200 Marc Haber <mh+debian-bugs at zugschlus.de> wrote:
> 14:40 <Zugschlus> I am trying to create an i386 sbuild chroot on an amd64 system
> 14:40 <Zugschlus> sudo sbuild-createchroot --arch=i386 sid
>                   /var/lib/sbuild/images/sid-i386 http://mirror.local/debian
> 14:40 <Zugschlus> => fine
> 14:40 <rleigh> OK.
> 14:40 <Zugschlus> sudo sbuild-update --arch=i386 -ud sid-i386
> 14:40 <Zugschlus> Chroot sid-i386 for architecture i386 not found
> 14:40 <Zugschlus> and this confuses me
> 14:41 <Zugschlus> strangely, it works without --arch=i386
> 14:42 <rleigh> I think this is because sbuild-update looks for a chroot named
>                $dist-$arch-sbuild, and this would be sid-i386-sbuild, but the
>                "sid-i386" as the distribution makes it looks for
>                "sid-i386-i386-sbuild".  Does it also work if you just use "sid"
>                and keep with --arch=i386?
> 14:42 <Zugschlus> no
> 14:42 <Zugschlus> sudo sbuild-update --arch=i386 -ud sid
> 14:42 <Zugschlus> Chroot sid for architecture i386 not found
> 14:43 <Zugschlus> I have a file /etc/schroot/chroot.d/sid-i386-sbuild-K8H9Ap
>                   defining a chroot named sid-i386-sbuild
> [sid-i386-sbuild]
> type=directory
> description=Debian sid/i386 autobuilder
> directory=/var/lib/sbuild/images/sid-i386
> groups=root,sbuild
> root-groups=root,sbuild
> script-config=sbuild/config
> personality=linux32
> 
> 14:44 <rleigh> That sounds OK.
> 14:44 <rleigh> If you run sbuild-update with --debug, it should list in there
>                all the chroots it find, and the one it wants.  I'm afraid it's
>                very verbose, but it might help.  I'll be happy to have a look
>                through.
> 14:45 <rleigh> It's possibly an issue with sbuild-update; the cross-building
>                stuff is not as widely tested as for normal building.
> 14:47 <rleigh> Hmm, that is really odd.  It's definitely finding it and
>                settting it, but then not using it.
> 14:47 <rleigh> Which sbuild version is this?
> 14:48 <Zugschlus> 0.62.5-1
> 14:48 <Zugschlus> the chroot is a directory chroot, I forgot to reserve LVM
>                   space for chroot LVs
> 14:49 <rleigh> A directory chroot should still update just fine.  I use them
>                all the time.
> 14:50 <rleigh> I have seen this before with using an sbuild version without
>                support for schroot namespaces (chroot:xxx), but since you're
>                running the latest version this isn't an issue.
> 14:50 <Zugschlus> ii  schroot         1.4.23-1        Execute commands in a
>                   chroot environment
> 14:50 <Zugschlus> just to be complete
> 14:51 <Zugschlus> is the odd suffix to the /etc/schroot/chroot.d file intended,
>                   or was there a rename supposed to happen?
> 14:52 <rleigh> The suffix can be safely removed.  It's there just so that we
>                don't accidentally overwrite any existing schroot configuration
>                if you create more than one chroot with the same distribution
>                name.
> 14:53 <Zugschlus> I see. That got me confused

sbuild is now being used for cross-building and this is handling foreign
architecture chroots just fine for me.

Can you confirm that this bug has been fixed in the meanwhile?

I'd like to close it then.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20151224/637d2a41/attachment.sig>