this version is needed in order to work correctly together with LyX 2.0. please bump. Reproducible: Always
2.14.1 release of Lilypond now available at http://download.linuxaudio.org/lilypond/sources/v2.14/
Created attachment 278259 [details] eBuild for Lilypond 2.14.1 Attached is an eBuild for anyone who wants to try the new version. It's simply the existing media-sound/lilypond-2.12.3 ebuild with the (no longer needed??) epatch lines removed. I've tried this and it Works For Me™ on an x86 system (mostly x86 not ~x86) as long as Siim Ainsaar's patch for media-gfx/fontforge has been applied (I'm using fontforge-20110222). This bug depends upon Bug 367425.
the ebuild worked well for me on ~amd64
Oh, that's stable vs. unstable.
2.14.1 built not with texlive-2011 but 2.14.2 does.
*** This bug has been marked as a duplicate of bug 334835 ***
(In reply to comment #6) > > *** This bug has been marked as a duplicate of bug 334835 *** I don't suppose you bothered to read the bugs fully or check how Lilypond's release versioning works, did you? 2.13 (as specified in bug #334835) is an old unstable version, 1.15 is the current development version. Distros should be packaging even-numbered (i.e. "stable") versions of Lilypond, i.e. 2.14.x at present. The 2.14.x releases address comment #1 in this bug (LyX 2.0 dependency) AND comment #1 in the other bug ("latest stable release was awhile ago"). 2.14.2 is only 5 weeks old. Finally, this bug report addresses the zlib issue correctly and the dependency upon bug #367425 to resolve that.
Correction to last comment: 2.13 (as specified in bug #334835) is an old unstable version, 2.15 is the current development version.
@Joe, I'm sorry if I bothered you. The reasoning behind marking this bug as duplicate in favor of #334835 is that usually (at least in my team/herds) we have a policy, if there are two or more bugs requesting the same thing (this time was "updating lilypond") we leave open the older and mark the others as duplicates of it. This is what happened here. I don't want to start a fight, so if you still want after the explanation I gave, me, to reopen this, I will do it. I'm trying to update a package I've never touched before, mistakes can be made and I'm counting on the help and contributions of users like you. Thank you all for your help so far and I hope to have working ebuilds for both current stable and unstable versions of lilypond soon.
(In reply to comment #9) > ... we have a > policy, if there are two or more bugs requesting the same thing (this time was > "updating lilypond") we leave open the older and mark the others as duplicates > of it. Thanks for the reply. I already have working Lilipond 2.14.1 under Gentoo. Just apply Siim Ainsaar's patch to fontforge, as attached to #367425 with a single epatch line added to the ebuild (I appreciate you may not be able to just add this to the portage tree, however) and then use the ebuild attached to this bug. Sorry if I was short with you, however I was unaware of your bug numbering priority policy. I made some efforts to document exactly how to get Lilypond working this way and felt like my efforts had been ignored, 6 weeks later.
