Source: lilypond
Version: 2.18.2-7
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
I made a dist-upgrade to buster testing.
I tried to compile the horn voice of
www.mutopiaproject.org/ftp/MozartWA/KV447/MozartHornConcerto3/MozartHornConcerto3-lys.zip
With the old system of strech testing this had worked.
With the actual system I got a segfault instead of a pdf score file.
Compilation of small files (up to 4 kB) work
you'll find a detailed german report at
https://lilypondforum.de/index.php/topic,70.0.html
This item is reported to the lilypond devel mailing list
http://lilypond.1069038.n5.nabble.com/segfault-with-2-18-2-from-Debian-9-0-testing-td204133.html
At my opinion lilypond is useless at buster testing
regards Thomas Wille
