FS#5205 - Amarok doesn't work with mysql > 5.0.22

Attached to Project: Arch Linux
Opened by nackd (Prieto) - Thursday, 10 August 2006, 20:38 GMT
Last edited by Jan de Groot (JGC) - Sunday, 13 August 2006, 12:28 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Damir Perisa (damir.perisa)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

See http://www.futhark.ch/mysql/148.html
Also, amarok can't read my collection when using mysql-5.0.23-1, there is a thread in the forums about this: http://bbs.archlinux.org/viewtopic.php?p=184237

It is good to be bleeding edge, but having a database server which has never been officially released due to bugs is not that good.
This task depends upon

Closed by  Damir Perisa (damir.perisa)
Monday, 06 November 2006, 05:53 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Saturday, 12 August 2006, 07:35 GMT
5.0.24 is out does this solve the issues?
Comment by nackd (Prieto) - Saturday, 12 August 2006, 11:38 GMT
I have compiled 5.0.24 and amarok doesn't work with it either.
Comment by Tobias Powalowski (tpowa) - Saturday, 12 August 2006, 11:39 GMT
ok but at least the version is now an official one
Comment by nackd (Prieto) - Saturday, 12 August 2006, 11:45 GMT
See this bug report: http://bugs.kde.org/show_bug.cgi?id=132114
and this thread: http://mail.kde.org/pipermail/amarok/2006-August/000925.html
Comment by Tobias Powalowski (tpowa) - Saturday, 12 August 2006, 15:40 GMT
me assigns it to amarok maintainer now
Comment by Gianluca Varisco (giangy) - Friday, 25 August 2006, 12:13 GMT
Amarok 1.4.2 was released and the problem with MySQL 5.0.23+ was fixed. For more details, see http://websvn.kde.org/tags/amarok/1.4.2/multimedia/amarok/ChangeLog?rev=575607&view=auto :-)
Comment by Damir Perisa (damir.perisa) - Friday, 25 August 2006, 18:17 GMT
amarok 1.4.2 is on the way...
Comment by Greg Meyer (oggb4mp3) - Monday, 06 November 2006, 01:57 GMT
Since it is fixed upstream, this bug can be closed.

Loading...