Bug 7051

Summary:	rpmlint: Don't allow /var/run/* in Mageia Cauldron / 3+
Product:	Infrastructure	Reporter:	Olav Vitters <olav>
Component:	BuildSystem	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	REOPENED ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, ngompa13, sysadmin-bugs
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Olav Vitters 2012-08-14 10:53:17 CEST

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.

Comment 1 Colin Guthrie 2012-08-14 11:04:50 CEST

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).

Comment 2 Rémi Verschelde 2015-09-10 15:00:03 CEST

Colin, is it still on your mental todo list or has it been implemented already? :)

Comment 3 Neal Gompa 2017-09-05 16:13:00 CEST

This is already in rpmlint-1.10.

CC: (none) => ngompa13
Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 4 Olav Vitters 2017-09-05 21:32:29 CEST

This has not been fixed. The bug is for the build infrastructure, I see an upload to Cauldron.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 5 Neal Gompa 2017-09-05 21:44:14 CEST

Oops, sorry, you're right. :)