On Thu, 2007-02-08 at 13:36 +0100, Frank Küster wrote: > Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote: > > > severity 380855 wishlist > > retitle 380855 lilypond: conform to new python policy > > thanks > [...] > > Work on the 2.8 version of lilypond is proceeding; it would not be > > productive to spend too much energy on 2.6 right now. > > 2.8 is uploaded and in testing. Does this bug still apply to the etch > version?
Yes, I think it does. I'm not certain, but there isn't any interest on my part in worrying about it right now. As soon as etch releases, I'm going to package 2.10, and so I'll make 2.10 conform to the new python policy (and this bug is a convenient reminder to do that). A fix for this one, however, would not be appropriate for etch in my opinion, especially since the lilypond build system is so fragile in my experience. So the result is that this bug should stay open, but it's not worth spending time now (or ever) to figure out the exact answer to your question. :) Thomas
signature.asc
Description: This is a digitally signed message part
