On 01/14/2018 10:20 AM, Baptiste Jonglez wrote: > Hi, > > Today I am experiencing build failures of several packages when using the > devtools: > > $ extra-x86_64-build -- -I ../../another-package/trunk/foo.pkg.tar.xz > (...) > ==> Making package: ring-gnome 3:20180112.2.d0bda53-1 (Sun Jan 14 > 16:06:22 CET 2018) > ==> Retrieving sources... > -> Updating ring-client-gnome git repo... > Fetching origin > ==> Validating source files with sha256sums... > ring-client-gnome ... Skipped > Failed to attach 9683 to compat systemd cgroup > /user.slice/user-1000.slice/session-c1.scope/payload: No such file or > directory > Failed to attach 9661 to compat systemd cgroup > /user.slice/user-1000.slice/session-c1.scope/supervisor: No such file or > directory > Failed to chown() cgroup > /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c1.scope/payload: > No such file or directory > Parent died too early > ==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/zorun/build > > Full log : https://paste.aliens-lyon.fr/gD0 > > This is the ring-gnome package in [community] but I had this issue with > another one. It's not 100% reproducible, but when it happens, all > subsequent builds of the same package exhibit the issue. > > My system is fully up-to-date, with kernel 4.14.13-1-ARCH and systemd > 236.0-3. It looks like a bug in systemd, or in the interaction with the > devtools. This may be caused by the systemd update a few days ago. > > Any idea? > Baptiste
Try logging out and in again, and you should be able to use nspawn again once your user session is using the updated systemd version. -- Eli Schwartz Bug Wrangler and Trusted User
signature.asc
Description: OpenPGP digital signature
