> I seem to be unable to reproduce it with 1.0.60~bpo70+1 but I can with
> 1.0.48+deb7u1; I didn't spot anything obvious from a very quick look,
> but I'll try to track this down a bit later (probably after the release
> sprint).
This bug actually is a duplicate of #702861 which was fixed in 1.0.5
> And are you running systemd?
Oh I forgot to mention: the host used to build the chroots is plain
wheezy, not running systemd:
# dpkg -l | grep systemd
ii libsystemd-login0:amd64 44-11+deb7u4 amd64 systemd login utility library
# aptitude why libsystemd-login0
i rhythmbox Depends dbus
i A dbu
> Also, Daniel, did you try to bootstrap wheezy or sid? And are you running
> systemd?
Like I saide: of wheezy/jessie only wheezy is affected. The commands I
ran are
# debootstrap wheezy /tmp/wheezy http://ftp.de.debian.org/debian
and
# debootstrap jessie /tmp/jessie http://ftp.de.debian.org/d
Hi Bastian,
is there anything I can do in the meantime to mitigate this, apart from
running `service mountdevsubfs.sh start` manually after e.g.
xen-create-image (which invokes deboostrap)?
Daniel
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe".
Package: debootstrap
Version: 1.0.48+deb7u1
Severity: critical
Justification: breaks unrelated software
Hi,
after running debootstrap the host's /run/shm tmpfs mount gets unmounted. Since
the mount point /run/shm itself is set to root:root/750, this breaks any other
package which relies on being
5 matches
Mail list logo
