On Tue, 05 May 2015, Emilio Pozuelo Monfort wrote: > On 29/04/15 14:29, Don Armstrong wrote: > > Upstream has been working on porting, but there are some serious > > issues with guile 2.0 which have not yet been resolved. I agree that > > this should be fixed before stretch, but I don't think that removing > > both packages this early is going to be helpful, as it'll be some > > time before the porting work is done. > > The last comment in the upstream bug report is from 2011. Do you have any > indication that upstream is still working on this? Is there any timeline?
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005#94 for a recent message from upstream. Basically, Guile 2.0 has some serious problems. I'd certainly like to be able to remove guile-1.8 and switch to 2.0, but doing so requires quite a bit of work in lilypond, and also some work in guile upstream. Indeed, it looks like lilypond may be forced to skip 2.0 entirely. > I am still very tempted to remove this from testing now so guile-1.8 > can go away... That would really just be hiding the issue. This really needs more work in both lilypond and guile's upstream. At this juncture, I'm OK with expending the effort myself to keep guile-1.8 working with lilypond as the sole reverse dependency if that's what is required. [Unfortunately, I don't have enough time or expertise to actually solve the issues with the newer versions of guile, though.] -- Don Armstrong http://www.donarmstrong.com If it jams, force it. If it breaks, it needed replacing anyway. -- Lowery's Law -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
