Your message dated Sat, 2 Jun 2012 10:30:45 +0300
with message-id <201206021030.49072.mo...@debian.org>
and subject line Re: [debian-mysql] Bug#675304: amarok
has caused the Debian Bug report #675304,
regarding upgrade from 5.1.61-3 to 5.5.23+dfsg-2 broke amarok
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
675304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-common
Version: 5.5.23+dfsg-2
Severity: critical

Since upgrading to 5.5.23+dfsg-2, I get following amarok error

The amarok database reported the following errors:
GREPME MySQLe query failed! (2000)  on init
In most cases you will need to resolve these errors before Amarok will run 
properly.

Then each song is said to be a duplicate, then I do not get any music in amarok 
DB.

amarok is
ii  amarok                              2.5.0-1                             
easy to use media player based on the KDE Platform

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (700, 
'proposed-updates'), (600, 'stable'), (400, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information

________________________________

This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes.
To protect the environment please do not print this e-mail unless necessary.

An NDS Group Limited company. www.nds.com



--- End Message ---
--- Begin Message ---
Version: 2.5.0-2

found 675304 2.5.0-1
thanks

Hello,

On penktadienis 01 Bir┼żelis 2012 01:40:22 Clint Byrum wrote:
> Excerpts from Nicholas Bamber's message of 2012-05-31 14:05:36 -0700:
> > Modestas,
> > 
> >     I would be very grateful if you could advise us on this bug:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675304
> > 
> >     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
> understand.
> 
> A workaround is probably to comment those out of /etc/mysql/my.cnf until
> the new amarok is available.

As the Debian changelog states, amarok 2.5.0-2 or later no longer reads system 
mysql configuration files or depends on the system mysql server in any way. 
That's was my original intent all along (and it was actually true for some 
period of time) but upstream broke it at some point.

I suppose mysql-common 5.5 should Break amarok << 2.5.0-2 because it's the one 
which ships the offensive my.cnf file with !includedir /etc/mysql/conf.d/ 
directive in it. /etc/mysql/conf.d/ does not exist if mysql-server-5.5 is not 
installed which causes libmysqld embedded into previous versions of amarok to 
bomb.

FWIW, I also believe that there is a bug in mysql-common that my.conf refers 
to the directory which might not be available.

-- 
Modestas Vainius <mo...@debian.org>

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

Reply via email to