Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 676208 - media-sound/lilypond-VERSION? with sys-devel/autogen-VERSION? and dev-scheme/guile-VERSION? not compatible
Summary: media-sound/lilypond-VERSION? with sys-devel/autogen-VERSION? and dev-scheme/...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Scheme Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-25 10:07 UTC by Klaus Ethgen
Modified: 2019-11-17 05:17 UTC (History)
2 users (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 Klaus Ethgen 2019-01-25 10:07:09 UTC
Some days ago I started to use lilypond on gentoo and had big troubles as I compiled it first with guile-2.x.

As you can see in the thread started from <20190113124201.GA13430@ikki.ethgen.ch> in lilypond mailinglist, it makes trouble with utf-8 characters or everything that is not ASCII. The conclusion is, that guile >= 2.0 counts as very experimental.

Now with the sync from today, sys-devel/autogen depends on guile >= 2.0, producing a conflict that can only be solved with the following mask:
>=dev-scheme/guile-2.0.0
=sys-devel/autogen-5.18.16

Please provide a working setup that is producing a working lilypond.
Comment 1 Arnaud Soulard 2019-01-25 13:04:03 UTC
I have the same issue when trying to install lilypond:

=================================================================
emerge -av media-sound/lilypond

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by media-sound/lilypond (argument)
=media-sound/lilypond-9999 **

=================================================================

When setting in file /etc/portage/package.accept_keywords/lilypond:
=media-sound/lilypond-9999 **

sudo emerge -av media-sound/lilypond
[ebuild     UD ] dev-scheme/guile-1.8.8-r3:12/8::gentoo [2.0.14-r3:12/22::gentoo] USE="deprecated nls readline%* regex threads -debug -debug-freelist% -debug-malloc -discouraged% -emacs% -networking*" 0 KiB
[ebuild  N    *] media-sound/lilypond-9999::gentoo  USE="-debug -emacs -guile2 -profile -vim-syntax" PYTHON_TARGETS="python2_7" 0 KiB

Total: 2 packages (1 downgrade, 1 new), Size of downloads: 0 KiB

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-scheme/guile:12

  (dev-scheme/guile-1.8.8-r3:12/8::gentoo, ebuild scheduled for merge) pulled in by
    <dev-scheme/guile-2.0:12 required by (media-sound/lilypond-9999:0/0::gentoo, ebuild scheduled for merge)
    ^                 ^^^^^^                                                                                                                                                          

  (dev-scheme/guile-2.0.14-r3:12/22::gentoo, installed) pulled in by
    >=dev-scheme/guile-2.0:= required by (sys-devel/autogen-5.18.16:0/0::gentoo, installed)
    ^^                 ^^^                                                                                                                                           
    (and 1 more with the same problem)



=================================================================
emerge -aC sys-devel/autogen

sudo emerge -av media-sound/lilypond

[ebuild     UD ] dev-scheme/guile-1.8.8-r3:12/8::gentoo [2.0.14-r3:12/22::gentoo] USE="deprecated nls readline%* regex threads -debug -debug-freelist% -debug-malloc -discouraged% -emacs% -networking*" 0 KiB
[ebuild  N    *] media-sound/lilypond-9999::gentoo  USE="-debug -emacs -guile2 -profile -vim-syntax" PYTHON_TARGETS="python2_7" 0 KiB


=> successful emerged
but if I run:
emerge -auvDN world


Calculating dependencies... done!
[ebuild   R    ] dev-scheme/guile-1.8.8-r3:12/8::gentoo  USE="deprecated nls readline regex threads -debug -debug-freelist -debug-malloc -discouraged -emacs -networking" 0 KiB
[ebuild     U ~] dev-scheme/guile-2.2.3:12/2.2-1::gentoo [1.8.8-r3:12/8::gentoo] USE="deprecated networking* nls regex threads -debug -debug-malloc (-debug-freelist%) (-discouraged%) (-emacs%) (-readline%*)" 16 862 KiB
[ebuild  N     ] sys-devel/autogen-5.18.16::gentoo  USE="-libopts -static-libs" 0 KiB

Total: 3 packages (1 upgrade, 1 new, 1 reinstall), Size of downloads: 16 862 KiB

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-scheme/guile:12

  (dev-scheme/guile-2.2.3:12/2.2-1::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-scheme/guile-2.0:= required by (sys-devel/autogen-5.18.16:0/0::gentoo, ebuild scheduled for merge)
    ^^                 ^^^                                                                                                                                                            

  (dev-scheme/guile-1.8.8-r3:12/8::gentoo, ebuild scheduled for merge) pulled in by
    <dev-scheme/guile-2.0:12 required by (media-sound/lilypond-9999:0/0::gentoo, installed)
    ^                 ^^^^^^                                                                                                                                         


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by media-sound/lilypond-9999::gentoo[-guile2]
# required by @selected
# required by @world (argument)
=dev-scheme/guile-2.2.3 ~amd64


Therefore, if I want to be able to update my gentoo on a day to day basis, I have to uninstall lilypond...