Bug 919926

Summary:	MySQL-libs conflicts with mariadb-libs
Product:	[Fedora] Fedora	Reporter:	nucleo <alekcejk>
Component:	mysql	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, h.reindl, kevin, rdieter, tgl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	MySQL-5.5.29-3.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-18 09:42:53 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 nucleo 2013-03-10 23:03:03 UTC

Description of problem:
Last KDE nightly composes failed with error

DEBUG util.py:264:  Error creating Live CD : Failed to build transaction : MySQL-libs conflicts with mariadb-libs-5.5.29-7.fc19.x86_64

http://koji.fedoraproject.org/koji/taskinfo?taskID=5100301
http://koji.fedoraproject.org/koji/taskinfo?taskID=5100302

Version-Release number of selected component (if applicable):
MySQL-5.5.30-2.fc19

Additional info:
Previous composes before importing new MySQL package was fine,
so last composes problem related  with new MySQL.

There is also other problem with missing MySQL component in bugzilla,
looks like for bugzilla MySQL=mysql, it finds mysql bugs 
for MySQL package.

https://admin.fedoraproject.org/pkgdb/acls/bugs/MySQL

Comment 1 Kevin Kofler 2013-03-10 23:13:08 UTC

MySQL-libs really needs to go away.

Comment 2 Harald Reindl 2013-03-10 23:39:37 UTC

if fedora would make clean decisions to "features" and the orcale mysql for F19 would get "mysql-orcale", only contain the server and mariadb provides and obsoltes mysql at all there would be no sible problem at all - proen with my self-made mariadb-packages for F17/F18

but wo cares at fedora-updtream
there are always vague decisions with no straight forwareded migrations 
since years and quality has no real importance because "first is all"

Comment 3 Rex Dieter 2013-03-12 14:20:22 UTC

Still a problem with last night's image compose.  I suspect similar problems are occuring from amarok's use of mysql-embedded.  Please change the soname in 
-embedded
subpkg too

Comment 4 Rex Dieter 2013-03-12 14:21:20 UTC

2nd attempt at reassigning (since MySQL bz component still doesn't exist).

Still a problem with last night's image compose.  I suspect similar problems are occuring from amarok's use of mysql-embedded.  Please change the soname in 
-embedded
subpkg too

Comment 5 Kevin Kofler 2013-03-12 14:44:28 UTC

Uhm, I thought mariadb-embedded already has a different soname? If Amarok is not build against that yet, it needs to be rebuilt.

Comment 6 Rex Dieter 2013-03-12 14:49:38 UTC

that is true, and confirmed that amarok is already using the new one,
libmysqld.so.18
darn, the compose-conflicts problem must be something else then.

Comment 7 Honza Horak 2013-03-12 14:58:19 UTC

I think there is only some delay in repo, since I still see MySQL-5.5.29-2.fc19 in the rawhide repo while the library soname was changed in MySQL-5.5.29-3.fc19.

Comment 8 Honza Horak 2013-03-18 09:42:53 UTC

It seems the live CD creation doesn't fail because of conflicting MySQL-libs any more [1], so I'm closing this bug for now. Feel free to re-open it if you need.

[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=5129361