On Thu, 2023-01-12 at 02:17 +0100, Jean Abou Samra wrote: > > Additionally I would have liked to target the last weekend of January / > > early February for a bugfix release 2.24.1. Unfortunately, I haven't > > heard back from the Debian people yet. As you may remember, the timing > > for the stable release was chosen to make it possible to include > > LilyPond 2.24.0 in the upcoming Debian Bookworm and a user also opened > > a request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026200 > > However, in answering I discovered that Debian removed guile-2.2 for > > the Bookworm release during November, after we had already branched. > > Right now, they only have guile-3.0 which LilyPond doesn't officially > > support. > > Oh noooo... <facepalm> > > Did anyone try to tell them that this was a bad idea? I mean, it's > true that Guile 3.0 is already three years old, but so far compiling > it for Windows requires trying branches that are kept more or less > alive by some volunteers but not integrated into the main tree, so > most people who want to write cross-platform software in Guile will > need to use Guile 2.2.
Please have a look at the link I posted above. I already replied there some time ago.
signature.asc
Description: This is a digitally signed message part
