Bug 1125434

Summary:	mariadb update attempts to install /etc/my.cnf with "placeholders" intact
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	mariadb	Assignee:	Honza Horak <hhorak>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	hhorak, jdornak, yaneti
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-21 22:20:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2014-07-31 20:03:42 UTC

Description of problem:

A new /etc/my.cnf file which comes with the latest update contains entries like:

log-error=@LOG_LOCATION_COMPAT@
pid-file=@PID_FILE_DIR_COMAPT@/@DAEMON_NAME_COMPAT@.pid
!includedir @sysconfdir@/my.cnf.d

It does not look like that this is going to fly.  On an update, fortunately, this show up in /etc/my.cnf.rpmnew and an old configuration file has corresponding entries which look saner.

Version-Release number of selected component (if applicable):
mariadb-10.0.12-5.fc22

Comment 1 Honza Horak 2014-08-04 10:41:14 UTC

Thanks for reporting, we'll fix this asap.

Comment 2 Michal Jaegermann 2014-08-21 22:20:27 UTC

AFAICS this is fixed and only a status of this report is not updated.