broken mpost binary from TeXLive (was: broken clef glyph)

[Werner LEMBERG]

Karl, Taco,


we are talking about the mpost bug I've reported as

  http://tug.org/mailman/htdig/tex-live/2013-May/033640.html

and which has been fixed meanwhile in TeXLive SVN (including
binaries).  The problem is that both Debian and Fedora currently ship
broken binaries since they probably base their TeXLive distributions
on the `TeXLive 2013' tag, which was used to produce the TeXLive DVDs.

>>>> If this bug of TeXlive will persist into stable GNU/Linux
>>>> distributions, it will likely have a devastating effect on
>>>> LilyPond's reputation.  It's not just the clef glyph that is
>>>> prominently broken, but also a number of other frequent glyphs
>>>> like the flags.
>>>
>>> Indeed.  While I had reported the bug before releasing TeXLive
>>> 2013, IIRC, it was not possible to stop the release process
>>> (again).
>>>
>>> I sincerely hope that both Debian and Fedora are going to use the
>>> *current* TeXLive version (from the SVN).
> 
> Well is there something we can do in terms of damage limitation
> (reputation and emails to address@hidden) such that the 'make files'
> or the binary, or whatever can detect the fact that we have a bad
> version of whatever it is that is causing this and display
> something?

I suggest that we exclude the affected mpost versions in lilypond's
configure script.

Is the working `post-tl13 bug-fix rebuild' of the binaries (as found
in the current TeXLive SVN) based on metapost 1.803?  And do you know
which metapost version introduced this bug?  I know that TeXLive SVN
r26509 (for TeXLive 2012) works just fine.


    Werner