Loïc Minier <[EMAIL PROTECTED]> writes: > So IIUC, a new upstream release requires python 2.4 and fixes the > gcc-4.1 build failure.
This is correct. > 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). Exactly. > 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. In my opinion, we should probably not release the existing Debian lilypond in the next release. It is too old and only leads to confusion in practice. At the same time, this is not a reason to remove it from testing immediately. > 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). This is what I think I should do. Thomas
