Bug#728500: apt-get fails: mkstemp (2: No such file or directory)

[Christian Meyer <c2h5oh@web.de>]

Am Samstag, den 02.11.2013, 01:11 +0100 schrieb David Kalnischkies:
> On Sat, Nov 2, 2013 at 12:00 AM, Christian Meyer <c2h5oh@web.de> wrote:
> > I debootstraped jessie in an stable LVM cryptsetup environment.
> > Afterwards I did some configuation, chrooted in the new system and did an
> >
> > I understood the error this way:
> > gpgv is installed and I found that mkstemp is not installed.(It is found in
> > gnulib and not in coreutils like mktemp)
> 
> That has nothing to do with a binary called mkstemp, it is referring to the
> libc method mkstemp (man 3 mkstemp   # if you have manpages-dev installed).
> [Ignore the message about gpgv, that is just a follow-up error]
> 
> The method is supposed to create and open a temporary file and based
> on the error message from the method, it sounds like it can't open the
> created temp file.
> 
> I and many others do chroots quite often, so I wonder what is so special
> about your setup, that it doesn't work for you as it does here.
> Have you done anything extraordinary to /tmp in your chroot?
> Are other applications acting strange as well?

Thanks for your explanation.
I'm not very familiar in setting up a new system vith debootstrap and chrooting in it.
So obviously I did something wrong. Here is what I did exactly:

	/usr/sbin/debootstrap --arch amd64 jessie /testing ftp://ftp.de.debian.org/debian/
		-> I: Base system installed successfully.

	mount -o bind /dev /testing/dev
	mount -o bind /dev/pts /testing/dev/pts
	mount -t sysfs sys /testing/sys
	mount -t proc proc /testing/proc
	cp /proc/mounts /testing/etc/mtab

	LANG=de chroot /testing /bin/bash

	configuring some files like hostname, fstab, resolv.conf, sources.list, ...

	mount -a
	apt-get update
		-> error

I didn't test any other application since this is only a young and very
minimal system, even without a kernel. a root password or any users. I
wanted to extend it by installing some packages first.


Now I tested /tmp in the chroot environment:

I can 'touch' a file in it and 'rm' it afterwards.

# ls -l / | grep tmp
drwxrwxrwt   2 root root    4096 Nov  2 07:51 tmp

# ls -a /tmp
.  ..

# mount | grep /tmp
#


I have no glue what could be extraordinary there. Please let me know when I did something wrong or if I can test something different.

Christian Meyer