maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #05105
Re: Summary of the MDEV-3882 (.deb upgrade from mysql to mariadb fails due to apt-get considering it a downgrade)
Hello.
would help us only temporarely - to the moment Oracle releases even
later' version.
We can use epoch to ensure that our version will always be bigger than the
official Debian/Ubuntu version of MySQL:
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
Something like 1:5.5.29-mariadb1~wheezy. This will always be prefered by
apt-get over any official Debian package.
Yep, that will always be preferred by apt-get.
So we can easily solve it this way.
I didn't find anything that could affect apt-get and guys on #Debian
didn't recommend anything.
I believe it works to specify desired version explicitly, as mentioned in the
bug report as workaround:
sudo apt-get install mariadb-server libmysqlclient18=5.5.29-mariadb1~wheezy
Yes, but my intention was to make it working plainly.
So for now i'd do about this:
- change nothing in the existing mariadb-produced debian packages.
- recommend to use 'aptitude' installing the mariadb-server on Debian.
So how do you like my proposal? Any other ideas?
I think it is better if we use the epoch to make MariaDB upgrades work
automatically with both apt-get and aptitude, like they used to.
Agree.
Did you check how Percona handles the similar problem?
Percona deals in similar way as far as i see.
Though they don't specify an Epoch, their Version is just sligthly
'later' than the native.
libmysqlclient16 in squeeze for instance:
native package: 5.1.66-0+squeeze1
percona's : 5.1.67-rel14.3-506.squeeze
Best regards.
HF
References