Hi, This bug is still present and nowadays prevents debootstrap to create an amd64 wheezy chroot on a current amd64 sid, or pbuilder to work with a previously created wheezy base-tgz.
I'm not coder, so maybe this remark will seem obvious to some, but creating an i386 wheezy chroot on a current amd64 sid system works correctly though. I imagine that the difference in architectures forces fakechroot to use the linker (or some other part, I don't quite understand the problem) from the chroot. Can't this behavior be mimicked when the architecture is the same ? Again, I'm no coder, please don't take offense if this is a silly question. As wheezy is now LTS, this bug is quite annoying since it prevents maintainers to use pbuilder to maintain packages for wheezy (I currently have to use a VM). Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature
