Created attachment 410028 [details] emerge --info The stable version media-sound/lilypond-2.18.2 depends on presently unstable dev-tex/metapost. $ emerge -pvt lilypond These are the packages that would be merged, in reverse order: Calculating dependencies . ... done! [ebuild R ] media-sound/lilypond-2.18.2::gentoo USE="-debug -emacs -profile -vim-syntax" LINGUAS="-ca -cs -da -de -el -eo -es -fi -fr -it -ja -nl -ru -sv -tr -uk -vi -zh_TW" PYTHON_TARGETS="python2_7" 0 KiB [ebuild N ~] dev-tex/metapost-1.902::gentoo 0 KiB [ebuild N ] app-eselect/eselect-mpost-0.3::gentoo 0 KiB Total: 3 packages (2 new, 1 reinstall), Size of downloads: 0 KiB 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-2.18.2::gentoo # required by lilypond (argument) =dev-tex/metapost-1.902 ~amd64
Technically, lilypond-2.18.2 depends on dev-tex/metapost or <dev-texlive/texlive-metapost-2013. texlive-metapost-2012 is available and stable on amd64, and in theory ought to satisfy the dependency unless something on your system (a new texlive version?) is blocking it.
Yes, texlive-metapost is 2014 already. So please stabilize =dev-tex/metapost-1.902
I am also running amd64 and have the same problem. Please confirm the bug and stabilize.
ok so after 2.5 months no action towards this being made stable despite stable version media-sound/lilypond-2.18.2 depends on presently unstable dev-tex/metapost. ?? This is why arches are CC'd by folk other than those of the herd or project charged with that responsibility on;t to be challenged by the pedantic rej or jer. Time out: one week
lilypond deps are wrong; dev-tex/metapost wont be used unless user eselects it; mpost command is provided by texlive-core...
is there something blocking this stabilization?
Well, the original bug was invalid as dep can be fulfilled by the other package listed in || ( ) dep, if you want to stabilize metapost for other reason, feel free to open a different bug for it
