Re: Bug#746005: Problems in Lilipond and Guile -- #746005

[Anthony Fok <foka@debian.org>]

Control: severity -1 important

On Fri, Dec 30, 2016 at 9:39 AM, Dr. Tobias Quathamer <toddy@debian.org> wrote:
> About a year later, Emilio states that the release team discussed this
> problem and "wouldn't like to release Stretch with guile-1.8 just for
> lilypond's sake":
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005#128>
>
> However, he also wrote in that message that "We can discuss this again later
> in the cycle if necessary, though hopefully lilypond can get in shape and we
> won't need to do that :)"

Dear friends,

I am happy to report that a new Debian version of lilypond (2.18.2-7),
with its own privately bundled guile-1.8, hidden inside

  * /usr/lib/$(DEB_HOST_MULTIARCH)/lilypond/2.18.2 and
  * /usr/share/lilypond/2.18.2/guile/1.8,

has entered unstable, and buildd has built it for all architectures except
powerpcspe (Needs-Build, long queue) and sh4 (BD-Uninstallable):

    https://buildd.debian.org/status/package.php?p=lilypond

So, while the migration to guile-2.0 is a definite goal, one that
upstream is still working on it slowly but surely (maybe in 2.20?),
the absence of guile-1.8 in Debian no longer causes lilypond 2.18.2 to
FTBFS, hence I am lowering the severity of this bug from serious to
important.

Hope this is enough to help bring LilyPond back into Debian 9 "stretch".
I will submit an unblock request right away.  Keeping my fingers crossed.  :-)

Cheers,

Anthony