Package: debootstrap Version: 1.0.10 Severity: normal On an AMD64 system, it appears to be impossible to use the fakechroot variant to create an i386 chroot.
* It is entirely possible for a user to create an i386 root using fakechroot and debootstrap on an i386 Debian system. * It is also possible for a user to create an AMD64 root using fakechroot and debootstrap on an AMD64 system. * Using Etch on an AMD64 system, it is possible to debootstrap an Etch i386 chroot using fakechroot. * Using Lenny on an AMD64 system, it is NOT possible to debootstrap a Lenny i386 chroot using fakechroot. When attempting to execute the command fakechroot fakeroot debootstrap --arch i386 --variant=fakechroot etch target I receive the message W: Failure trying to run: chroot /path/to/target dpkg --force-depends --install var/cache/apt/archives/base-files_4_i386.deb var/cache/apt/archives/base-passwd_3.5.11_i386.deb The contents of the target's /debootstrap/debootstrap.log are: dpkg: /home/zpalmer/sandbox/ztemp2/test7/lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /usr/lib32/libfakeroot/libfakeroot-sysv.so) This leads me to believe that it either has something to do with the way debootstrap executes the fakechroot variant or something to do with how the fakeroot package is built. Either way, this prevents cross-platform fakechroot debootstraps. I have no workaround at this time other than to create a normal 32-bit chroot on my system using privileges and do the fakechroot from within that. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debootstrap depends on: ii binutils 2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii wget 1.11.4-1 retrieves files from the web debootstrap recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
