Fonts are spectacularly broken

Bug #1243777 reported by David Kastrup on 2013-10-23
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
lilypond (Ubuntu)
Undecided
Unassigned
Saucy
Undecided
Unassigned
texlive-bin (Ubuntu)
Undecided
Unassigned
Saucy
Undecided
Unassigned

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 <email address hidden>

        * 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.

David Kastrup (dak) wrote :

Correction: this concerns the MetaPost version (/usr/bin/mpost).

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lilypond (Ubuntu):
status: New → Confirmed
Changed in texlive-bin (Ubuntu):
status: New → Confirmed
Joseph Wakeling (webdrake) wrote :

The attached is a simple lilypond example file to test any fix for this bug. Simply copy to a directory and then,

    lilypond ubuntu-example.ly

... to produce .ps and .pdf output.

Joseph Wakeling (webdrake) wrote :

This next attachment is Lilypond output produced with the current 13.10 Lilypond package, showing the visible impact of the mpost problem. The treble clef (the curvy symbol on the leftmost part of the music) is misshapen.

Joseph Wakeling (webdrake) wrote :

This second example shows correct Lilypond output with a correctly-formed treble clef, built using Lilypond built from deb source with a fixed mpost.

To reproduce:

   (i) install updated texlive-binaries from https://launchpad.net/~laney/+archive/experimental/ (contains fixed mpost)

   (ii) apt-get source lilypond; cd lilypond-2.16.2; ./configure && make

   (iii) out/bin/lilypond ubuntu-example.ly

Joseph Wakeling (webdrake) wrote :

Note that all the lilypond packages will need rebuilding from this, i.e. lilypond, lilypond-data, lilypond-doc, lilypond-doc-*.

Iain Lane (laney) on 2013-10-27
description: updated
description: updated
Iain Lane (laney) wrote :

Uploaded to saucy-proposed.

SRU team, it's not techincally a minimal backport for this bug. But the other fixes are bug fixes (arguably serious, although I don't have enough context to reproduce / assess that myself; doing this SRU on a personal request) so I hope you can accept regardless. Require an extended testing period if you think that's warranted.

Joseph Wakeling (webdrake) wrote :

Thanks Iain! :-)

Iain Lane (laney) on 2013-10-28
Changed in texlive-bin (Ubuntu):
status: Confirmed → Fix Released
Changed in texlive-bin (Ubuntu Saucy):
status: New → In Progress
Iain Lane (laney) on 2013-10-28
Changed in lilypond (Ubuntu Saucy):
status: New → In Progress
Brian Murray (brian-murray) wrote :

I'll go ahead and accept this but let's wait two weeks for any issues to appear on the error tracker or in Launchpad.

Changed in texlive-bin (Ubuntu Saucy):
status: In Progress → Fix Committed
tags: added: verification-needed

Hello David, or anyone else affected,

Accepted texlive-bin into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/texlive-bin/2013.20130529.30792-1ubuntu1 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!

description: updated
Benkő Pál (benko-pal) wrote :

2013.20130529.30792-1ubuntu1 fixed the bug for me; as I'm not the original reporter, I didn't change the tag.

Miklos Juhasz (mjuhasz) on 2013-11-01
tags: added: verification-done
removed: verification-needed
Joseph Wakeling (webdrake) wrote :

Yes, the package in saucy-proposed fixes the mpost problem. Bear in mind that lilypond will need to be rebuilt using the updated texlive-bin in order to benefit from it.

Brian Murray (brian-murray) wrote :

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
Joseph Wakeling (webdrake) wrote :

I installed the updated versions of lilypond, lilypond-data, lilypond-doc-html and lilypond-doc-pdf from saucy-proposed. Lilypond now produces correct output, and the fonts in the documentation are correct too. I haven't checked the non-English Lilypond documentation.

Joseph Wakeling (webdrake) wrote :

I've checked through the international documentation too, i.e. lilypond-doc-html-* and lilypond-doc-pdf-*. It all also looks OK, so appears that the bug is indeed fixed by these packages.

Miklos Juhasz (mjuhasz) on 2013-11-02
tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package texlive-bin - 2013.20130529.30792-1ubuntu1

---------------
texlive-bin (2013.20130529.30792-1ubuntu1) saucy; urgency=low

  * Import metapost bugfix release 1.803 to fix crash and bad font rendering
    in lilypond (LP: #1243777)
  * Update pmpost correspondingly (backport from Debian)
 -- Iain Lane <email address hidden> Fri, 25 Oct 2013 11:55:18 +0100

Changed in texlive-bin (Ubuntu Saucy):
status: Fix Committed → Fix Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lilypond - 2.16.2-2build0.1

---------------
lilypond (2.16.2-2build0.1) saucy; urgency=low

  * No-change rebuild against fixed mpost (LP: #1243777)
  * Add BD on texlive-binaries (formerly transitive) to build against the
    SRUed version.
 -- Iain Lane <email address hidden> Mon, 28 Oct 2013 17:57:18 +0000

Changed in lilypond (Ubuntu Saucy):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers