Bug 1177836

Summary:	MariaDB 5.5.40 update breaks a number of packages including MySQL-python
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Kurik <jkurik>
Component:	mariadb	Assignee:	Honza Horak <hhorak>
Status:	CLOSED ERRATA	QA Contact:	Branislav Blaškovič <bblaskov>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	7.1	CC:	bblaskov, blc, cstpierr, databases-maint, fkrska, hannsj_uhl, hartsjc, hhorak, jkurik, jscotka, jsvarova, ksrot, lpol, mattias.ellert, ohudlick, ovasik, pasik, perobins, pm-eus, psklenar, rbu, sauchter, spamfaenger, volker27
Target Milestone:	rc	Keywords:	EasyFix, Patch, Regression, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://mariadb.atlassian.net/browse/MDEV-6862
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Due to an incorrect check for the build environment in the MariaDB header file, packages that require the mariadb-devel packages for building failed to build with an error massage. This update fixes the check for the build environment in the mysql.h file, so that the check is applied only when expected. As a result, software that requires mariadb-devel now builds successfully.	Story Points:	---
Clone Of:	1166603	Environment:
Last Closed:	2015-01-05 13:46:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1166603, 1188317
Bug Blocks:

Description Jan Kurik 2014-12-30 19:01:45 UTC

This bug has been copied from bug #1166603 and has been proposed
to be backported to 7.0 z-stream (EUS).

Comment 6 Honza Horak 2015-01-01 21:02:17 UTC

How to test:
1. #> yum-builddep MySQL-python-1.2.3-11.el7.src.rpm
2. $> rpmbuild --rebuild MySQL-python-1.2.3-11.el7.src.rpm

Comment 8 Branislav Blaškovič 2015-01-05 06:22:25 UTC

Verified according to comment 7.

Comment 11 errata-xmlrpc 2015-01-05 13:46:20 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-0007.html