Bug#765443: ltsp-server: Unset variables set by libpam-tmpdir in ltsp-chroot?

2014-10-15 Thread Petter Reinholdtsen
Package: ltsp-client-core Version: 5.5.3-1 Severity: normal User: debian-...@lists.debian.org Usertags: debian-edu When using libpam-tmpdir on the LTSP server and then calling 'ltsp-chroot' to do operations in the LTSP chroot, the temp directory variables are inherited and causing 'apt-get

Bug#765443: ltsp-server: Unset variables set by libpam-tmpdir in ltsp-chroot?

2014-10-15 Thread Vagrant Cascadian
On 2014-10-15, Petter Reinholdtsen wrote: When using libpam-tmpdir on the LTSP server and then calling 'ltsp-chroot' to do operations in the LTSP chroot, the temp directory variables are inherited and causing 'apt-get upgrade' (because of postinst scripts using the temp directory variables)

Bug#765443: ltsp-server: Unset variables set by libpam-tmpdir in ltsp-chroot?

2014-10-15 Thread Petter Reinholdtsen
[Vagrant Cascadian] I'm not sure what to make of this one, honestly. I would go with unsetting all of them or checking if they exist in the chroot and unsetting if they don't. I fail to see why it would be that much more code. We are talking about something like this: unset TMPDIR TEMP

Bug#765443: ltsp-server: Unset variables set by libpam-tmpdir in ltsp-chroot?

2014-10-15 Thread Vagrant Cascadian
Control: tags -1 pending fixed-upstream On 2014-10-15, Petter Reinholdtsen wrote: I would go with unsetting all of them or checking if they exist in the chroot and unsetting if they don't. I fail to see why it would be that much more code. We are talking about something like this: unset