| commit | d24e96542eacff7ca9d8e176b2c94c8f4d024022 | |
| author | nhnielsen <nhnielsen@283d02a7-25f6-0310-bc7c-ecb5cbfe19da> | |
| Fri, 13 Jul 2007 20:22:46 +0000 (13 20:22 +0000) | ||
| committer | nhnielsen <nhnielsen@283d02a7-25f6-0310-bc7c-ecb5cbfe19da> | |
| Fri, 13 Jul 2007 20:22:46 +0000 (13 20:22 +0000) | ||
| tree | 6e4efa5fdf72dfd41c4e092b2d584caee541b8ec | treesnapshot (tar.gz zip) |
| parent | 90c8a0b5eea2520b3e13a21ab81dd75e7baaf5df | commitdiff |
Make the tracks in the Magnatune database behave and actually show up in the tree. Magnatune service currently has the same problem as the Jamendo service with duplicate tracks... but since they run on the same code, this should not come as a big suprise
git-svn-id: svn+ssh://ianmonroe@svn.kde.org/home/kde/trunk/extragear/multimedia/amarok@687520 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
git-svn-id: svn+ssh://ianmonroe@svn.kde.org/home/kde/trunk/extragear/multimedia/amarok@687520 283d02a7-25f6-0310-bc7c-ecb5cbfe19da