Control: reassign -1 libpam-tmpdir On Fri, Mar 03, 2017 at 04:17:50PM +0100, Johannes Schauer wrote: > On Wed, 1 Mar 2017 01:28:53 +0100 Julian Andres Klode <j...@debian.org> wrote: > > On Wed, Mar 01, 2017 at 01:21:22AM +0100, Julian Andres Klode wrote: > > > Fails with a lot of errors for Debian chroots, but it works perfectly fine > > > with Ubuntu ones. Not sure what's going wrong here. I think this has been > > > going on for months, but I often forget about it because I don't do much > > > binary building anymore (mostly just letting CI pass & upload source these > > > days). > > > > It's libpam-tmpdir that's breaking this somehow - no idea how, but removing > > libpam-tmpdir from my system allows it to work again. > > I tried to reproduce the problem. After having installed libpam-tmpdir I get > the same errors as you do, so success! > > But now I wonder how to fix the problem. It seems that the package sets $TMP > and $TMPDIR to /tmp/user/1000 for me. I guess the last bit is my user id. But > then it fails to create that last component of that directory. This is why > dpkg-deb in your log is unable to create a temporary directory. The path that > $TMP and $TMPDIR are set to simply doesn't exist. At least on my system.
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. Chris
