Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73826 - Amarok 1.2 beta needs musicbrainz to build and it is not in the ebuild.
Summary: Amarok 1.2 beta needs musicbrainz to build and it is not in the ebuild.
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Sound Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-08 11:29 UTC by Charles Sheridan
Modified: 2005-01-10 10:13 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Sheridan 2004-12-08 11:29:25 UTC
Amarok 1.2 beta1 needs musicbrainz to build properly and only kde 3.3.1 and higher installs it. Musicbrainz should be added to the amarok ebuild as a dependency.

Reproducible: Always
Steps to Reproduce:
1.Emerge amarok
2.
3.

Actual Results:  
Stopped emerging with an error of couldn't find musisbrainz.la

Expected Results:  
Compiled successfully
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2005-01-10 02:24:05 UTC
amarok depends on tunepimp, that depends on musicbrainz.
Could you try to find out why it was not picked up?
Comment 2 Charles Sheridan 2005-01-10 07:00:50 UTC
I unemerged musicbrainz and tried to see how to get it back by emerging amaroK. The only time that it showed up in the list to emerge was when I was using the --deep flag. Everything else didn't pull it up as something that was needed. I also checked what happened when tunepimp wasn't already installed. When it isn't installed, then it catches that it needs musicbrainz. From what I can tell, tunepimp was installed with kdemultimedia and since it was already there, it didn't check whether all of its dependicies had been installed.
Comment 3 Gregorio Guidi (RETIRED) gentoo-dev 2005-01-10 10:13:20 UTC
There's nothing to do then: portage does not scan the dependency tree unless
you use --deep, it assumes that installed dependencies are not broken...