I was wondering if you could take a look at #773765 and provide your input on it. Basically, if you create a new pbuilder chroot and then try to use it to build libxshmfence, it's failing because it doesn't have a working shm filesystem in the chroot. The cause is that the chroot gets systemd installed instead of sysvinit, and the systemd package doesn't include any /run/shm directory (or symlink). So, when pbuilder tries to mount a tmpfs on <chroot>/run/shm that fails.
The pbuilder maintainers are saying this is a bug in systemd, as the /run release goal says the system should have /run/shm with /dev/shm being a compatibility/ABI symlink to it. -- Daniel Schepler
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
