Hi Anthony, On Sat, 2023-01-28 at 17:58 -0700, Anthony Fok wrote: > And... lilypond 2.24.0-1 has entered Debian! Though I already found a > bug when upgrading lilypond-doc due to /usr/share/info/lilypond > symlink conflict, my own fault for not testing it thoroughly enough > before upload. Thanks to excellent commit messages in LilyPond, by > Kevin Barry in this case, I was able to find out the problem and fix > it in a jiffy: we had been running (in debian/rules) both "$(MAKE) > install-doc" and "$(MAKE) install-info", not knowing that it is not > only an unnecessary duplication, but also install-info's behaviour > changed. Building 2.24.0-2 now, and keeping my fingers crossed. :-)
Thank you for your work! Unfortunately the package is missing two other major changes in 2.24.0: the Scheme files (.scm) should be byte- compiled for reasonable performance (which will depend on the architecture, to some degree, so maybe merge lilypond and -data?) and text fonts must be shipped separately. Please have a look here: https://lilypond.org/doc/v2.24/Documentation/changes/index.html#notes-for-source-compilation-and-packagers > > That said, since 2023-02-12 is a "Soft Freeze", bug fix releases can > still go after 2023-02-12, though the delay to testing migration > becomes 10 days regardless of the urgency setting, so perhaps > 2023-02-28 is the absolute latest for a bug fix release to make it > into bookworm before the 2023-03-12 Hard Freeze? Ok, I'll keep this date in mind and see when a release would be possible / make sense. Cheers Jonas
signature.asc
Description: This is a digitally signed message part
