[debian-mysql] Bug#675304: amarok

Nicholas Bamber nicholas at periapt.co.uk
Thu May 31 21:05:36 UTC 2012

	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?

More information about the pkg-mysql-maint mailing list