Re, I have found why it builed for you and not on my system.
The python version installed on my system was a
2.4 version. I had backported on a 2.3 version,
and the problem seem solved.
It will be interesting to know why there is this problem
with new versions of python, because if one
day Python is 2.4 by default, the bug could be a
problem to build. I don't know if it is a problem of
Debian Package or if it is a general problem of python 2.4.
I will test more...
So, for Thomas BUSHNELL: I don't know if it is really a good idea to
wait Python 2.4 by default to release lilypond in debian :)
I hope that you will be satisfy of my report, this
time :).
--
.---. Ludovic RESLINGER
/ \
[EMAIL PROTECTED]@./ Trumpet Student in CNR
/`\_/`\ Free Software Developer
// )X( \\
| \ : )|_ _,'| .''`.
/`\_`> <_/ \ @======TTT=====::_ | : :' :
\__/'---'\__/ ((_<=HHH___)) `.| `. `'`
`---UUU---'=> `-
signature.asc
Description: Digital signature
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
