Re: Lilypond on Fedora 38 "mostly broken"

2023-12-20 Thread Peter Mayes
I just saw that there was a lilypond update available for Fedora 38 (my 
main machine), and updating from 2.25.4 to 2.25.11 has fixed the problem.


Same is true for Fedora 39.

Just in case others are affected.

On 17/12/2023 11:25, Jean Abou Samra wrote:


This is not https://bugzilla.redhat.com/show_bug.cgi?id=2208744 but 
rather https://bugzilla.redhat.com/show_bug.cgi?id=2253842 , which is 
being fixed. The updates are in the "Testing" repositories. See 
https://bugzilla.redhat.com/show_bug.cgi?id=2253842#c3 for how to 
install the update on Fedora 38.



--
Best wishes -- Peter
--
Peter Mayes




Re: Lilypond on Fedora 38 "mostly broken"

2023-12-17 Thread Jean Abou Samra
This is not https://bugzilla.redhat.com/show_bug.cgi?id=2208744 but rather 
https://bugzilla.redhat.com/show_bug.cgi?id=2253842 , which is being fixed. The 
updates are in the "Testing" repositories. See 
https://bugzilla.redhat.com/show_bug.cgi?id=2253842#c3 for how to install the 
update on Fedora 38.




signature.asc
Description: This is a digitally signed message part


Lilypond on Fedora 38 "mostly broken"

2023-12-17 Thread Peter Mayes
I am running into the following error on my main system, which is Fedora 
38 Linux with lilypond-2.25.4-2.fc38.x86_64 installed.


This is with ANY score:

warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH 
-dAutoRotatePages=/None -dPrinted=false /tmp/lilypond-tmp-5499149)' 
failed (256)


/usr/share/lilypond/2.25.4/ly/init.ly:64:2: error: Guile signaled an 
error for the expression beginning here

#
 (let ((book-handler (if (defined? 'default-toplevel-book-handler)
Throw to key `ly-file-failed' with args `()'.

From an internet search, it seems that this is a well-known issue:

https://bugzilla.redhat.com/show_bug.cgi?id=2208744 [A duplicate of 
2208024, where there is more info]


Bug 2208744 - lilypond-2.25.4-1.fc38.x86_64 mostly broken

From what I can understand, that seems to have been fixed back in May, 
so I am a little surprised that it isn't fixed yet in Fedora 38.


Also, I have a Fedora 39 virtual machine, and that has the same issue 
with 2.25.4


Does anybody have any inside information on when we can expect to see a fix?

This is not a show-stopper for me, as I have another system with a 
slightly older version of Lilypond.


Thanks in advance.

--
Best wishes -- Peter
--
Peter Mayes