MySQL-libs conflicts with mariadb-libs-5.5.29-7.fc19.x86_64
Rex Dieter
rdieter at math.unl.edu
Sun Mar 10 23:30:34 UTC 2013
alekcejk at googlemail.com wrote:
> Last KDE nightly composes failed because of 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
>
> 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.
In addition to there not being any MySQL bugzilla component,
1. Shouldn't the 'mysql' component be retired and blocked now?
2. Should the "best practice" be to use
Requires: mariadb, BuildRequires: mariadb-devel
instead of
Requires: mysql, BuildRequires: mysql-devel
now?
3. And long-term, what to do about MySQL-libs getting pulled into live
image composes? can it be blacklisted or something?
-- rex
More information about the devel
mailing list