> I've seen this behaviour in a non-sbuild context too, thus I'm > reassigning this bug to libpam-tmpdir. If it interferes with > TMP/TMPDIR, it ought to make sure the target exists, and does not > pollute any chroot builds etc.
Can you describe exactly what you have seen and steps to reproduce? Does sbuild either clean up TMP and TMPDIR, or make sure those exist when chroot-ing? Otherwise, those directories naturally won't exist inside the chroot, and there's nothing a PAM module that runs at the session start can do about that. I suspect this is an sbuild bug, but I'm not familiar with the internals of it, so it might be somewhere else. Whatever you're seeing I suspect is something else. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
