Bug 986549

Summary: debuginfo conflict with mysql-debuginfo
Product: [Fedora] Fedora Reporter: Germano Massullo <germano.massullo>
Component: mariadbAssignee: Honza Horak <hhorak>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 19CC: hhorak
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: 2013-07-22 12:03:25 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:
Attachments:
Description Flags
konsole output none

Description Germano Massullo 2013-07-20 13:52:11 UTC
Created attachment 776171 [details]
konsole output

Description of problem:
My machine is a F19 upgraded from F18. The migration from mysql to mariadb left some troubles behind... I was installing debuginfos for an Amarok crash, when I noticed a conflict between mysql-debuginfo and mariadb-debuginfo packages. I solved by removing mysql-debuginfo.
It should be scheduled that the migration to mariadb removes all mysql debuginfos.

Comment 1 Honza Horak 2013-07-22 08:40:16 UTC
Thanks for reporting, but I'm not sure if we can do much about that. It doesn't seem easy to generate the same provides/obsoletes with debuginfo as with other subpackages, if it's possible at all.

What's more, it's probably not what we want -- we don't want to update debuginfo package to mariadb-debuginfo automatically when someone had mysql-debuginfo installed, since debuginfo packages are generally not strictly tied to packages actually installed on the computer.

But even if we wanted, it is probably not worth the trouble.

Comment 2 Germano Massullo 2013-07-22 09:38:53 UTC
Ok, thank you for the explanation

Comment 3 Honza Horak 2013-07-22 12:03:25 UTC
Always welcome. So I'll close this for now as per comment #1, feel free to re-open if necessary.