Upgrading MariaDB 5.5 to 10.1.11 fails with RPM (MDEV-9584)

[MDEV-17722] MariaDB common update file fails Created: 2018-11-14  Updated: 2020-04-22

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Technical task Priority: Major
Reporter: Wilbur Union Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Compatibility
Environment:

Centos 7.4


Issue Links:
Duplicate
duplicates MDEV-9800 Conflicts upon installing MariaDB ser... Open
duplicates MDEV-14548 rpm file conflict Closed
PartOf
is part of MDEV-22322 Percona Server -> Mariadb Upgrades Open
Sprint: 10.1.14

 Description   

The mariaDb common file update persistantly fails with the error => file /etc/my.cnf from install of MariaDB-common-10.2.19-1.el7.centos.x86_64 conflicts with file from package Percona-Server-shared-56-5.6.41-rel84.1.el7.x86_64

If there is a MariaDb file instead that provides

/usr/lib64/libmysqlclient.so.18.1.0
/usr/lib64/libmysqlclient_r.so.18.1.0

please let me know and I will change over to it

This has been going on since the release of 10.2 and sometimes Percona provides an update release that works and sometimes does not - so I have to manually go to the repo and " rpm Uvh --force [file link] " it to install



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2018-11-14 ]

I believe this was intended for MariaDB Server rather than MariaDB ColumnStore. I have moved it appropriately.

Comment by Elena Stepanova [ 2018-12-07 ]

This is a part of a generic problem which is supposed to be addressed one day in the scope of MDEV-9584. For now, RPM cross-upgrades can only work by pure luck. Workarounds vary from forced upgrade (which apparently works for you) to removal of the old packages and installing new ones instead – which, in turn, might at some point require ignoring dependencies.

Generated at Thu Feb 08 08:38:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.