Please provide more information:

• which mysql/mariadb packages do you have before the upgrade attempt (dpkg -l | grep -iE 'maria|mysql)
• what exactly you were trying to do (apt-get ... or whatever else command you were running)
• which mysql/mariadb packages you got after the unsuccessful upgrade attempt (again dpkg -l | grep -iE 'maria|mysql)

sysadmin@aaron:~$ dpkg -l | grep -iE 'maria|mysql'
ii libdbd-mysql-perl 4.021-1+b1 amd64 Perl5 database interface to the MySQL database
ii libmariadbclient18:amd64 5.5.39-2 amd64 MariaDB database client library
ii libmysqlclient18:amd64 5.5.38-0+wheezy1 amd64 MySQL database client library
ii mariadb-client-5.5 5.5.37-1 amd64 MariaDB database client binaries
ii mariadb-client-core-5.5 5.5.39-2 amd64 MariaDB database core client binaries
ii mariadb-common 5.5.39-2 all MariaDB common metapackage
ii mariadb-server 5.5.37-1 all MariaDB database server (metapackage depending on the latest version)
iU mariadb-server-5.5 5.5.39-2 amd64 MariaDB database server binaries
ii mariadb-server-core-5.5 5.5.39-2 amd64 MariaDB database core server files
ii mysql-common 5.5.38-0+wheezy1 all MySQL database common files, e.g. /etc/mysql/my.cnf
rc mysql-server-5.5 5.5.37-0+wheezy1 amd64 MySQL database server binaries and system database setup
ii php5-mysqlnd 5.4.4-14+deb7u14 amd64 MySQL module for php5 (Native Driver)

I've just done an "apt-get upgrade", few hours after this bug report, and the upgrade works fine now.
Did you updated the "mariadb-client-5.5_5.5.39-2_amd64.deb" to resolve the problem ?

Hi,

Thanks for the update.
None of mariadb* packages you have on the machine come from our repository. Apparently, you are using the 'unstable' Debian repo. We don't control package publishing there; I suppose it's possible that they were updated after your report. If it's important, we can try to ask Otto Kekäläinen, or you can use Debian resources to find out.

I think I use your repository:

$ cat /etc/apt/sources.list.d/MariaDB.list 
  #
  # MariaDB 5.5 repository list - created 2013-12-11 23:45 UTC
  # http://mariadb.org/mariadb/repositories/
  #
  deb http://ftp.igh.cnrs.fr/pub/mariadb/repo/5.5/debian wheezy main
  deb-src http://ftp.igh.cnrs.fr/pub/mariadb/repo/5.5/debian wheezy main

Our packages look differently, you'd see something like 5.5.39+maria-1~wheezy in the version field, you can see it yourself in the repo: http://ftp.igh.cnrs.fr/pub/mariadb/repo/5.5/debian/pool/main/m/mariadb-5.5/.
"5.5.39-2" and alike is the Debian thing.
Probably you have both repos on the list, and apt thinks that the Debian one is higher.

Btw, it's a potentially problematic configuration, especially if at some point you want to switch to 10.0 – if you have both repos, you shouldn't use upgrade or dist-upgrade. Better still, choose one of the repos and disable the other one.

Ok, Thanx a lot, I'll search about packages priorities.
I close the issue.
Cheers

In Debian testing/unstable the location of the man page innochecksum was changed and that is the likely cause to your error message. You can recover by running 'sudo dpkg -r mariadb-server-5.5' and then 'sudo apt-get install mariadb-server' to continue to install/upgrade the whole set of packages.

Please don't use Debian testing/unstable repositories mixed with your Wheezy install, at least not in production environments.

Closed as "Not a Bug" in the sense that it's not MariaDB bug, at least.