Bug#357057: ping

2006-07-24 Thread Thomas Bushnell BSG
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

Bug#357057: ping

2006-07-22 Thread Loïc Minier
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 py

Bug#357057: ping

2006-07-21 Thread Thomas Bushnell BSG
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 li

Bug#357057: ping

2006-07-21 Thread Loïc Minier
Hi, 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