| 2013-10-23 16:12:34 |
David Kastrup |
bug |
|
|
added bug |
| 2013-10-23 16:29:56 |
Launchpad Janitor |
lilypond (Ubuntu): status |
New |
Confirmed |
|
| 2013-10-23 17:00:15 |
James |
bug |
|
|
added subscriber James |
| 2013-10-24 13:26:10 |
Benkő Pál |
bug |
|
|
added subscriber Benkő Pál |
| 2013-10-24 15:04:08 |
Joseph Wakeling |
bug |
|
|
added subscriber Joseph Wakeling |
| 2013-10-24 16:46:13 |
Joseph Wakeling |
bug task added |
|
texlive-bin (Ubuntu) |
|
| 2013-10-25 08:15:48 |
Launchpad Janitor |
texlive-bin (Ubuntu): status |
New |
Confirmed |
|
| 2013-10-25 08:16:33 |
Francisco Vila |
bug |
|
|
added subscriber Francisco Vila |
| 2013-10-26 09:53:05 |
Joseph Wakeling |
attachment added |
|
Simple Lilypond input file to test fix https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+attachment/3891750/+files/ubuntu-example.ly |
|
| 2013-10-26 10:06:13 |
Joseph Wakeling |
attachment added |
|
Example of incorrect Lilypond output produced with current 13.10 lilypond package https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+attachment/3891759/+files/ubuntu-example-wrong.pdf |
|
| 2013-10-26 10:09:47 |
Joseph Wakeling |
attachment added |
|
Example of correct Lilypond output produced with lilypond built with fixed mpost https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+attachment/3891760/+files/ubuntu-example-correct.pdf |
|
| 2013-10-27 17:08:41 |
Iain Lane |
description |
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 ]
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 <taco@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. |
|
| 2013-10-27 17:10:07 |
Iain Lane |
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 <taco@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 ]
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 <taco@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.
[ 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. |
|
| 2013-10-28 16:56:36 |
Iain Lane |
nominated for series |
|
Ubuntu Saucy |
|
| 2013-10-28 16:56:36 |
Iain Lane |
bug task added |
|
lilypond (Ubuntu Saucy) |
|
| 2013-10-28 16:56:36 |
Iain Lane |
bug task added |
|
texlive-bin (Ubuntu Saucy) |
|
| 2013-10-28 16:56:48 |
Iain Lane |
texlive-bin (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2013-10-28 16:56:54 |
Iain Lane |
texlive-bin (Ubuntu Saucy): status |
New |
In Progress |
|
| 2013-10-28 18:23:19 |
Iain Lane |
lilypond (Ubuntu Saucy): status |
New |
In Progress |
|
| 2013-10-28 18:29:02 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/trusty-proposed/lilypond |
|
| 2013-10-31 15:45:10 |
Brian Murray |
texlive-bin (Ubuntu Saucy): status |
In Progress |
Fix Committed |
|
| 2013-10-31 15:45:13 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2013-10-31 15:45:18 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2013-10-31 15:45:20 |
Brian Murray |
tags |
|
verification-needed |
|
| 2013-10-31 15:46:11 |
Brian Murray |
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 <taco@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.
[ 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 ]
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 <taco@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. |
|
| 2013-11-01 11:30:25 |
Miklos Juhasz |
tags |
verification-needed |
verification-done |
|
| 2013-11-01 17:41:53 |
Brian Murray |
lilypond (Ubuntu Saucy): status |
In Progress |
Fix Committed |
|
| 2013-11-01 17:41:58 |
Brian Murray |
tags |
verification-done |
|
|
| 2013-11-01 17:42:00 |
Brian Murray |
tags |
|
verification-needed |
|
| 2013-11-01 17:55:35 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/lilypond |
|
| 2013-11-02 12:55:29 |
Miklos Juhasz |
tags |
verification-needed |
verification-done |
|
| 2013-11-07 16:38:34 |
Launchpad Janitor |
texlive-bin (Ubuntu Saucy): status |
Fix Committed |
Fix Released |
|
| 2013-11-07 16:38:39 |
Stéphane Graber |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-11-13 00:52:08 |
Launchpad Janitor |
lilypond (Ubuntu Saucy): status |
Fix Committed |
Fix Released |
|
