Harald Dunkel dixit: > Logfile is attached. If I kick out libpam-tmpdir there is no such > problem. But this would be very painful. Do you think pbuilder could > create the missing directory tree in /tmp instead?
This seems to be bogus. Packages cannot rely on specific per-system configuration, such as trees below /tmp, or $HOME, during build, so I’d say something is done wrong here, and I very much doubt it is in pbuilder. What’s going on here, anyway? • pam doesn’t run in chroots, or does it? • libpam-tmpdir seems to have an RC bug (uninstallability) caused by it not creating the needed parent directories itself? • why is libpam-tmpdir in a --variant=buildd chroot, anyway? • or do you just fail to unset $TMPDIR before calling pbuilder? Hah! You may be running into the latter. I strongly recommend to use a wrapper around cowbuilder/pbuilder invocations; see specifically https://github.com/mirabilos/shellsnippets/blob/ab3ffb3714d8600c98d23102ed65a7d08383c11e/mksh/debian-dev/c#L127 and also https://github.com/mirabilos/shellsnippets/blob/ab3ffb3714d8600c98d23102ed65a7d08383c11e/mksh/debian-dev/c#L35 which apparently became necessary at some point as well. Please try: sudo env --unset=XDG_RUNTIME_DIR --unset=TMPDIR DIST=sid ARCH=amd64 EXTRAPACKAGES="ca-certificates" pbuilder create (Your command, with env(1) intermediate added. Just “sudo foo=bar” is not reliable/portable anyway.) Does this fix your issue, when used ceteris paribus? bye, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
