Loïc Minier <[EMAIL PROTECTED]> writes: > On Fri, May 26, 2006, Thomas Bushnell BSG wrote: >> This is blocked waiting for the python-defaults to be changed. > > It's not clear to me why you can't fix the gcc-4.1 build failure before > python2.4 is uploaded. I've read your argument concerning lilypond > working best when python2.4 is python, or with some python 2.4 > libraries, however this probably true before gcc-4.1 was made the > default, and would still be true with a fixed lilypond.
Actually, python 2.4 is required for the python upgrade. Upstream has (of course) fixed the gcc-4.1 problem already, so the upgrade closes it too, which is why I had coupled the two. You are right that it can be fixed independently. Basically, I need a single piece of information to judge whether a separate fix is a good idea: knowing whether python-defaults will be uploaded in the next week or so. Do you have an actual answer to this question? The people who might ignore questions on the subject. Thomas
