With the /usr move, /var/run is now a tmpfs filesystem. Anything created on this should be done using systemd-tmpfiles. Various packages still expect /var/run to be a normal filesystem. Thus if a service needs a directory in /var/run, it won't start. It would be good to just prevent /var/run in any package, forcing the packager to create a tmpfiles.d entry. This would've avoided bug 7047 and probably other bugs.
Yup, this has been on my mental todo list for a while. Also, /var/lock in addition to /var/run. I'd also like to ensure packages do not install files in /etc/systemd (with the exception of the systemd package itself to create the basic heirarchy). This is an administrator space and packages should use /usr/lib/systemd tree instead. Ditto for tmpfiles.d and udev rules. They should NOT be in /etc/ when packaged. /etc/ is admin space! Ditto for anything in /run (nothing should be doing this but may as well be safe).
Colin, is it still on your mental todo list or has it been implemented already? :)
This is already in rpmlint-1.10.
CC: (none) => ngompa13Resolution: (none) => FIXEDStatus: NEW => RESOLVED
This has not been fixed. The bug is for the build infrastructure, I see an upload to Cauldron.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Oops, sorry, you're right. :)