An update for those who are watching: We needed a new fontforge in Debian, which is now there.
However, while lilypond claims to build with python 2.3, it turns out this is not actually the case; it relies on a library that only exists in python 2.4. Because of the way the python packages are arranged, it is non-trivial to use any version of python but the default. The Debian python team plans to shift the python package to have 2.4 as the default, but it isn't done yet. I can work around this one, either by contorting the build system to use python 2.4 even though 2.3 is the default, or by kludging the 2.4 library in question to be present for lilypond's use. If this were the only problem, I would do it now. However, there is also a showstopper bug which prevents lilypond 2.8.1 from being compiled on any system which does not already have lilypond installed, and the fix is not obvious. Upstream is working on it, and presumably the fix will be in 2.8.2. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
