You are not logged in.
I've been building AUR packages in a clean chroot for a long time, but it started to fail recently. So, I deleted the entire chroot directory and tried to make a new one following the wiki: https://wiki.archlinux.org/index.php/De … nience_way
$ mkdir ~/chroot
$ CHROOT=$HOME/chroot
mkarchroot $CHROOT/root base-devel
I'm getting the following error on the last step:
.
.
.
( 6/11) Creating system user accounts...
( 7/11) Creating temporary files...
( 8/11) Reloading device manager configuration...
Skipped: Device manager is not running.
( 9/11) Arming ConditionNeedsUpdate...
(10/11) Updating the info directory file...
(11/11) Rebuilding certificate stores...
Failed to attach 8773 to compat systemd cgroup /user.slice/user-1000.slice/session-1.scope/payload: No such file or directory
Failed to attach 7145 to compat systemd cgroup /user.slice/user-1000.slice/session-1.scope/supervisor: No such file or directory
Failed to chown() cgroup /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-1.scope/payload: No such file or directory
There is a solution mentioned here:
https://bugs.archlinux.org/task/58892#comment174565
Removing "--keep-unit" from /usr/bin/arch-nspawn in combination with chmod a+rwX /var/lib/archbuild/extra-x86_64 made "sudo extra-x86_64-build" work again. (I am not recommending a+rwX on a general basis).
Thanks to sangy for the tip about removing "--keep-unit".
Can anyone explain what is causing the problem and how this solves it?
Last edited by colinkeenan (2018-11-21 19:48:29)
Offline
I don't know, but logging out and logging in again usually fixes it for me. If the problem manifests, I believe it's usually the result of updating systemd and then having a stale logind session slice.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline