when will amarok 1.4 be available in debian sarge? still there are a lot of dependencies not fulfilled.

any ideas? i can\'t compile from source...

Hi.
Go to backports.org and update your libtag.
After that it is possible to compile amarok 1.4svn from source (I am doing this all the time). IMO is this the only dependency not fullfilled in sarge.

Here you have debian files for amaroK. The author of the page usually updates it.
http://www2.truman.edu/~iam504/amarok/

And if you can help me with amarok for ubuntu (debian packages) please take a look at this topic: http://amarok.kde.org/component/option,com_simpleboard/Itemid,57/func,view/catid,9/id,10835/#10835

Pochu

marcel wrote:

IMO is this the only dependency not fullfilled in sarge.

not quiet. amarok 1.4b1 depends on kdelibs4, but i got kdelibs4c2a installed.
and there are several dependencies more.
libtag1c2_1.4-1 i.e collidates with libtag1c2a.

i guess i\'ll wait until amarok1.4.b1 will be available through apt-get without any probs.

rokkford wrote:

not quiet. amarok 1.4b1 depends on kdelibs4, but i got kdelibs4c2a installed.
and there are several dependencies more.
libtag1c2_1.4-1 i.e collidates with libtag1c2a.

That\'s true for the deb packages you are using. Obviously they were built for e.g. sid or etch but not sarge.

rokkford wrote:

marcel wrote:

IMO is this the only dependency not fullfilled in sarge.

not quiet. amarok 1.4b1 depends on kdelibs4, but i got kdelibs4c2a installed.
and there are several dependencies more.
libtag1c2_1.4-1 i.e collidates with libtag1c2a.

i guess i\'ll wait until amarok1.4.b1 will be available through apt-get without any probs.

Whats wrong with my packages (the ones on truman.edu)? Its built on a vanilla sarge system.

OK, looks more like rokkford is using non-sarge packets...
Your packets seem to be fine.

KDE maintains backwards binary compability within a major version, probably if rokkford just forced the install it would work. Or use klik.

I agree.
I think debian renamed their packages because of a c++ switch or something like that. It\'s definitely no KDE thing, happened before, in the times when sarge was testing.

marcel wrote:

I agree.
I think debian renamed their packages because of a c++ switch or something like that. It\'s definitely no KDE thing, happened before, in the times when sarge was testing.

Oh well if its a C++ ABI thing it might not be compatible then.

that\'s true, debian again has problems with dependencies.

nevertheless installing amarok-svn worked out fine