On 23/10/13 18:22, David Kastrup wrote:
Of course, this was sort of predictable. Would we have been in time if we had immediately created a backport of the configure patch and named the result 2.16.3?
I think it would depend on when you got it out by. As far as I can tell Ubuntu just imports Lilypond direct from Debian Unstable and doesn't make any direct intervention in it. I don't think there's even a volunteer contributor who takes any responsibility (which there is for e.g. Frescobaldi).
There have been a bunch of occasions in the past when Ubuntu hasn't picked up on an upgraded stable release of Lilypond despite it being available, for exactly this reason.
_______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
