Excerpts from Nicholas Bamber's message of 2012-05-31 14:05:36 -0700:
> I would be very grateful if you could advise us on this bug:
> I presume what has happpened is that the user is on testing and did an
> apt-get upgrade. Because of the current state of affairs his mysql got
> upgraded and not his amarok.
> I don't quite see why that should cause his amarok to fail - an
> explanation would be appreciated.
> Should we be asking for the amarok 2.5.0-3 to be rushed through to
> testing? Should we put a breaks clause to make late mysql incompatible
> with early versions of amarok - though I really don't want to do that as
> it would be unworkable in the long term.
> Also beyond following the proper transition procedures is there
> something we could be doing to avoid these situations?
If I had to guess, I'd say its the new MySQL 5.5 mysql-common's my.cnf
directives that the old 5.1 libmysqld embedded in amarok does not
A workaround is probably to comment those out of /etc/mysql/my.cnf until
the new amarok is available.
pkg-kde-extras mailing list