Settled on IRC: This needs "profile=sbuild" in the chroot.d/*
configuration, then schroot will use the sbuild/fstab instead of the
default/fstab. Then I get:
E: 10mount: E: Failed to resolve path “/var/lib/schroot/mount/sid-
amd64-3471b9f9-d710-47ea-b735-029f4b1c1315/dev/shm”: Not a directory
But this isn't quite the fault of systemd -- if your schroot has a
broken dev/shm then /dev/ or /dev/shm/ won't be a directory to mount on.
If you additionally bind-mount /dev, it works fine:
/dev /dev none rw,bind 0 0
tmpfs /dev/shm tmpfs defaults 0 0
Or change your schroot to have a /dev/shm/ directory. It seems mk-sbuild
by default creates them like that:
$ ls -ld /home/martin-scratch/schroot/sid-amd64/dev/shm
lrwxrwxrwx 1 root root 8 Mai 7 2013
/home/martin-scratch/schroot/sid-amd64/dev/shm -> /run/shm
Thus it can't mount something onto a symlink.
** Changed in: schroot (Ubuntu)
Status: Incomplete => Invalid
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320534
Title:
sbuild fails under systemd-boot with /dev/shm tmpfs mount
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1320534/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
