Hello David, or anyone else affected, Accepted lilypond into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/lilypond/2.16.2-2build0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: lilypond (Ubuntu Saucy) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-bin in Ubuntu. https://bugs.launchpad.net/bugs/1243777 Title: Fonts are spectacularly broken Status in “lilypond” package in Ubuntu: Confirmed Status in “texlive-bin” package in Ubuntu: Fix Released Status in “lilypond” source package in Saucy: Fix Committed Status in “texlive-bin” source package in Saucy: Fix Committed Bug description: [ Description ] metafont / metapost in texlive-binaries shipped with 13.10 is broken. It renders characters incorrectly and breaks note flags. [ Proposed fix ] Update metapost to 1.803, the next upstream release after the one we're shipping. It only contains two bug fixes - from the changelog: 2013-05-22 Taco Hoekwater <t...@luatex.org> * svgout.w: fix a problem with overly large characters in SVG output mode when prologues != 3. * mp.w: quick fix for a fatal crash during free-ing of TFM metric data at the end of the run. pmpost (Debian patch) needs updating too; this was taken from Debian's git repository. lilypond needs a no-change rebuild with the new texlive-binaries after that is accepted. [ QA ] Download https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+attachment/3891750/+files /ubuntu-example.ly Process it with $ lilypond ubuntu-example.ly Compare the output to comments #5 and #6 on this bug to see if it is correct. [ Regression potential ] Bug fixes only. Check that metapost still works. Wait 14 days before releasing the package from -proposed. [ Original report ] The current build is done with a version of Metafont that is known to be broken. Every single file produced by this compilation of LilyPond has a spectacularly broken treble clef at the start of each line, and most note flags are quite broken as well. The current developer version for LilyPond (2.17.29) refuses to compile with the broken Metafont version. Unfortunately, 2.16.2 does not yet contain the respective check. Metafont versions announcing itself as anything between 1.600 and 1.802 (inclusively) are broken. The currently distributed version of Metafont with Ubuntu is 1.802. Since this affects _every_ output file produced by LilyPond, this bug is _critical_. The texlive-binaries package needs to get updated (Debian already did so), and preferably the build dependencies must reflect the inability of building a working version of LilyPond with the current version of texlive-binaries, which is 2013.20130529.30792-1build2. The corresponding bug in texlive-bin is https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1220653 which has not seen a lot of interest. This build of LilyPond has to be withdrawn as _fast_ _as_ _possible_. It is not possible to typeset music of useful quality with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
