[MDEV-5557] New debian security upgrade break galera repo. Created: 2014-01-24  Updated: 2020-06-02  Resolved: 2020-06-02

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 5.5.34-galera
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Stefan Eriksson Assignee: Seppo Jaakola
Resolution: Won't Fix Votes: 0
Labels: galera
Environment:

Debian 7 wheezy

Issue Links:
Relates
relates to MDEV-5252 Deb installation issues due to versio... Closed

 Description   

Upgrading these (current stable) breaks mariadb-galera-server-5.5

u: libmysqlclient18
u: mysql-common

It will result in the removal of mysql-galera-server-5.5 binary

and trying to reinstall:

apt-get install mariadb-galera-server galera
Reading package lists... Done
Building dependency tree
Reading state information... Done
galera is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
mariadb-galera-server : Depends: mariadb-galera-server-5.5 (= 5.5.34+maria-1~wheezy) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Current packages after upgrade
/# dpkg -l |grep mysql
ii libdbd-mysql-perl 4.021-1+b1 amd64 Perl5 database interface to the MySQL database
ii libmysqlclient18:amd64 5.5.35+dfsg-0+wheezy1 amd64 MySQL database client library
ii mariadb-common 5.5.34+maria-1~wheezy all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mysql-common 5.5.35+dfsg-0+wheezy1 all MySQL database common files, e.g. /etc/mysql/my.cnf

[EDIT TEMP FIX]

apt-get install mariadb-galera-server-5.5 mariadb-client-5.5 libmysqlclient18=5.5.34+maria-1~wheezy mysql-common=5.5.34+maria-1~wheezy

 Comments   
Comment by Stefan Eriksson [ 2014-01-24 ]

what is the best way to handle these issues?

Is it to recommend all users to:

Pinning the MariaDB Repository

Another thing you can do is to pin the MariaDB repository that you use. This is done by creating a file under '/etc/apt/preferences.d/' with the following contents:
Package: *
Pin: origin <mirror-domain>
Pin-Priority: 1000
Replace '<mirror-domain>' with the domain name of the MariaDB mirror you use. For example, 'ftp.osuosl.org'. With the pin file in place, packages from your MariaDB repository will have priority over packages from the system repositories

an apt-get upgrade breaks the mariadb galera cluster rahter often when mysql-common is added to the mix, maybe rename packages?

Comment by Elena Stepanova [ 2014-01-24 ]

The general issue is being worked on in scope of MDEV-5252, currently we have a community patch which is awaiting a review.

Comment by Stefan Eriksson [ 2014-01-30 ]

Elena thanks can you link for the community patch url? would be nice to see progress.

Comment by Elena Stepanova [ 2014-01-30 ]

The link to the merge request: https://code.launchpad.net/~mcoleman/maria/maria-fix-bug5190/+merge/194226
(It can also be found in the first comment to MDEV-5252)

Comment by Herman van Rink (Inactive) [ 2014-02-03 ]

This issue seems to be fixed in the repo.

Comment by Elena Stepanova [ 2014-10-19 ]

After all back-and-forth, it seems that the only viable solution we came up with is to release the matching versions of MariaDB server as soon as possible after MySQL 5.5 is released, to prevent the situation when the higher version of MySQL is in the debian/ubuntu repos, while MariaDB is not in ours yet.
We seem to have been more or less successful at that over the past months.

However, with MGC it's not the case yet, it can be released significantly later than the corresponding MariaDB 5.5.x server. So, I'm assigning it to nirbhay to decide how to deal with it in regard to Galera. Please close if there's nothing to do.

Comment by Ralf Gebhardt [ 2020-06-02 ]

Unsupported version

Generated at Thu Feb 08 07:05:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.