reassign 856434 sbuild
thanks

]] Chris Hofstaedtler 

> On Sun, Dec 01, 2024 at 04:10:00PM +0100, Tollef Fog Heen wrote:
> > 
> > > 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?
> 
> So, the non-sbuild context was this:
> https://github.com/grml/grml-debootstrap/issues/232

Thank you.  It's a very similar context – chroot-ing and needing to take
action for TMP to be valid.

> > 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.
> 
> Well, maybe all tools need to be prepared that TMP/TMPDIR point to
> something that will not exist and thus need to filter them out
> immediately.
> 
> If that is true, then please feel free to reassign to sbuild.

Something calling chroot and running commands has to do one of:

- unset TMP and TMPDIR (so things fall back to /tmp, which hopefully
  exists).

- ensure TMP and TMPDIR exists in the chroot.

- ensure libpam-tmpdir is installed and configured in the chroot, and
  open a new PAM session there when chroot-ing (so the PAM session hooks
  run). (This will ensure that TMP/TMPDIR is set appropriately and
  exists.)

Otherwise, TMP/TMPDIR might not exist, and tools generally rely on that
existing and being read- and writeable.

I have no opinion on which one of those is right for sbuild.  I'll
reassign the bug back to sbuild, since it sounds like the adjustment
needs to happen there.  Happy to help or advise further if that's
helpful, please cc me in that case.

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Reply via email to