On Sun, Jul 24, 2011 at 12:03:59AM +0200, Aurelien Jarno wrote: > > > > It at least does the right thing on the i386 buildds. Maybe the > > chroot was older? > > > > It's what I thought first, but the script [1] doesn't seems to do that, > or at least I fail to see where. > > [1] https://buildd.debian.org/docs/create-chroot.sh
/usr/sbin/sbuild-createchroot has: my ($personality, $personality_message); # Detect whether personality might be needed. if ($conf->get('ARCH') ne $conf->get('HOST_ARCH')) { # Take care of the known case(s). if ($conf->get('ARCH') eq 'i386' && $conf->get('HOST_ARCH') eq 'amd64') { $personality='linux32'; $personality_message = "I: Added personality=$personality automatically (i386 on amd64).\n"; } else { $personality_message = "W: The selected architecture and the current architecture do not match\n" . "W: (" . $conf->get('ARCH') . " versus " . $conf->get('HOST_ARCH') . ").\n" . "I: You probably need to add a personality option (see schroot(1)).\n" . "I: You may want to report your use case to the sbuild developers so that\n" . "I: the appropriate option gets automatically added in the future.\n\n"; } } Kurt _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers