Control: severity -1 minor On Fri, Jan 27, 2017 at 11:26 PM, Arthur Marsh <arthur.ma...@internode.on.net> wrote: > Package: lilypond > Version: 2.18.2-6 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > > upgrading lilypond 2.18.2-4.1 -> 2.18.2-6, so > aptitude did: > [REMOVE, NOT USED] guile-1.8:amd64 1.8.8+1-10+b1 > [REMOVE, NOT USED] guile-1.8-libs:amd64 1.8.8+1-10+b1 > > ldd lists libguile.so.17 as a dependency of /usr/bin/lilypond.real > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > reinstalled guile-1.8 and guile-1.8-libs
Hello Arthur, Thank you for your bug report. However, I would like to assure you that lilypond 2.18.2-6 and on (now 2.18.2-7) does *not* need the guile-1.8 and guile-1.8-libs packages any more. As a matter of fact, the guile-1.8 packages have been *removed* from Debian stretch (the upcoming Debian 9) because it is somewhat ancient and have been superseded by guile-2.0. Unfortunately, LilyPond and Guile 2.0 are just not ready for one another yet. That is why lilypond 2.18.2-6 and on comes with its own privately bundled copy of guile-1.8. And you are supposed to run /usr/bin/lilypond, which sets the appropriate LD_LIBRARY_PATH environment variable for /usr/bin/lilypond.real so it can find where we hide libguile.so.17. You are *not* supposed to run /usr/bin/lilypond.real directly. See http://bugs.debian.org/746005 for the full glorious detail. So, yes, please feel free to run "sudo apt-get remove --purge guile-1.8-libs guile-1.8" any time. I assure you that /usr/bin/lilypond would still run perfectly. If it really bothers you, I could try to move /usr/bin/lilypond.real into /usr/lib/x86_64-linux-gnu/lilypond/2.18.2/bin/ so you don't see it, but the Debian 9 "stretch" hard freeze is coming up very quickly in less than a week, and I would rather not fix what ain't broken at this point in time to avoid further delays or introducing other bugs in the process. Thank you for your understanding. Downgrading bug severity from important to minor. Cheers, Anthony
