Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20991 - [fontforge] Regression that create problems with LilyPond build
Attached to Project:
Arch Linux
Opened by Patrick McCarty (pnorcks) - Wednesday, 29 September 2010, 18:20 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 30 September 2010, 19:52 GMT
Opened by Patrick McCarty (pnorcks) - Wednesday, 29 September 2010, 18:20 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 30 September 2010, 19:52 GMT
|
DetailsDescription:
lilypond 2.12.3-4 was built with fontforge 20100501-1, but this fontforge version has a serious regression, causing LilyPond's custom fonts to build incorrectly. Originally reported here: https://bbs.archlinux.org/viewtopic.php?pid=832685 The LilyPond team is using a CVS snapshot of fontforge in order to work around these issues until a new version of fontforge is released. The attached patch incorporates some upstream changes in fontforge, and it seems to fix the regression. I have tested a lilypond build with a patched fontforge, and I haven't noticed any defects with the font generation. Package version: 20100501-1 |
This task depends upon
spline-fixes.patch
Could you please confirm that it fixes this bug when it does?
I've opened a new issue to track the rebuild: https://bugs.archlinux.org/task/21006