Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 557596 - media-sound/lilypond-2.18.2 causes emerge issues with texlive-metapost
Summary: media-sound/lilypond-2.18.2 causes emerge issues with texlive-metapost
Status: RESOLVED DUPLICATE of bug 525712
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Karl Lindén
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-14 17:27 UTC by gentoo
Modified: 2016-05-28 16:23 UTC (History)
3 users (show)

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

Attachments
emerge --info output (emerge_info.txt,16.81 KB, text/plain)
2015-08-14 17:28 UTC, gentoo 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gentoo 2015-08-14 17:27:04 UTC 
I get this message when emerge -uDNv1 world:

dev-texlive/texlive-metapost:0                                                                                                     
                                                                                                                                   
  (dev-texlive/texlive-metapost-2014:0/0::gentoo, ebuild scheduled for merge) conflicts with                                       
    <dev-texlive/texlive-metapost-2013 required by (media-sound/lilypond-2.18.2:0/0::gentoo, installed)                            
    ^                             ^^^^                                                                                             

I think it's a problem with the way that texlive-metapost now has slots. Maybe the lilypond ebuild needs some kind of modification to require whatever slot is available?

Reproducible: Always




emerge --info see attachment.
Comment 1 gentoo 2015-08-14 17:28:04 UTC 
Created attachment 409012 [details]
emerge --info output
Comment 2 gentoo 2015-12-03 20:26:08 UTC 
This issue is fixed by unmasking lilypond-2.19.15.
Comment 3 Karl Lindén 2016-05-28 16:23:32 UTC 
I think this is the same problem as #525712.

*** This bug has been marked as a duplicate of bug 525712 ***