670b865cb2
We've received a bug report, that the 'rpm -qc' incorrectly returns the MySQL
server default log file '/var/log/mysql/mysqld.log' as a configuration file.
https://issues.redhat.com/browse/RHEL-57601
This was caused by us packing it in the SPECfile '%files' section with the
'%config %ghost' directives. The reason was historical. We tried to mark
the file as owned by the package, but at the same time to not pack it,
and also prevent its deleteion on package removal.
The correct way is to not list the file at all.
The parent directory is properly packed and owned instead (already), so it should be
clear that the files inside are associated with that package. This is how we already
do it with the DB datadir '/var/lib/mysql'.
Resolves: RHEL-112386
While investigating this issue, we also reviewed the log file creation.
The log file is created automatically by the MySQL server when needed.
This can even happen in the middle of the server runtime, when the file
is (re)moved, and the DB server is tasked to flush the logs.
I checked the MySQL server documentation, and tested it, and I found, that the logfile
is indeed created by the server. The only possible reason why the file might be needed
to be created beforehand, is when the file lies on a location to which the MySQL server
won't have permissions to write to.
This is likely the case of MySQL upstream RPMs, which place it by default to the '/var/log':
|
||
|---|---|---|
| .fmf | ||
| plans | ||
| .gitignore | ||
| boost-1.57.0-mpl-print.patch | ||
| boost-1.58.0-pool.patch | ||
| gating.yaml | ||
| my.cnf.in | ||
| mysql8.4.rpmlintrc | ||
| mysql8.4.spec | ||
| mysql_config_multilib.sh | ||
| mysql-check-socket.sh | ||
| mysql-file-contents.patch | ||
| mysql-flush-logrotate.patch | ||
| mysql-install-test.patch | ||
| mysql-paths.patch | ||
| mysql-prepare-db-dir.sh | ||
| mysql-rpath.patch | ||
| mysql-scripts-common.sh | ||
| mysql-scripts.patch | ||
| mysql-sharedir.patch | ||
| mysql-wait-stop.sh | ||
| mysql.service.in | ||
| mysql.tmpfiles.d.in | ||
| mysql@.service.in | ||
| README.mysql-docs | ||
| README.mysql-license | ||
| rh-skipped-tests-list-arm.list | ||
| rh-skipped-tests-list-base.list | ||
| rh-skipped-tests-list-ppc.list | ||
| rh-skipped-tests-list-s390.list | ||
| rpminspect.yaml | ||
| server.cnf.in | ||
| sources | ||
MySQL is distributed under GPL v2, but there are some licensing exceptions that allow the client libraries to be linked with a non-GPL application, so long as the application is under a license approved by Oracle. For details see 'The Universal FOSS Exception, Version 1.0': https://oss.oracle.com/licenses/universal-foss-exception/ A predecessor of that license exception is now deprecated 'FOSS License Exception': http://www.mysql.com/about/legal/licensing/foss-exception/ Some innobase code from Percona and Google is under BSD license. Some code related to test-suite is under LGPLv2.