David Kastrup <d...@gnu.org> writes: >>>> \shape >>>> Slur #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) >>>> /media/IntelSSD/patchybuild/autobuild/build/out/lybook-db/61/lily-1564b6f0.ly:144:12: >>>> error: wrong type for argument 2. Expecting string or music, found >>>> ((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) >>>> \shape Slur >>>> #'((-0.5 . 1.5) (-3 . 0) (0 . 0) (0 . 0)) >>>> Interpreting music... >>>> >>>> [snip] >>>> >>>> fatal error: failed files: "61/lily-1564b6f0.ly" >>>> >>>> I presume 220f439edbd95266113248a984ebe6c4b97dcf14 is the culprit. >>> >>> Huh. This should have been caught by running convert-ly and I have no >>> idea why it didn't. I'll back the shape change out of staging (rebasing >>> the other commits in the process) and investigate what went wrong here. >>> >>> It is quite strange since a number of very similar lines converted just >>> fine. >> >> Do you need any more info on the identity of the failing file? > > No. git grep works just fine for finding those. It is more than one.
No, just one. Documentation/es/changes.tely. Seems like the Spanish change file is the only one left at 2.16 state (the others being either older or younger), and apparently the change files don't have LilyPond version numbers, and thus are not converted by convert-ly. Huh. I'll probably convert it manually, causing a merge conflict later when the translation branch gets updated. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
