|
| From: | Knut Petersen |
| Subject: | Re: Patchy email |
| Date: | Sat, 27 Jul 2019 08:19:45 +0200 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 27.07.19 07:56, David Kastrup wrote:
What happened to the musicxml2ly patch? It vanished from staging. Shall I push it again?It didn't pass patchy testing on my computer with failures in the musicxml files. So it appears to have a problem with, uh, Python 2.7.16+ (according to python --version on my current Ubuntu). If you need more pointers, I can try getting useful logs.
Yes, that would be very helpful. Before announcing that I thought that the patch was ready it passed a full GUB build on my system and the code processed all musicxml from the lilypond sources correctly with both the GUB-generated python 2.4.5 and the system's (opensuse tumbleweed) python 2.7.16. The relevant log file and the *.ly files generated from the xml sources would be of interest. What distribution do you use? Please your /etc/os-release. Knut
| [Prev in Thread] | Current Thread | [Next in Thread] |