[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Akonadi with MariaDB 10



Am Dienstag, 14. Juli 2015, 19:51:54 schrieb Martin Steigerwald:
[…]
> With newest akonadi-backend-mysql package from unstable it is not possible
> to replace mysql with mariadb.
> 
> I have just switched and will test for a while. So far looks good.
> 
> See:
> 
> 
> Bug#746651: akonadi-backend-mysql: please make it possible to use with
> MariaDB packages
> https://bugs.debian.org/746651

So far so good, there are just one issue:

It complains about missing fields and tables in mysql table and recommends to 
run mysql_upgrade script.

This however is not inside mariadb-server-core but in mariadb-server:

martin@merkaba:~> dpkg -L mariadb-server-core-10.0 | grep upgrade
martin@merkaba:~> dpkg -L mariadb-server-10.0 | grep upgrade 
/usr/bin/mysql_upgrade
/usr/share/man/man1/mysql_upgrade.1.gz
/var/lib/mysql-upgrade

Thus one has to install a full MariaDB server to do the upgrade. The upgrade 
then works as following:

martin@merkaba:~/.local/share/akonadi> mysql_upgrade --defaults-
file=mysql.conf --socket=/tmp/akonadi-martin.MekFVe/mysql.socket
MySQL upgrade detected
Phase 1/6: Checking and upgrading mysql database
Processing databases
mysql
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.host                                         OK
mysql.ndb_binlog_index                             OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.servers                                      OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.user                                         OK
Phase 2/6: Fixing views from mysql
Phase 3/6: Running 'mysql_fix_privilege_tables'
Phase 4/6: Fixing table and database names
Phase 5/6: Checking and upgrading tables
Processing databases
akonadi
akonadi.collectionattributetable                   OK
akonadi.collectionmimetyperelation                 OK
akonadi.collectionpimitemrelation                  OK
akonadi.collectiontable                            OK
akonadi.flagtable                                  OK
akonadi.mimetypetable                              OK
akonadi.parttable                                  OK
akonadi.parttypetable                              OK
akonadi.pimitemflagrelation                        OK
akonadi.pimitemtable                               OK
akonadi.pimitemtagrelation                         OK
akonadi.resourcetable                              OK
akonadi.schemaversiontable                         OK
akonadi.tagattributetable                          OK
akonadi.tagremoteidresourcerelationtable           OK
akonadi.tagtable                                   OK
akonadi.tagtypetable                               OK
information_schema
performance_schema
Phase 6/6: Running 'FLUSH PRIVILEGES'
OK

Then all is nice :)

I am not sure whether both options are needed, but just the --defaults-file 
option was not enough.

I reported a bug about including mysql_upgrade script in core package:

Bug#793977: mariadb-server-core-10.0: please include mysql_upgrade for 
application started mariadb server

I think this process ideally would be automatically triggered by Akonadi, but 
well as AkonadiNext may replace it, it may not be worthwhile to still 
implement it, as it can be fixed manually and it didn´t seem to affect 
availability of the database to Akonadi.

Ciao,
-- 
Martin


Reply to: