Amarok 1.4.2 collection scan fails

[Jeff Mitchell]

Also, I'm not too familiar with Debian package names, but it looks like he has 
two versions of taglib installed there.  Is that so?  This is something that 
is known to cause problems...

--Jeff

On Sunday 27 August 2006 00:40, Adeodato Simó wrote:
> * Florian Genauer [Fri, 25 Aug 2006 17:49:40 +0200]:
> > I am using Debian sarge - and thus I have
> >
> > ii  libtag1-dev    1.4-4
> > ii  libtag1c2a     1.4-4
> > ii  libtagc0       1.4-4
> > ii  libtagc0-dev   1.4-4
> >
> > installed on it.
>
> Where did you get those? I ask since there is a problem with them:
> if a library package name ends in c2 or c2a, then it should be compiled
> against libstdc++6.
>
> The default libstdc++ in sarge is libstdc++5, so either the package
> should be named libtag1. (Unless they're indeed compiled against
> libstdc++6).
>
> You can find quite up to date and well-done backports for taglib here:
>
>   http://backports.org/debian/pool/main/t/taglib/
>
> I guess I could also look into providing Amarok sarge packages for 1.4
> (latest one I did was 1.3.6). I'd like a bit of hint of how much
> interest there'd be for those, in order not to work in vain. ;-)
>
> Cheers,