This is caused by the kill_target being included in the WHAT_TO_DO for --print-debs. When a target is not specified, it is set to the working directory (I guess), and kill_target will indeed wipe it out. Adding kill_target or printdebs to the list at line 251 would fix this, since that would ensure that the user specifies a target whenever debootstrap is going to destroy one.
That would probably break other things -- maybe this will help the maintainer find a solution, though. -- Ryan Schultz "vi users are mammals, and they flip out and kill people *all the time.*" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
