I tried to compile a new rc via
s6-rc-compile (or rather wanted
sh -x /usr/share/libalpm/scripts/s6-rc-db-update-hook to do this for me), but it complains:
root@artix # s6-rc-compile $(mktemp -d) /etc/s6/sv
s6-rc-compile: fatal: unable to read /etc/s6/sv/event/type: No such file or directory
The upstream manual (http://skarnet.org/software/s6-rc/s6-rc-compile.html) unmistakably demands
Now the directories
/etc/s6/sv/event/ and
/etc/s6/sv/supervise/ don't have
type files, and this defeats
s6-rc-compile, which is a bummer.
What is wrong here?
What are you trying to accomplish here exactly? Every directory in the source (/etc/s6/sv) must follow the source format. So yeah if they don't have the appropriate type file, s6-rc-compile will fail. I don't know why you have directories named /etc/s6/sv/event and /etc/s6/sv/supervise in there but they didn't come from any s6 script or s6 package.
I'm following your advice at https://forum.artixlinux.org/index.php/topic,1108.msg9419.html#msg9419 to make NFS _netdev mounts wait on connman at boot-up. It is a quite young, largely vanilla Artix-s6 with a few GUI packages. pacman -Qo doesn't blame any packages to own those directories.
I just revised my shell history and found that I played around with s6-supervise (https://skarnet.org/software/s6/s6-supervise.html), which creates directories named that way. Directly in the sv tree and not in a service directory.
I removed the directories and s6-rc-compile went through. Thanks anyway, issue solved. It's a bit misleading that s6-supervise doesn't remove its helper directory even if called wrongly, but that's a cosmetic issue, close to RTFM.