Hi Jonas, On Wed, Jan 25, 2023 at 2:44 PM Jonas Hahnfeld <hah...@hahnjo.de> wrote: > Thanks for pushing to get guile-2.2 back into Debian and LilyPond > 2.24.0 packaged for Debian Bookworm, much appreciated. Regarding > maintenance of Guile 2.2, we are probably in this together since our > official binaries use it as well...
Many thanks to Rob Browning for his blessings, and to the Debian FTP Masters for asking me for more details, and let guile-2.2 back into Debian 12 bookworm. And thank you for offering to help with Guile 2.2 maintenance just in case any problem arises! I really hope LilyPond 2.26.0 and the rest of the ecosystem (e.g. on Windows platform) will be ready for Guile 3.0 really soon. 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. :-) > Another question for planning would be regarding Debian's freeze: What > would be the last date that you could possibly pick up a bug fix > release 2.24.1 of LilyPond? There are no concrete plans yet, but if you > say that it is possible and somehow fits the schedule, we might go for > it. Great question! I'm not entirely sure! You likely know about about freeze schedule from https://release.debian.org/bookworm/freeze_policy.html but how it would exactly happen is a bit hard to say; there is always uncertainty, but here is my interpretation: According to that page, since the Soft Freeze starts on 2023-02-12, I would say having 2.24.1 released before 2023-02-05 would be the safest bet, giving me a day or two of leeway to get it built, tested and uploaded, and then 5 days for migration to testing/bookworm before 2023-02-12. Though maybe if I were to set "urgency=high" in debian/changelog, the delay is supposedly reduced to 2 days, so perhaps 2023-02-08? 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? That said, bug fixes after 2023-03-12 is still possible (with a minimum 20-day delay for migration to bookworm), but the lilypond Debian package currently does not have any autopkgtest yet, so that would require a manual review and unblock from the Release Managers. I suppose I could try to add an autopkgtest for LilyPond by trying to run "make test" but hopefully using the existing /usr/bin/lilypond binary instead of recompiling the whole thing from source? (Though that's a possibility too...) That might remove the need for manual review. I'm not sure. Failing that, there will be "bookworm-backports" after the Debian 12 is released where we could backport future bug fixes. Something like that? Thank you so much for your work on LilyPond! It's always exciting to have a new release as an end user, and it is amazing the amount of dedication and great work that you and the rest of the LilyPond development team put into such a complicated yet immensely useful piece of software. Kudos to you all! Cheers, Anthony