Is the working `post-tl13 bug-fix rebuild' of the binaries (as found
in the current TeXLive SVN) based on metapost 1.803?
Yes. Just run mpost --version.
And do you know which metapost version introduced this bug?
I don't know.
As far as TL goes, there were no releases of mpost between TL'12 and
TL'13. We did not do any bug-fix binaries in 2012 (and I sincerely hope
we never have to again). So all I can say is that mpost 1.802, the
original TL 2013 binary, has the bug. The TL'12 version was 1.504.
I suggest that we exclude the affected mpost versions in lilypond's
configure script.
Makes sense to me, FWIW. That's the only thing you can control. None
of us control what the distros do, and even if they changed, plenty of
users would still have the bad version(s).
Best,
karl
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
