[MDEV-4562] RPM packages are wrongly marked as replacing MySQL Created: 2013-05-22  Updated: 2013-05-22  Resolved: 2013-05-22

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.30, 5.5.29-galera
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Klavs Klavsen Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: packaging

Issue Links:
Duplicate
is duplicated by MDEV-3950 mariadb rpms should not obsolete mysql? Open

 Description   

I have both MySQL rpms (from MySQL) and MariaDB and MariaDB-Galera packages in my local repo - as I am working om moving servers to using MariaDB (and some MariaDB-Galera).

My problem is, that with those packages in my local repo - yum suggests hopeless updates - such as this:

 MariaDB-Galera-server                                                      x86_64                                          5.5.29-1                                                                 yousee                                                               19 M
     replacing  MySQL-server.x86_64 5.5.30-1.el6
 MariaDB-client                                                             x86_64                                          5.5.30-1                                                                 yousee                                                               10 M
     replacing  MySQL-client.x86_64 5.5.30-1.el6
 MariaDB-server                                                             x86_64                                          5.5.30-1                                                                 yousee                                                               33 M
     replacing  MySQL-server.x86_64 5.5.30-1.el6

I think it would be fixed by something like this:

  • MariaDB-Server - should have MariaDB-Galera-Server and MySQL-Server listed as conflicts (and vice versa for MariaDB-Galera).
  • I think it's this obsoletes lines, that doesn't work (atleast with RPM version in RHEL 6):

    Obsoletes:	mysql < %{version}-%{release}

    so it should be removed - this way you'll have to MANUALLY and ACTIVELY ask to install MariaDB-Server or MariaDB-Galera-Server - to get your current replaced - instead of a yum update wanting to do it automaticly for you


Generated at Thu Feb 08 06:57:23 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.