Am So., 19. Apr. 2020 um 21:59 Uhr schrieb Jonas Hahnfeld :
>
> Am Sonntag, den 19.04.2020, 18:20 + schrieb Valentin Villenave:
> > On 4/19/20, David Kastrup <
> > d...@gnu.org
> > > wrote:
> > > mkstemp! does not generate a string. It overwrites an existing string
> > > in-place, and that's b
Am Sonntag, den 19.04.2020, 18:20 + schrieb Valentin Villenave:
> On 4/19/20, David Kastrup <
> d...@gnu.org
> > wrote:
> > mkstemp! does not generate a string. It overwrites an existing string
> > in-place, and that's bad news for a literal string.
>
> Yes, it overwrite the string, opens a p
Am Sonntag, den 19.04.2020, 20:57 +0200 schrieb David Kastrup:
> Jonas Hahnfeld writes:
> > So I guess the fix is to delete the (temporary) directory and all
> > contained files? And maybe putting it under /tmp?
> >
> > Oh, and ignore my comment that I had tested this with Guile 2.2. Looks
> > li
Jonas Hahnfeld writes:
> Am Sonntag, den 19.04.2020, 20:03 +0200 schrieb David Kastrup:
>> David Kastrup <
>> d...@gnu.org
>> > writes:
>>
>> > David Kastrup <
>> > d...@gnu.org
>> > > writes:
>> >
>> > > David Kastrup <
>> > > d...@gnu.org
>> > > > writes:
>> > >
>> > > > Valentin Villenave <
Valentin Villenave writes:
> On 4/19/20, David Kastrup wrote:
>> mkstemp! does not generate a string. It overwrites an existing string
>> in-place, and that's bad news for a literal string.
>
> Yes, it overwrite the string,
You can/must not override a literal string. It's read-only.
> opens
Am Sonntag, den 19.04.2020, 20:03 +0200 schrieb David Kastrup:
> David Kastrup <
> d...@gnu.org
> > writes:
>
> > David Kastrup <
> > d...@gnu.org
> > > writes:
> >
> > > David Kastrup <
> > > d...@gnu.org
> > > > writes:
> > >
> > > > Valentin Villenave <
> > > > valen...@villenave.net
> > > >
>>> Does anybody have an idea _what_ and _why_ would leave a .uuid
>>> file lying around in the temporary file with, well, an uuid kind
>>> of number in it? Is that an artifact of my freetype library or
>>> something?
Definitely not FreeType, but...
>> Seems to be something that fontconfig doe
On 4/19/20, David Kastrup wrote:
> mkstemp! does not generate a string. It overwrites an existing string
> in-place, and that's bad news for a literal string.
Yes, it overwrite the string, opens a port, then I read the
port-filename which should be an _other_ string object, shouldn’t it?
(sigh -
On 4/19/20, David Kastrup wrote:
> So I am afraid that things are rather weird at my side:
> -rw-r--r-- 1 dak dak 36 Apr 19 19:51 .uuid
> dak@lola:/usr/local/tmp/lilypond2$ cat dummyfont-C5PUYM-dir/.uuid
> 35d52a4b-44f7-41b6-afca-165a4187aa4f
WTF. Could it be some trace left due to your filesy
Valentin Villenave writes:
> On 4/19/20, David Kastrup wrote:
>> You need (mkstemp! (string-copy "...
>> because mkstemp! overrides the string.
>
> Why, yes. What I want to copy is precisely the mkstemp-generated
> string. What did I miss?
mkstemp! does not generate a string. It overwrites an
On 4/19/20, David Kastrup wrote:
> You need (mkstemp! (string-copy "...
> because mkstemp! overrides the string.
Why, yes. What I want to copy is precisely the mkstemp-generated
string. What did I miss?
V.
David Kastrup writes:
> David Kastrup writes:
>
>> David Kastrup writes:
>>
>>> Valentin Villenave writes:
>>>
On 4/19/20, David Kastrup wrote:
> Note that the delete-file instructions are executed while the book is
> being read in while markup is typeset when the books are being
David Kastrup writes:
> David Kastrup writes:
>
>> Valentin Villenave writes:
>>
>>> On 4/19/20, David Kastrup wrote:
Note that the delete-file instructions are executed while the book is
being read in while markup is typeset when the books are being processed
at the end of the
David Kastrup writes:
> Valentin Villenave writes:
>
>> On 4/19/20, David Kastrup wrote:
>>> Note that the delete-file instructions are executed while the book is
>>> being read in while markup is typeset when the books are being processed
>>> at the end of the input file.
>>
>> Yes, it looked
Valentin Villenave writes:
> On 4/19/20, David Kastrup wrote:
>> ERROR: In procedure mkstemp!:
>> string is read-only: "kaka-XX"
>
> Could the following help?
>
> diff --git a/input/regression/font-name-add-files.ly
> b/input/regression/font-name-add-files.ly
> index 33f73f0c68..264e2b6532
Valentin Villenave writes:
> On 4/19/20, David Kastrup wrote:
>> Note that the delete-file instructions are executed while the book is
>> being read in while markup is typeset when the books are being processed
>> at the end of the input file.
>
> Yes, it looked completely bonkers to me as well,
On 4/19/20, David Kastrup wrote:
> Note that the delete-file instructions are executed while the book is
> being read in while markup is typeset when the books are being processed
> at the end of the input file.
Yes, it looked completely bonkers to me as well, until I realized it worked :-)
> No
On 4/19/20, David Kastrup wrote:
> ERROR: In procedure mkstemp!:
> string is read-only: "kaka-XX"
Could the following help?
diff --git a/input/regression/font-name-add-files.ly
b/input/regression/font-name-add-files.ly
index 33f73f0c68..264e2b6532 100644
--- a/input/regression/font-name-add
Jonas Hahnfeld writes:
> Am Sonntag, den 19.04.2020, 19:07 +0200 schrieb David Kastrup:
>> Jonas Hahnfeld <
>> hah...@hahnjo.de
>> > writes:
>>
>> > Am Sonntag, den 19.04.2020, 18:59 +0200 schrieb David Kastrup:
>> > > pat...@gnu.org
>> > >
>> > > writes:
>> > >
>> > > > 16:36:18 (UTC) Begin
Am Sonntag, den 19.04.2020, 19:07 +0200 schrieb David Kastrup:
> Jonas Hahnfeld <
> hah...@hahnjo.de
> > writes:
>
> > Am Sonntag, den 19.04.2020, 18:59 +0200 schrieb David Kastrup:
> > > pat...@gnu.org
> > >
> > > writes:
> > >
> > > > 16:36:18 (UTC) Begin LilyPond compile, previous commit at
Jonas Hahnfeld writes:
> Am Sonntag, den 19.04.2020, 18:59 +0200 schrieb David Kastrup:
>> pat...@gnu.org
>> writes:
>>
>> > 16:36:18 (UTC) Begin LilyPond compile, previous commit at
>> > 12bf65758f33510e6b8e6e4d4a91bb1ebb459248
>> > 16:36:21 From ssh://git.sv.gnu.org/srv/git/lilypond
>> >
Am Sonntag, den 19.04.2020, 18:59 +0200 schrieb David Kastrup:
> pat...@gnu.org
> writes:
>
> > 16:36:18 (UTC) Begin LilyPond compile, previous commit at
> > 12bf65758f33510e6b8e6e4d4a91bb1ebb459248
> > 16:36:21 From ssh://git.sv.gnu.org/srv/git/lilypond
> >12bf65758f..0cfef7069e master
pat...@gnu.org writes:
> 16:36:18 (UTC) Begin LilyPond compile, previous commit at
> 12bf65758f33510e6b8e6e4d4a91bb1ebb459248
> 16:36:21 From ssh://git.sv.gnu.org/srv/git/lilypond
>12bf65758f..0cfef7069e master -> origin/master
>12bf65758f..0cfef7069e staging-> origin/stagin
16:36:18 (UTC) Begin LilyPond compile, previous commit at
12bf65758f33510e6b8e6e4d4a91bb1ebb459248
16:36:21 From ssh://git.sv.gnu.org/srv/git/lilypond
12bf65758f..0cfef7069e master -> origin/master
12bf65758f..0cfef7069e staging-> origin/staging
16:36:27 Merged staging, now a
14:41:10 (UTC) Begin LilyPond compile, previous commit at
1dd353f70131eabd43a1b6455d6d05b58fb9db79
14:41:19 Merged staging, now at:1dd353f70131eabd43a1b6455d6d05b58fb9db79
14:41:19Success:./autogen.sh --noconfigure
14:41:33Success:/tmp/
On 3/25/20, Werner LEMBERG wrote:
> Oops, I gave wrong advice, sorry.
You’re not the one to blame; I was the one who jumped the gun.
> Please do
> s/@example/@samp/
> and re-commit.
Done. Aand this is why we have a patch reviewing process. Lesson
learned. (Again.)
V.
> makeinfo.notation.log states:
>
> out/notation/rhythms.texi:1961: misplaced {
> out/notation/rhythms.texi:1961: misplaced }
>
> The respective line appears to be:
>
> the note name uppercase @example{R}. Their duration is entered
>
> @example is not an in-text command but rather an env
pat...@gnu.org writes:
> 22:26:26 (UTC) Begin LilyPond compile, previous commit at
> 83045b846acb4aaadf54373941a915c4c45fb522
> 22:26:34 Merged staging, now at: 83045b846acb4aaadf54373941a915c4c45fb522
> 22:26:35 Success:./autogen.sh --noconfigure
> 22:26:47 Suc
22:26:26 (UTC) Begin LilyPond compile, previous commit at
83045b846acb4aaadf54373941a915c4c45fb522
22:26:34 Merged staging, now at:83045b846acb4aaadf54373941a915c4c45fb522
22:26:35Success:./autogen.sh --noconfigure
22:26:47Success:/tmp/
pkx1...@posteo.net writes:
> David,
>
> On 07/03/2020 00:59, David Kastrup wrote:
>> David Kastrup writes:
>>
>>> pat...@gnu.org writes:
>>>
23:42:58 (UTC) Begin LilyPond compile, previous commit at
bf6f650dbc16cb33181501eee2aca082a5a5e3ef
23:43:05 Merged staging, now at: bf6f6
David,
On 07/03/2020 00:59, David Kastrup wrote:
David Kastrup writes:
pat...@gnu.org writes:
23:42:58 (UTC) Begin LilyPond compile, previous commit at
bf6f650dbc16cb33181501eee2aca082a5a5e3ef
23:43:05 Merged staging, now at:bf6f650dbc16cb33181501eee2aca082a5a5e3ef
23:43:06
David Kastrup writes:
> pat...@gnu.org writes:
>
>> 23:42:58 (UTC) Begin LilyPond compile, previous commit at
>> bf6f650dbc16cb33181501eee2aca082a5a5e3ef
>> 23:43:05 Merged staging, now at: bf6f650dbc16cb33181501eee2aca082a5a5e3ef
>> 23:43:06 Success:./autogen.sh --noc
David Kastrup writes:
> pat...@gnu.org writes:
>
>> 23:42:58 (UTC) Begin LilyPond compile, previous commit at
>> bf6f650dbc16cb33181501eee2aca082a5a5e3ef
>> 23:43:05 Merged staging, now at: bf6f650dbc16cb33181501eee2aca082a5a5e3ef
>> 23:43:06 Success:./autogen.sh --noc
pat...@gnu.org writes:
> 23:42:58 (UTC) Begin LilyPond compile, previous commit at
> bf6f650dbc16cb33181501eee2aca082a5a5e3ef
> 23:43:05 Merged staging, now at: bf6f650dbc16cb33181501eee2aca082a5a5e3ef
> 23:43:06 Success:./autogen.sh --noconfigure
> 23:43:18 Suc
David Kastrup writes:
> pat...@gnu.org writes:
>
>> 23:08:39 (UTC) Begin LilyPond compile, previous commit at
>> 825dd87d0b1b58e56d7c66ef1fc1dd672d913c84
>> 23:08:41 Auto packing the repository in background for optimum performance.
>> See "git help gc" for manual housekeeping.
>> 23:08:47 Me
pat...@gnu.org writes:
> 23:08:39 (UTC) Begin LilyPond compile, previous commit at
> 825dd87d0b1b58e56d7c66ef1fc1dd672d913c84
> 23:08:41 Auto packing the repository in background for optimum performance.
> See "git help gc" for manual housekeeping.
> 23:08:47 Merged staging, now at: 825d
23:08:39 (UTC) Begin LilyPond compile, previous commit at
825dd87d0b1b58e56d7c66ef1fc1dd672d913c84
23:08:41 Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
23:08:47 Merged staging, now at:825dd87d0b1b58e56d7c66ef1fc1dd672d
10:35:17 (UTC) Begin LilyPond compile, previous commit at
b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:35:20 Merged staging, now at:b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:35:21Success:./autogen.sh --noconfigure
10:35:34Success:/tmp/
David Kastrup writes:
> Knut Petersen writes:
>
>> On 26.07.19 20:36, David Kastrup wrote:
>>>
Unless Knut is also running patchy now that he has commit access (and
perhaps didn't have a clean master?).
(I don't want to cast aspersions, but it might be a genuine mistake if
>>
On 30.07.19 01:39, David Kastrup wrote:
No, that make test needs a fix. make test is supposed to test the
version in the work directory, not some weird amalgamate between system
installed version and work directory version.
Any idea what would be required here?
Yes.
https://codereview.appsp
On 30.07.19 01:39, David Kastrup wrote:
Stracing shows that after 'make all' it is also necessary to execute
'make install' prior to 'make test-baseline' or 'make test-clean'.
That's insane. Having to install LilyPond before being able to test it
makes no sense.
During regression testing we
Knut Petersen writes:
> On 29.07.19 17:55, David Kastrup wrote:
>> Well, it is rather obvious that you should not be seeing failure with
>> unchanged master (assuming that you have some reasonably current Python
>> on your system) and I should not be seeing failure with your patch
>> (assuming th
On 29.07.19 17:55, David Kastrup wrote:
Well, it is rather obvious that you should not be seeing failure with
unchanged master (assuming that you have some reasonably current Python
on your system) and I should not be seeing failure with your patch
(assuming that it tests out on your system: the
Knut Petersen writes:
> On 29.07.19 16:27, David Kastrup wrote:
>> And here are the results from a freshly cloned tree: with your patch,
>> test-baseline fails. Without it, it succeeds.
>
> Thanks. The other way round here.
>
>> Would any log files help? I can rerun make test (both successfully
Knut Petersen writes:
> On 29.07.19 16:27, David Kastrup wrote:
>> And here are the results from a freshly cloned tree: with your patch,
>> test-baseline fails. Without it, it succeeds.
>
> Thanks. The other way round here.
>
>> Would any log files help? I can rerun make test (both successfully
On 29.07.19 16:27, David Kastrup wrote:
And here are the results from a freshly cloned tree: with your patch,
test-baseline fails. Without it, it succeeds.
Thanks. The other way round here.
Would any log files help? I can rerun make test (both successfully and
unsuccessfully) with redirecte
David Kastrup writes:
> Knut Petersen writes:
>
>> Hi David!
>>
>> Thank you for the information you provided. Something is really broken,
>> but after quite some time of debugging, I'm beginning to wonder if it really
>> is my patch / system or if it might be that origin/master is broken after
Knut Petersen writes:
> Hi David!
>
> Thank you for the information you provided. Something is really broken,
> but after quite some time of debugging, I'm beginning to wonder if it really
> is my patch / system or if it might be that origin/master is broken after all.
>
> Could you please verify
Hi David!
Thank you for the information you provided. Something is really broken,
but after quite some time of debugging, I'm beginning to wonder if it really
is my patch / system or if it might be that origin/master is broken after all.
Could you please verify if (after adapting the arguments
James writes:
> Hello,
>
> On 27/07/2019 10:10, David Kastrup wrote:
>> James writes:
>>
>>> On 26/07/2019 19:36, David Kastrup wrote:
...
I run Patchy when I notice something went to staging. Due to its cost,
I tend to abort it when I discover someone else pushing before me.
>>>
Hello,
On 27/07/2019 10:10, David Kastrup wrote:
James writes:
On 26/07/2019 19:36, David Kastrup wrote:
...
I run Patchy when I notice something went to staging. Due to its cost,
I tend to abort it when I discover someone else pushing before me.
So it would appear that your repository (an
James writes:
> On 26/07/2019 19:36, David Kastrup wrote:
>> ...
>> I run Patchy when I notice something went to staging. Due to its cost,
>> I tend to abort it when I discover someone else pushing before me.
>>
>> So it would appear that your repository (and probably that of Knut) have
>> a loc
On 26/07/2019 19:36, David Kastrup wrote:
...
I run Patchy when I notice something went to staging. Due to its cost,
I tend to abort it when I discover someone else pushing before me.
So it would appear that your repository (and probably that of Knut) have
a local master branch which would mas
Knut Petersen writes:
> On 27.07.19 07:56, David Kastrup wrote:
>>
>>> What happened to the musicxml2ly patch? It vanished from staging.
>>> Shall I push it again?
>> It didn't pass patchy testing on my computer with failures in the
>> musicxml files. So it appears to have a problem with, uh, Py
On 27.07.19 07:56, David Kastrup wrote:
What happened to the musicxml2ly patch? It vanished from staging.
Shall I push it again?
It didn't pass patchy testing on my computer with failures in the
musicxml files. So it appears to have a problem with, uh, Python
2.7.16+ (according to python --ve
Knut Petersen writes:
> On 26.07.19 20:36, David Kastrup wrote:
>>
>>> Unless Knut is also running patchy now that he has commit access (and
>>> perhaps didn't have a clean master?).
>>>
>>> (I don't want to cast aspersions, but it might be a genuine mistake if
>>> it was Knut). Knut?
>> I rather
On 26.07.19 20:36, David Kastrup wrote:
Unless Knut is also running patchy now that he has commit access (and
perhaps didn't have a clean master?).
(I don't want to cast aspersions, but it might be a genuine mistake if
it was Knut). Knut?
I rather doubt that it was Knut since I mentioned the
James writes:
> Hello,
>
> On 26/07/2019 16:13, David Kastrup wrote:
>> David Kastrup writes:
>>
>>> David Kastrup writes:
>>>
fatal: Not a valid object name master
Apparently, the patch from
commit 7583351fbf2f08a4d1f3f0b075fe8b691adc0b95
Author: Knut Petersen
Da
Hello,
On 26/07/2019 16:13, David Kastrup wrote:
David Kastrup writes:
David Kastrup writes:
fatal: Not a valid object name master
Apparently, the patch from
commit 7583351fbf2f08a4d1f3f0b075fe8b691adc0b95
Author: Knut Petersen
Date: Sun Jul 7 13:16:05 2019 +0200
Optimize tree.gi
pat...@gnu.org writes:
> 15:04:59 (UTC) Begin LilyPond compile, previous commit at
> 95a26f04acfa14068edff2d4457bfeca12ad80fc
> 15:05:03 Merged staging, now at: 95a26f04acfa14068edff2d4457bfeca12ad80fc
> 15:05:03 Success:./autogen.sh --noconfigure
> 15:05:19 Suc
15:04:59 (UTC) Begin LilyPond compile, previous commit at
95a26f04acfa14068edff2d4457bfeca12ad80fc
15:05:03 Merged staging, now at:95a26f04acfa14068edff2d4457bfeca12ad80fc
15:05:03Success:./autogen.sh --noconfigure
15:05:19Success:/tmp/
David Kastrup writes:
> David Kastrup writes:
>
>> fatal: Not a valid object name master
>>
>> Apparently, the patch from
>> commit 7583351fbf2f08a4d1f3f0b075fe8b691adc0b95
>> Author: Knut Petersen
>> Date: Sun Jul 7 13:16:05 2019 +0200
>>
>> Optimize tree.gittxt messages
>>
>> W
David Kastrup writes:
> pat...@gnu.org writes:
>
>> 14:39:40 (UTC) Begin LilyPond compile, previous commit at
>> 1c51a616e289fffb918942c8f1e189ab50809157
>> 14:39:51 Merged staging, now at: 1c51a616e289fffb918942c8f1e189ab50809157
>> 14:39:52 Success:./autogen.sh --noc
pat...@gnu.org writes:
> 14:39:40 (UTC) Begin LilyPond compile, previous commit at
> 1c51a616e289fffb918942c8f1e189ab50809157
> 14:39:51 Merged staging, now at: 1c51a616e289fffb918942c8f1e189ab50809157
> 14:39:52 Success:./autogen.sh --noconfigure
> 14:40:08 Suc
14:39:40 (UTC) Begin LilyPond compile, previous commit at
1c51a616e289fffb918942c8f1e189ab50809157
14:39:51 Merged staging, now at:1c51a616e289fffb918942c8f1e189ab50809157
14:39:52Success:./autogen.sh --noconfigure
14:40:08Success:/tmp/
David,
On Thu, 13 Jun 2019 10:03:41 +0200, David Kastrup wrote:
> James writes:
>
> > David,
> >
> > Revert the commit if its easier. I'll figure it out this evening when
> > I get home. It's probably some oversight or a makelsr issue.
> >
> > Sorry.
>
> Ah, this was a third-party commit by
James writes:
> David,
>
> Revert the commit if its easier. I'll figure it out this evening when
> I get home. It's probably some oversight or a makelsr issue.
>
> Sorry.
Ah, this was a third-party commit by you. The most frequent error here
is to apply a provided patch with
git apply xxx
David,
Revert the commit if its easier. I'll figure it out this evening when I get
home. It's probably some oversight or a makelsr issue.
Sorry.
Thu Jun 13 08:35:24 GMT+01:00 2019 David Kastrup :
> David Kastrup writes:
>
> > pat...@gnu.org writes:
> >
> >> 07:02:37 (UTC) Begin LilyPond comp
David Kastrup writes:
> pat...@gnu.org writes:
>
>> 07:02:37 (UTC) Begin LilyPond compile, previous commit at
>> 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
>> 07:02:40 Merged staging, now at: 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
>> 07:02:41 Success:./autogen.sh --noc
pat...@gnu.org writes:
> 07:02:37 (UTC) Begin LilyPond compile, previous commit at
> 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
> 07:02:40 Merged staging, now at: 52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
> 07:02:41 Success:./autogen.sh --noconfigure
> 07:02:57 Suc
07:02:37 (UTC) Begin LilyPond compile, previous commit at
52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
07:02:40 Merged staging, now at:52c98e2ec5f3ef2a24ee1a2d94dd09f8517a6f36
07:02:41Success:./autogen.sh --noconfigure
07:02:57Success:/tmp/
"James Lowe" writes:
> David
>> Thats the musicxml2ly thing again. I now locally did make & make
>> install now and restarted to see whether this still breaks.
>>
>> We probably need to make sure to use the right versions of
>> musicxml2ly (the ones in the build tree rather than the installed
David
> -Original Message-
> From: lilypond-devel
> On Behalf Of David Kastrup
> Sent: 19 June 2018 11:51
> To: pat...@gnu.org
> Cc: lilypond-devel@gnu.org
> Subject: Re: Patchy email
>
> pat...@gnu.org writes:
>
> > 10:01:55 (UTC) Begin
pat...@gnu.org writes:
> 10:01:55 (UTC) Begin LilyPond compile, previous commit at
> f3279a829a6eb5c009440f39de15c0104b038b7c
> 10:02:00 Merged staging, now at: f3279a829a6eb5c009440f39de15c0104b038b7c
> 10:02:01 Success:./autogen.sh --noconfigure
> 10:02:15 Suc
10:01:55 (UTC) Begin LilyPond compile, previous commit at
f3279a829a6eb5c009440f39de15c0104b038b7c
10:02:00 Merged staging, now at:f3279a829a6eb5c009440f39de15c0104b038b7c
10:02:01Success:./autogen.sh --noconfigure
10:02:15Success:/tmp/
11:52:14 (UTC) Begin LilyPond compile, previous commit at
fdab8053c4fbfadf38867f7d14769d227ce26749
11:52:24 Merged staging, now at:fdab8053c4fbfadf38867f7d14769d227ce26749
11:52:24Success:./autogen.sh --noconfigure
11:52:39Success:/tmp/
pat...@gnu.org writes:
> 15:20:22 (UTC) Begin LilyPond compile, previous commit at
> 65aaa35a119053e92a608fbedceb20762787d21b
> 15:20:27 Merged staging, now at: 65aaa35a119053e92a608fbedceb20762787d21b
> 15:20:28 Success:./autogen.sh --noconfigure
> 15:20:36 *** FAIL
15:20:22 (UTC) Begin LilyPond compile, previous commit at
65aaa35a119053e92a608fbedceb20762787d21b
15:20:27 Merged staging, now at:65aaa35a119053e92a608fbedceb20762787d21b
15:20:28Success:./autogen.sh --noconfigure
15:20:36 *** FAILED BUILD ***
/tmp/li
15:03:41 (UTC) Begin LilyPond compile, previous commit at
65aaa35a119053e92a608fbedceb20762787d21b
15:03:46 Merged staging, now at:65aaa35a119053e92a608fbedceb20762787d21b
15:03:47Success:./autogen.sh --noconfigure
15:04:03Success:/tmp/
Jean-Charles,
On 01/10/16 12:59, Jean-Charles Malahieude wrote:
Le 28/09/2016 à 13:23, James a écrit :
Now if only Jean-Charles, Graham et al, could script checking reg
test diffs and finding obscure make errors in all the .log files we
generate ;)
I'm not good at all with scripting, but c
Le 28/09/2016 à 13:23, James a écrit :
Now if only Jean-Charles, Graham et al, could script checking reg
test diffs and finding obscure make errors in all the .log files we
generate ;)
I'm not good at all with scripting, but could try to track down the
logs. What would you like me to do in t
On 28/09/16 10:24, David Kastrup wrote:
pat...@gnu.org writes:
07:29:54 (UTC) Begin LilyPond compile, previous commit at
8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:58 Merged staging, now at:8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:59Success:./a
pat...@gnu.org writes:
> 07:29:54 (UTC) Begin LilyPond compile, previous commit at
> 8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
> 07:29:58 Merged staging, now at: 8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
> 07:29:59 Success:./autogen.sh --noconfigure
> 07:30:16 Suc
07:29:54 (UTC) Begin LilyPond compile, previous commit at
8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:58 Merged staging, now at:8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
07:29:59Success:./autogen.sh --noconfigure
07:30:16Success:/tmp/
14:30:36 (UTC) Begin LilyPond compile, previous commit at
905109ea0e90efa8d9c1ba02769e458a0707cc47
14:30:42 Merged staging, now at:905109ea0e90efa8d9c1ba02769e458a0707cc47
14:30:43Success:./autogen.sh --noconfigure
14:30:56Success:/tmp/
pat...@gnu.org writes:
> 10:35:41 (UTC) Begin LilyPond compile, previous commit at
> def633f7a88fe8950b685adee93165c42299bd5c
> 10:35:55 Merged staging, now at: def633f7a88fe8950b685adee93165c42299bd5c
> 10:35:56 Success:./autogen.sh --noconfigure
> 10:36:13 Suc
10:35:41 (UTC) Begin LilyPond compile, previous commit at
def633f7a88fe8950b685adee93165c42299bd5c
10:35:55 Merged staging, now at:def633f7a88fe8950b685adee93165c42299bd5c
10:35:56Success:./autogen.sh --noconfigure
10:36:13Success:/tmp/
10:02:01 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
10:02:05 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
10:02:06Success:./autogen.sh --noconfigure
10:02:25Success:/tmp/
09:52:20 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:52:24 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:52:25Success:./autogen.sh --noconfigure
09:52:39Success:/tmp/
09:47:21 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:47:25 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:47:26Success:./autogen.sh --noconfigure
09:47:40Success:/tmp/
09:34:56 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:35:10 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:35:11Success:./autogen.sh --noconfigure
09:35:11 *** FAILED BUILD ***
/tmp/li
09:38:31 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:38:35 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:38:36Success:./autogen.sh --noconfigure
09:38:54Success:/tmp/
09:33:49 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:33:54 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:33:54Success:./autogen.sh --noconfigure
09:33:55 *** FAILED BUILD ***
/tmp/li
pat...@gnu.org writes:
> 09:14:55 (UTC) Begin LilyPond compile, previous commit at
> dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
> 09:15:08 test-master-lock and PID entry exist but previous Patchy
> run (PID 17333) died, resetting test-master-lock anyway.
> 09:15:10 Merged staging, now at:
09:14:55 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:15:08 test-master-lock and PID entry exist but previous Patchy
run (PID 17333) died, resetting test-master-lock anyway.
09:15:10 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb
David,
On 04/03/16 13:22, David Kastrup wrote:
> pat...@gnu.org writes:
>
>> 12:50:04 (UTC) Begin LilyPond compile, previous commit at
>> 1d9fc4b1512eb69a28677890dc26658c3552c6cd
>> 12:50:07 From ssh://git.sv.gnu.org/srv/git/lilypond
>>7a2e1ee..1d9fc4b master -> origin/master
>> 12:50
pat...@gnu.org writes:
> 12:50:04 (UTC) Begin LilyPond compile, previous commit at
> 1d9fc4b1512eb69a28677890dc26658c3552c6cd
> 12:50:07 From ssh://git.sv.gnu.org/srv/git/lilypond
>7a2e1ee..1d9fc4b master -> origin/master
> 12:50:08 Merged staging, now at: 1d9fc4b1512eb69a286778
12:50:04 (UTC) Begin LilyPond compile, previous commit at
1d9fc4b1512eb69a28677890dc26658c3552c6cd
12:50:07 From ssh://git.sv.gnu.org/srv/git/lilypond
7a2e1ee..1d9fc4b master -> origin/master
12:50:08 Merged staging, now at:1d9fc4b1512eb69a28677890dc26658c3552c6cd
12:50:09
12:08:37 (UTC) Begin LilyPond compile, previous commit at
1d9fc4b1512eb69a28677890dc26658c3552c6cd
12:08:44 Merged staging, now at:1d9fc4b1512eb69a28677890dc26658c3552c6cd
12:08:44Success:./autogen.sh --noconfigure
12:09:02Success:/tmp/
I'm presuming this is down to XeTeX not being installed on my patchy user.
Running patchy staging again after installing.
--
Phil Holmes
- Original Message -
From:
To:
Cc:
Sent: Monday, February 29, 2016 8:48 AM
Subject: Patchy email
08:43:24 (UTC) Begin LilyPond co
1 - 100 of 338 matches
Mail list logo
