Bugfix release. Reproducible: Always Steps to Reproduce: 1. emerge amarok 2. 3.
Renaming the ebuild seems to work. However, there have been cpu usage problems reported (constant 100%), so, if this is bumped, could you please keep 1.2.1 for those of us with laptops that tend to overheat?
*** Bug 85333 has been marked as a duplicate of this bug. ***
I've bumped my 1.2.1 ebuild on my amd64 box and it run's great, I'm using arts output but i tried aKode engine output and it starts to eat my whole cpu after few seconds, arts behave very good.
The CPU usage problem is fixed in CVS. Patch here: http://phpfi.com/54482
Created attachment 53593 [details, diff] Patch to fix the 100% CPU use problem This is the fix that went into CVS (a revert from a change, actually). I've adapted that to amarok-1.2.2 source, this could be aplied by the ebuild.
Created attachment 53597 [details, diff] Previous patch had a problem Always test a patch before submiting... Shame on me ;-)
Just to note that the patch is for http://bugs.kde.org/show_bug.cgi?id=101524, not related to akode (probably http://bugs.kde.org/show_bug.cgi?id=101433, not amarok's fault)
*** Bug 85550 has been marked as a duplicate of this bug. ***
*** Bug 85660 has been marked as a duplicate of this bug. ***
Created attachment 53716 [details] New ebuild that patches the source with the above patch before building I just added: src_unpack() { unpack ${A} cd ${S} epatch ${FILESDIR}/100cbfix.diff } and put 100cbfix.diff in the files directory.
amarok-1.2.2 is in portage now.