Feature: Include warning in files put in /usr/lib/tmpfiles.d/
Reason: To inform users to create a file (with same name) in /etc/tmpfiles.d/ when they want to customize anything in that file because that file could be overwritten with the next package update
This is what tmpfiles.d(5) man page says about tmpfiles.d files:
Files in /etc/tmpfiles.d override files with the same name in /usr/lib/tmpfiles.d and /run/tmpfiles.d. Files in /run/tmpfiles.d override files with the same name in /usr/lib/tmpfiles.d. Packages should install their configuration files in /usr/lib/tmpfiles.d. Files in /etc/tmpfiles.d are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied, all all other conflicting entries will be logged as errors. When two lines are prefix and suffix of each other, then the prefix is always processed first, the suffix later. Otherwise, the files/directories are processed in the order they are listed.
(In reply to Honza Horak from comment #2)
> This is what tmpfiles.d(5) man page says about tmpfiles.d files:
Which means correct way to change /usr/lib/tmpfiles.d/mariadb.conf is actually creating /etc/tmpfiles.d/mariadb.conf.
If there are no objections, I'd close this as NOTABUG.
For the record, this is a public bug with multiple private comments. The public comments don't reflect it, but the private discussion has turned to adding a warning to the /usr/lib/tmpfiles.d/mariadb.conf file (provided by mariadb-server rpm).
This has purportedly already been added to the mariadb-server rpm in Fedora, though it must be rawhide or something because I don't see it on my Fedora 22.
I've tagged this as GSS-Proposed for RHEL 7.3.
The comment is even in F22 branch but the package was not rebuilt just for this change:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.