weird error engraving two files with 2.23.14

2022-10-12 Thread Federico Bruni
Hi folks I've recently used convert-ly to update my private music sheet library and test version 2.23.14 (official binaries). Two files are failing with the same error message: Drawing systems... Converting to `foo.pdf'... warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotateP

Re: source file ... .scm newer than compiled ... .go file

2022-10-12 Thread Federico Bruni
Il giorno mer 12 ott 2022 alle 23:59:32 +0200, Federico Bruni ha scritto: I'll have to find a solution when building the flatpak. Waiting for minutes or hours while CPU hits 100% is not an option. For the records, another application using Guile (GNU Cash) had the same problem with flatpak th

PATCHES - Countdown to October 14

2022-10-12 Thread Colin Campbell
Here is the current countdown report. The next countdown will begin on Octobwer 14th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1663 cairo: follow filename convention for SVG output - Jiří Hon https://

Re: source file ... .scm newer than compiled ... .go file

2022-10-12 Thread Federico Bruni
Il giorno mer 12 ott 2022 alle 21:23:03 +0200, Jonas Hahnfeld ha scritto: On Wed, 2022-10-12 at 00:30 +0200, Federico Bruni wrote: Hi all I think I've already seen discussions about this. Can you please remind how to work around this error? Guile looks at file timestamps and the .go f

stable/2.24 has branched; master is 2.25.0

2022-10-12 Thread Jonas Hahnfeld via Discussions on LilyPond development
Hi all, as discussed, I ran the formatting tools (clang-format and fixscm.py) and branched stable/2.24 from commit 2d8a09d28e5c8a. The version in master is now 2.25.0 and the branch is open again for development. Translation updates can continue to go into the stable/2.24 branch, all other fixes

Re: source file ... .scm newer than compiled ... .go file

2022-10-12 Thread Jonas Hahnfeld via Discussions on LilyPond development
On Wed, 2022-10-12 at 00:30 +0200, Federico Bruni wrote: > Hi all > > I think I've already seen discussions about this. > Can you please remind how to work around this error? Guile looks at file timestamps and the .go files must always be newer than their .scm counterparts. Guile's build system s