Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Cannot execute yum update after adding Percona respository

Description

Hi, I find that once I stand up a new CentOS 7 instance, then add the Percona repository, doing yum update doesn't work, we see conflicts.  The fix is to remove mariadb-libs.  I think we should have a cleaner way of resolving dependencies right away after adding the repository and trying to update packages

This is the fix:

Environment

None

Smart Checklist

Activity

David Bennett March 10, 2019 at 8:01 AM

This has been addressed by using separate repos for new products. There are work arounds for the older products.

Evgeniy Patlan October 17, 2017 at 5:51 AM

Thanks for the info . I will check this issue from another angle and try to find another solution to fix it now.
As for repo for Percona-Server-80 it is good idea as we should start doing this sometimes.

Vadim Tkachenko October 16, 2017 at 8:24 PM

We are not creating separate repose in the middle of product lifecycle.

But we can consider creating Percona-Server-80 separate repos

David Bennett October 16, 2017 at 2:20 PM
Edited

   

Upstream MySQL has addressed this issue by having separate repos for different versions of products.   For example,  there is a separate repo for MySQL-5.6.-community and MySQL-5.7-community.    What are you thoughts about this possibility?

Evgeniy Patlan October 16, 2017 at 12:53 PM

I have discussed this question with .

This task is much more complicated and need proper investigation.
I will investigate everything and try to find the proper solution

Won't Do

Details

Assignee

Reporter

Components

Priority

Smart Checklist

Created October 12, 2017 at 4:01 PM
Updated March 5, 2024 at 2:34 PM
Resolved March 10, 2019 at 8:01 AM