David Kastrup writes:
> Jonas Hahnfeld writes:
>
>> Am Mittwoch, den 15.07.2020, 21:35 +0200 schrieb David Kastrup:
>>> Jonas Hahnfeld writes:
>>> > Am Mittwoch, den 15.07.2020, 17:31 +0100 schrieb Phil Holmes:
>>> > > Here's the logfile and the ly file.
>>> >
>>> > Could this be collisions
Jonas Hahnfeld writes:
> Am Mittwoch, den 15.07.2020, 21:35 +0200 schrieb David Kastrup:
>> Jonas Hahnfeld writes:
>> > Am Mittwoch, den 15.07.2020, 17:31 +0100 schrieb Phil Holmes:
>> > > Here's the logfile and the ly file.
>> >
>> > Could this be collisions of the random file names generated
Am Mittwoch, den 15.07.2020, 21:35 +0200 schrieb David Kastrup:
> Jonas Hahnfeld writes:
> > Am Mittwoch, den 15.07.2020, 17:31 +0100 schrieb Phil Holmes:
> > > Here's the logfile and the ly file.
> >
> > Could this be collisions of the random file names generated for
> > temporary files? The
Jonas Hahnfeld writes:
> Am Mittwoch, den 15.07.2020, 17:31 +0100 schrieb Phil Holmes:
>> Here's the logfile and the ly file.
>
> Could this be collisions of the random file names generated for
> temporary files? The argument to backend-library.scm:248 comes
> from create-file-exclusive which
Hi,
Le 02/07/2020 à 09:05, Han-Wen Nienhuys a écrit :
You can also do a global cleanup. We have done this in the past, but
it has the disadvantage that it makes history (eg. git-blame) harder
to read.
So, I did the global cleanup:
https://gitlab.com/lilypond/lilypond/-/merge_requests/251
Le 15/07/2020 à 19:44, Jean Abou Samra a écrit :
Hi,
Le 15/07/2020 à 18:31, Phil Holmes a écrit :
Here's the logfile and the ly file.
/home/gub/NewGub/gub/target/linux-x86/root/usr/share/lilypond/current/scm/backend-library.scm:248:5:
In procedure close-port in expression (close-port port):
Hi,
Le 15/07/2020 à 18:31, Phil Holmes a écrit :
Here's the logfile and the ly file.
/home/gub/NewGub/gub/target/linux-x86/root/usr/share/lilypond/current/scm/backend-library.scm:248:5:
In procedure close-port in expression (close-port port):
Am Mittwoch, den 15.07.2020, 17:31 +0100 schrieb Phil Holmes:
> Here's the logfile and the ly file.
Could this be collisions of the random file names generated for
temporary files? The argument to backend-library.scm:248 comes
from create-file-exclusive which returns #f if the file already exists
Here's the logfile and the ly file.
Once we understand the issue, I'll wait until you say "go" for 21.4.
--
Phil Holmes
- Original Message -
From: "Jonas Hahnfeld"
To: "Phil Holmes" ; "Devel"
Sent: Wednesday, July 15, 2020 4:31 PM
Subject: Re: Today's problem with GUB build
Am Mittwoch, den 15.07.2020, 16:26 +0100 schrieb Phil Holmes:
> Here's the lilypond-doc.log zipped.
Do you happen to still have out/lybook-db/snippet-names-
bcc309d5e1e5a6301f36814c1d4d872c.log around? In any case, it's odd that
you're seeing issues with the very same base commit as 2.21.3
> I
Here's the lilypond-doc.log zipped.
I was doing a new release to get the documentation on the website looking
correct again. We've had problems in the past if the build number is not
incremented.
If I don't get problems I can easily do another release with the updates you
mentioned. If I
Am Mittwoch, den 15.07.2020, 15:04 +0100 schrieb Phil Holmes:
> I get this:
>
> Making Documentation/out-www/web.texi (copy)
> Command '/home/gub/NewGub/gub/target/linux-x86/root/usr/bin/lilypond \
> -dbackend=eps --formats=ps,png,pdf -djob-count=8 -dinclude-eps-fonts
> -dgs-load-fonts
>
I get this:
Making Documentation/out-www/web.texi (copy)
Command '/home/gub/NewGub/gub/target/linux-x86/root/usr/bin/lilypond \
-dbackend=eps --formats=ps,png,pdf -djob-count=8 -dinclude-eps-fonts -dgs-load-fonts
--header=doctitle --header=doctitleca --header=doctitlecs --header=doctitlede
Am Dienstag, den 14.07.2020, 09:05 +0200 schrieb Jonas Hahnfeld:
> Am Montag, den 13.07.2020, 22:38 +0200 schrieb Jonas Hahnfeld:
> > Am Montag, den 13.07.2020, 21:07 +0200 schrieb Han-Wen Nienhuys:
> > > On Mon, Jul 13, 2020 at 7:49 PM Phil Holmes wrote:
> > > > I created a new release today. I
14 matches
Mail list logo
