Additional info: Bug cannot be reproduced with lilypond in stretch/stretch-backports, though it seems to be the same upstream version of lilypond. Note other versions differ, though, e.g. texlive.
-- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-0.bpo.4-amd64 (SMP w/2 CPU cores) 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) Versions of packages lilypond depends on: ii ghostscript 9.26a~dfsg-0+deb9u3 ii libc6 2.24-11+deb9u4 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3.2 ii libgcc1 1:6.3.0-18+deb9u1 ii libglib2.0-0 2.50.3-2 ii libgmp10 2:6.1.2+dfsg-1 ii libltdl7 2.4.6-2 ii libpango-1.0-0 1.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libstdc++6 6.3.0-18+deb9u1 ii lilypond-data 2.19.81+really-2.18.2-13~bpo9+1 ii python 2.7.13-2 Versions of packages lilypond recommends: ii texlive-latex-base 2016.20170123-5 Versions of packages lilypond suggests: pn lilypond-doc <none> -- no debconf information ?
signature.asc
Description: OpenPGP digital signature
