Your message dated Mon, 9 Jan 2017 14:20:49 +0100
with message-id <[email protected]>
and subject line Re: [buildd-tools-devel] Bug#761435: schroot: Nothing is
mounted inside the chroot
has caused the Debian Bug report #761435,
regarding schroot: Nothing is mounted inside the chroot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
761435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761435
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: schroot
Version: 1.6.10-1+b1
Severity: important
Dear Maintainer,
I don't use schroot very often, and I recently noticed that when I use
it, the inner system is missing all its mounts. In particular, there is
nothing mounted on /proc or /dev/pts, but there is a private /tmp/ that
is persistent even after schroot exits.
Upgrading to the version in experimental does NOT help.
I do use systemd, and I don't think I've successfully used schroot since
I switched.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages schroot depends on:
ii libboost-filesystem1.55.0 1.55.0+dfsg-2
ii libboost-iostreams1.55.0 1.55.0+dfsg-2
ii libboost-program-options1.55.0 1.55.0+dfsg-2
ii libboost-regex1.55.0 1.55.0+dfsg-2
ii libboost-system1.55.0 1.55.0+dfsg-2
ii libc6 2.19-10
ii libgcc1 1:4.9.1-12
ii libpam0g 1.1.8-3.1
ii libstdc++6 4.9.1-12
ii libuuid1 2.20.1-5.8
ii schroot-common 1.6.10-1
schroot recommends no packages.
Versions of packages schroot suggests:
pn aufs-modules | unionfs-modules <none>
pn btrfs-tools <none>
ii debootstrap 1.0.61
ii lvm2 2.02.109-1
ii qemu-user-static 2.1+dfsg-4
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Sun, 15 Nov 2015, Sebastian Schmidt wrote:
> There is no type= setting, so it defaults to “plain”:
> | type=type
> | The type of the chroot. Valid types are ‘plain’, ‘directory’,
> | ‘file’, ‘loopback’, ‘block-device’, ‘btrfs-snapshot’ and ‘lvm-snapshot’.
> | If empty or omitted, the default type is ‘plain’. Note that ‘plain’
> | chroots do not run setup scripts and mount filesystems; ‘directory’ is
> | recommended for normal use (see “Plain and directory chroots”, below).
>
> Setting type=directory should fix your problem.
Closing the bug since it was a user mistake.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--- End Message ---
