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

Processing control commands: > severity -1 important Bug #746005 [lilypond] lilypond: please migrate to guile-2.0 Severity set to 'important' from 'serious' -- 746005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

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

Control: severity -1 important On Fri, Dec 30, 2016 at 9:39 AM, Dr. Tobias Quathamer 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": >

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

Am 30.12.2016 um 07:28 schrieb Marc Dequènes (duck): Quack, I think the release team should have been involved much much earlier. Hi, the release team has been involved, see Emilio's mail from April 2015: About a year later, Emil

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

Quack, I think the release team should have been involved much much earlier. It seems having Lilypond working with recent Guile before the release is not going to happen. Even if it built properly there would maybe have runtime bugs to solve. If people are willing to maintain Guile 1.8 into