** Description changed:

+ [ 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.
+ 
+ [ Regression potential ]
+ 
+ Bug fixes only. Check that metapost still works.
+ 
+ [ 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.

** Description changed:

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243777

Title:
  Fonts are spectacularly broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to