Bug 200303 - Use packagekit to check for useful codecs
Summary: Use packagekit to check for useful codecs
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 189665 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-15 14:37 UTC by Dotan Cohen
Modified: 2009-07-25 09:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dotan Cohen 2009-07-15 14:37:29 UTC
Version:            (using KDE 4.2.96)
Installed from:    Ubuntu Packages

It appears that Amarok is not using a desktop and distro independent way of installing codecs. If has been suggested on the *buntu bugtracker that Amarok should use packagekit to check for useful codecs instead of using update-notifier-kde to prompt for restricted codecs install.

See this bug:
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/346246
Comment 1 Dotan Cohen 2009-07-15 14:38:59 UTC
*** Bug 189665 has been marked as a duplicate of this bug. ***
Comment 2 Myriam Schweingruber 2009-07-15 20:43:22 UTC
Dotan, there is no way we  could do that, for obvious reasons: we don't make packages at all :). We provide the tarball of the application, it's up to the packagers of the distributions to provide the necessary codecs and links to get the codecs installed.
Comment 3 Dotan Cohen 2009-07-23 09:08:38 UTC
Thank you, Myriam. I am a bit confused as *buntu seems to insist that it is a KDE issue. Could you please take a look at the downstream bug and try to make sense of what they are saying? I would like to see this issue resolved, and the *buntu devs might just need a hint as to what they are doing wrong, or maybe you (or I if you tell me) can tell them why this is not KDE's responsibility. Thanks.
Comment 4 Mark Kretschmann 2009-07-25 09:50:48 UTC
FYI, we are also discussing this issue on our developer mailing list:

http://lists.kde.org/?t=124834372100001&r=1&w=2