FS#80155 - [lilypond] ghostscript 10.02.1 breaks PDF creation for lilypond

Attached to Project: Arch Linux
Opened by Patrick McCarty (pnorcks) - Friday, 03 November 2023, 22:24 GMT
Last edited by Caleb Maclennan (alerque) - Monday, 06 November 2023, 10:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To David Runge (dvzrv)
Caleb Maclennan (alerque)
Brett Cornwall (ainola)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

A breaking change was introduced in Ghostscript 10.02.1 that breaks LilyPond's ability to create PDFs.

Steps to reproduce:
Run `lilypond ...` on any .ly file to generate a PDF. Instead an error is raised.

Program versions:
- ghostscript 10.02.1-1
- lilypond 2.24.2-1

Since LilyPond's primary output format is PDF, I set the bug severity as "High". I hope that this abides by the bug report guidelines. If not, please lower the severity.

Upstream bug report for Ghostscript, closed as a won't fix:
https://bugs.ghostscript.com/show_bug.cgi?id=707307

Relevant LilyPond bug reports:
https://gitlab.com/lilypond/lilypond/-/issues/6675
https://gitlab.com/lilypond/lilypond/-/issues/6676

Proposed fix for LilyPond, not yet reviewed or approved as of this writing:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2160
This task depends upon

Closed by  Caleb Maclennan (alerque)
Monday, 06 November 2023, 10:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  pkgrel=3 is patched to work again.
Comment by Jonas Hahnfeld (hahnjo) - Sunday, 05 November 2023, 20:32 GMT
Given that LilyPond is currently quite broken, you may consider applying the patch in https://gitlab.com/lilypond/lilypond/-/merge_requests/2160. We cannot merge it right now because it breaks a special mode that we only use in our CI testing, but this should not be relevant for Arch Linux users...
Comment by Patrick McCarty (pnorcks) - Monday, 06 November 2023, 07:02 GMT
  • Field changed: Percent Complete (100% → 0%)
I can still reproduce the issue with lilypond 2.24.2-2, unfortunately. When compiling a test file with `--verbose`, I still see the `Error: /undefined in /finddevice` from ghostscript, thus resulting in no PDF created.
Comment by Caleb Maclennan (alerque) - Monday, 06 November 2023, 07:45 GMT
I've hit this too. I didn't notice it at first because most of my lilypond builds are run through LaTeX, but rendering anything to PDF directly in Lilypond is completely broken.

I was able to get it working by downgrading ghostscript with this package file from the archive: https://archive.archlinux.org/packages/g/ghostscript/ghostscript-10.01.2-1-x86_64.pkg.tar.zst
Comment by Jonas Hahnfeld (hahnjo) - Monday, 06 November 2023, 07:56 GMT
Yes, it appears the latest version of the merge request isn't fully working... Also for reproducibility, maybe use an explicit commit hash to apply? Here is the initial commit that should work: https://gitlab.com/lilypond/lilypond/-/commit/1695a4d6 I'm not sure if I have time today to make sure it actually works for 2.24.2...
Comment by Caleb Maclennan (alerque) - Monday, 06 November 2023, 08:01 GMT
Also because I wasn't clear, by "I hit this too" I mean with the patched package -2 with MR#2160 applied.

Also my use case does not use `--verbose`. It does have some elaborate network of lilypond includes with some custom scheme code, but none of it seems to related to the Postscript changes in Ghostscript or verbose mode or anything, so I don't know what gives yet.
Comment by Caleb Maclennan (alerque) - Monday, 06 November 2023, 08:13 GMT
I'll look into pinning the patch to the SHA and see if that build works, thanks for the pointer.
Comment by Caleb Maclennan (alerque) - Monday, 06 November 2023, 08:36 GMT
At least for my project use case the 1695a4d6 version of the patch *does* work with the latest ghost script where the version of the MR the pkgrel 2 happened to be built with did not. I've released pkgrel-3 with the pinned sha of the patch.

@pnorcks Let me know if that works for you too. I'll leave this open so it can be commented on until we confirm this works for others too. Then we'll bump as soon soon as Lilypond has a patch release out too.
Comment by Patrick McCarty (pnorcks) - Monday, 06 November 2023, 09:51 GMT
@alerque The changes in commit 1695a4d6 fix the issue for me.
Comment by Caleb Maclennan (alerque) - Monday, 06 November 2023, 10:16 GMT
Great. Then I'll close this since our patched Lilypond package works again and leave further changes to updating to a fixed upstream release and dropping our patching.

Loading...