Thanks for Elena and Sergei for looking into the issues I reported about building MariaDB on some architectures that MariaDB support! What do you people think, what kind of priority is it for MariaDB to be equally good as MySQL in terms of multi-architecture support? Should these issues be fixed next week or should I package MariaDB 5.5 and soon MariaDB 10.0 so that they are not offered to all architectures that MySQL is? 2014-02-19 18:01 GMT+02:00 Otto Kekäläinen <otto@seravo.fi>:

Hello!

The Debian build status can be seen at https://buildd.debian.org/status/package.php?p=mariadb-5.5 (and for MySQL at https://buildd.debian.org/status/package.php?p=mysql-5.5).

The sparc build issue already got solved but for the others I filed the following bugs (as each failure seems to have different cause):

https://mariadb.atlassian.net/browse/MDEV-5708 https://mariadb.atlassian.net/browse/MDEV-5707 https://mariadb.atlassian.net/browse/MDEV-5706

Could somebody please look into these?

I assume that some of them might be easy if MySQL already has them solved, then all that needs to be done is to copy a patch from MySQL upstream or from MySQL patches in Debian (see http://anonscm.debian.org/gitweb/?p=pkg-mysql/mysql-5.5.git;a=tree;f=debian/...).

(MariaDB Debian builds are pulled from http://anonscm.debian.org/gitweb/?p=pkg-mysql/mariadb-5.5.git and mirrored at https://github.com/ottok/mariadb-5.5)

Also, here are two QA issues that are related. I am not sure what to do with them: http://qa.debian.org/bls/packages/m/mariadb-5.5.html

-- Check out our blog at http://seravo.fi/blog and follow @ottokekalainen