lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patchy email


From: David Kastrup
Subject: Re: Patchy email
Date: Wed, 18 Jan 2012 11:58:53 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux)

Graham Percival <address@hidden> writes:

> On Wed, Jan 18, 2012 at 02:20:09AM -0800,
> address@hidden wrote:
>> *** FAILED BUILD ***
>> 
>>      nice make doc -j3 CPU_COUNT=3
>> 
>>      Previous good commit:   11cf086eaba246f043d553a8bafcdbf1b47b9117
>> 
>>      Current broken commit:  b667b7fe1bf651b7373014204edbe0e68f17326e
>
>
> /main/large-tmp/lilypond-autobuild/build/out/lybook-db/d5/lily-6e11c268.ly:1115:4:
> error: unknown escaped string: `\autoFootnoteGrob'

Culprit would be
commit 44f3e55e3c283ccfdcb32af3ba3f45ec8580ca23
Author: Yoshiki Sawada <address@hidden>
Date:   Sun Jan 15 09:00:54 2012 +0900

    Doc-ja: Adding and updating NR
    
    Doc-ja: Adding and updating NR.


merged in from the translation branch.

This is somewhat unfortunate: the newly created translation refers to a
version that has been semi-fixed after a syntax change by running
scripts/auxiliar/update-with-convert-ly.sh, and corrected afterwards.

It would seem that rerunning scripts/auxiliar/update-with-convert-ly.sh
after merging the translation might have fixed that problem this time.

I am not sure it would work in all such cases.

I don't have a better suggestion than doing a test run before pushing a
translation merge.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]