[Pkg-kde-extras] Bug#672207: [amarok] Fails to open internal database after upgrade to mysql 5.5 from, 5.1

2012-05-09 Thread tv.deb...@googlemail.com
Package: amarok Version: 2.5.0-1 Followup-For: Bug #672207 Dear Maintainer, I can confirm this, reverting to mysql-common 5.1.62-1 solves the issue. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500,

[Pkg-kde-extras] Bug#672207: [amarok] Fails to open internal database after upgrade to mysql 5.5 from, 5.1

2012-05-09 Thread Jay DeKing
Confirmed here on wheezy/sid and, as noted above, reverting to mysql-common 5.1.62-1 solves the issue for me. Jay DeKing   A generation which ignores history has no past and no future. -- Robert Heinlein___ pkg-kde-extras mailing list

[Pkg-kde-extras] Bug#672207: [amarok] Fails to open internal database after upgrade to mysql 5.5 from 5.1

2012-05-08 Thread Schrober
Package: amarok Version: 2.5.0-1 Severity: normal It just shows The amarok database reported the following errors: GREPME MySQLe query failed! (2000) Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist on init In most cases you will need to resolve these errors