Debian Wheezy wirth http://mirrors.linsrv.net/mariadb/repo/10.0/debian mirror.

Hi,

Thanks for reporting this.
Yes, unfortunately it so happens that the direct upgrade from alpha to beta currently does not work. Please run the following:

sudo apt-get remove libmariadbclient18 libmysqlclient18 mariadb-client-10.0 mariadb-client-core-10.0 mariadb-server mariadb-server-10.0 mariadb-server-core-10.0
sudo apt-get install mariadb-server

It should fix the broken installation (and your data should remain intact, but as usual with any upgrade, the good practice is to make a backup before running it).

Please let us know if it works for you.

Thanks and sorry for the inconvenience.

Thank you for your answer.

Tonight, I'll do what you are advicing and I'll let you know if it works.

Question : will it do the same problem when it will upgrade from 10.0.5 to the next betas? And from beta to final?

No, there should be no such problem in future. It's a bug that we are going to fix right away, actually it might happen that by the time you retry installation the fixed packages will already be available; but you will need to run the remove command anyway, as currently after the failed upgrade your MariaDB installation is in inconsistent state.

Elena, thank you, that did the trick. I also removed and reinstalled mysql-common and mariadb-common because they were still in 10.0.5, and I re-configured MariaDB. I didn't loose any data so that's cool.

I noticed that 10.0.5 packages were removed from the mirror I used, so I think you can just close the ticket. I suppose that when the 10.0.5 packages will be added again, the bug will not happen again.

By the way, great and fast support, thank you!

Right, deb packages are re-uploaded to the mirrors; maybe the mirror you are using is not up-to-date yet, but it will be soon. The new packages don't have the problem, upgrade 10.0.4 => 10.0.5 should work smoothly (I tried upgrade on Wheezy to confirm). Please let us know if you encounter further issues.