On Sat, Nov 27, 2010 at 18:10:18 -0800, Don Armstrong wrote: > On Sat, 27 Nov 2010, Julien Cristau wrote: > > On Fri, Nov 26, 2010 at 15:52:21 -0800, Don Armstrong wrote: > > > The fix is to unblock lilypond. The only reason it didn't make it > > > in for the freeze were the failures of fontforge brought about by > > > a new version. > > > > Unblocking lilypond is not going to help until we can get it built > > on s390. > > That's why I haven't asked for an unblock yet. There is a patch that > may resolve that problem on s390 that needs to be tested (and also > needs a response from the maintainers of fontforge.) > > I haven't had time to go deep into the problem besides creating a > smaller test case. See #594629 and the work that Nico Tyni has done; I > think he may be closest to a patch. > > Christian/Kęstutis: can you look at the patch and see if it's > something that you'd be willing to make an new upload with? [I'll try > to get a test in with a new fontforge on s390 if you'd be willing to > upload a package with it, assuming that it fixes the problem.] > lilypond built on s390 with the new fontforge. I unblocked both. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature