История изменений

Нет, не поправил. Ты просто добавил переносы вручную. Ну е-мае, это так сложно?

И ты гуглить пробовал? У меня вот это нашлось: https://forums.percona.com/t/bad-yum-dependencies-in-the-percona-repository/7478

This is a quite irritating repo dependency issue and I suggest that it should be fixed by Percona. By default disable the repo at all time as it will break your system yum updates when having mariadb-libs installed and not even have any Percona packages installed. I use Katello and was luckily able to disabled this repo by default in the activation keys section. I have to enable the Percona repo when performing an product upgrade. Still a clumsy workaround.

И вот это:

The problem occurs when having no Percona software installed on systems. I had the Percona repo enabled by default for all systems and when a server has the mariadb-libs installed it breaks the yum update. So I have to permanently disable the Percona to be able to yum update systems.

The same problem is also being described at :

Yum / rpm throwing conflict errors for software not installed - CentOS

I strongly advise to have a second look at the issue.

Thanks,

Laurens

У тебя это самое Percona software стоит на системе или нет? Если нет — выключи его репозиторий совсем, ошибки уйдут.

Проверить можно через

yum list installed | grep -i percona

Нет, не поправил. Ты просто добавил переносы вручную. Ну е-мае, это так сложно?

И ты гуглить пробовал? У меня вот это нашлось: https://forums.percona.com/t/bad-yum-dependencies-in-the-percona-repository/7478

This is a quite irritating repo dependency issue and I suggest that it should be fixed by Percona. By default disable the repo at all time as it will break your system yum updates when having mariadb-libs installed and not even have any Percona packages installed. I use Katello and was luckily able to disabled this repo by default in the activation keys section. I have to enable the Percona repo when performing an product upgrade. Still a clumsy workaround.

И вот это:

The problem occurs when having no Percona software installed on systems. I had the Percona repo enabled by default for all systems and when a server has the mariadb-libs installed it breaks the yum update. So I have to permanently disable the Percona to be able to yum update systems.

The same problem is also being described at :

Yum / rpm throwing conflict errors for software not installed - CentOS

I strongly advise to have a second look at the issue.

Thanks,

Laurens

У тебя это самое Percona software стоит на системе или нет? Если нет — выключи его репозиторий совсем, ошибки уйдут.

Нет, не поправил. Ты просто добавил переносы вручную. Ну е-мае, это так сложно?

И ты гуглить пробовал? У меня вот это нашлось: https://forums.percona.com/t/bad-yum-dependencies-in-the-percona-repository/7478

This is a quite irritating repo dependency issue and I suggest that it should be fixed by Percona. By default disable the repo at all time as it will break your system yum updates when having mariadb-libs installed and not even have any Percona packages installed. I use Katello and was luckily able to disabled this repo by default in the activation keys section. I have to enable the Percona repo when performing an product upgrade. Still a clumsy workaround.