Comment 3 for bug 392377

Q: Is there any way I can add additional debugging to debootstrap (eg: pausing between installed packages, more verbose output, etc) so I can possibly track down where this is happening? I am aware that this may not even be a problem of debootstrap, but a problem caused by a package in the chroot created by debootstrap interacting with processes outside of the chroot.

As noted above, I am quite willing to do most of the diagnosis to find the crux of the issue.