Hi, On Fri, Jul 21, 2006, Thomas Bushnell BSG wrote: > 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.
So IIUC, a new upstream release requires python 2.4 and fixes the gcc-4.1 build failure. > 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. Concerning the new upstream release, I suggest you follow the Python transition and package lilypond with python 2.4 as the PYTHON runtime. This will still work after the switch, and requires about the same amount of work (the only additional work is the "sed" snippet I added to debian/rules in my patch). Whatever you decide on the above, I suggest you upload the gcc-4.1 build failure fix right now though, so that people can build the package if they need to, and to keep lilypond in a releasable state. I don't know when the switch to the default python version will be, but you can prepare a package to experimental if you need to experiment with that (it has a switched python-defaults). Bye, -- Loïc Minier <[EMAIL PROTECTED]>
