Bug#926231: [debian-mysql] Bug#926231: Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-17 Thread Otto Kekäläinen
I think I've found out what is going on here. If one has mysql-5.7 installed, one needs to run mysql_upgrade plus some extra conversions to get the database in a working state. I rename the socket auth plugin in

Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-16 Thread Brad Rogers
On Tue, 16 Apr 2019 11:33:23 +0300 Otto Kekäläinen wrote: Hello Otto, >I am sorry but I am not able to replicate this bug. So it cannot at >least be common, thus downgrading severity. > >Please figure out a way for me to replicate it so I can debug what is >happening. Also, check out if there

Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-16 Thread Otto Kekäläinen
Control: severity -1 normal I am sorry but I am not able to replicate this bug. So it cannot at least be common, thus downgrading severity. Please figure out a way for me to replicate it so I can debug what is happening. Also, check out if there is any output at /var/log/mysql/* Here are is an

Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-04 Thread Graham Cobb
Package: mariadb-server-10.3 Version: 1:10.3.13-2 Followup-For: Bug #926231 OK, this is weird! I tried the two options suggested by Otto. mysql_upgrade failed... # mysql_upgrade Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000):

Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-04 Thread Otto Kekäläinen
Have you tried running mysql_upgrade or systemctl restart mariadb ? Both commands will run some mysql.user table modifications to compensate on how MySQL 5.7 is different from MySQL 5.6 and previous ones.

Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-03 Thread Olaf van der Spek
On Wed, Apr 3, 2019 at 11:12 PM Graham Cobb wrote: > I'm not sure what the "MariaDB error log" is but I have found the following > entries in syslog: It's /var/log/mysql/error.log

Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-03 Thread Graham Cobb
Package: mariadb-server-10.3 Version: 1:10.3.13-2 Followup-For: Bug #926231 I'm not sure what the "MariaDB error log" is but I have found the following entries in syslog: Apr 3 20:31:00 novatech mariadb-server-10.3.postinst[8418]: Apr 3 20:31:00 novatech mariadb-server-10.3.postinst[8418]:

Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-02 Thread Otto Kekäläinen
What does the MariaDB error log say when the ALTER TABLE in the postinst run? ti 2. huhtikuuta 2019 klo 17.30 Graham Cobb kirjoitti: > Package: mariadb-server-10.3 > Version: 1:10.3.13-2 > Followup-For: Bug #926231 > > The bug still exists in 1:10.3.13-2 > > > -- System Information: > Debian

Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-02 Thread Graham Cobb
Package: mariadb-server-10.3 Version: 1:10.3.13-2 Followup-For: Bug #926231 The bug still exists in 1:10.3.13-2 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux

Bug#926231: [debian-mysql] Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-02 Thread Otto Kekäläinen
Please try again with latest version in Debian unstable: mariadb-10.3 1:10.3.13-2

Bug#926231: mariadb-server-10.3: dpkg configure error - upgrade from mysql

2019-04-02 Thread Graham Cobb
Package: mariadb-server-10.3 Version: 1:10.3.13-1 Severity: important Dear Maintainer, mariadb-server-10.3 will not configure on my debian testing (buster) system. The system previously used mysql (I do not remember exacty which version but I can find out if necessary). Since that was