Hi, I'm kind of new in artix,
I was wondering if that was normal to have some /run/systemd repository in my system ? or other systemd file
Are there supposed to be there ? or are there a sign of failure from my part in order to make my system work properly ?
Thanks for any answers ;)
Wouldn't/Shouldn't cause any issue, probably some package created that
/run/systemd is created by elogind. It is normal. There may be some systemd service files that sneak in packages (as part of upstream). We try our best to remove these, but they're harmless. They just do nothing since well you can't launch a systemd service without systemd. :P
Thanks for the answers,
What is the process I should have when founding a package that have file related to systemd which cause issues ?
For example podman have errors trying to write in /run/systemd/journal/socket, what is the process in order to contribute or point some packages issue in the artix community ? :)
We don't really have a formal process but it sounds like its worth importing podman and disabling systemd in the build since it's trying to use journald.
Podman has been imported and from example I found it seems to work now without mentioning journald. After mirror syncs you can pacman -Sy galaxy/podman