Your message dated Mon, 30 Jan 2017 21:56:11 -0700 with message-id <CABrvRiHX2sEtT53mVJtbjXJ=epohejaftjt0fqw1u3y_w5e...@mail.gmail.com> and subject line Bug #684192: lilypond-book: not running due to python problem has caused the Debian Bug report #684192, regarding lilypond-book: not running due to python problem to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 684192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684192 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Package: lilypond Version: 2.14.2-3 Severity: normal ~> lilypond-book -h Traceback (most recent call last): File "/usr/bin/lilypond-book", line 703, in <module> main () File "/usr/bin/lilypond-book", line 634, in main files = do_options () File "/usr/bin/lilypond-book", line 609, in do_options (global_options, args) = opt_parser.parse_args () File "/usr/lib/python2.7/optparse.py", line 1399, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python2.7/optparse.py", line 1443, in _process_args self._process_short_opts(rargs, values) File "/usr/lib/python2.7/optparse.py", line 1550, in _process_short_opts option.process(opt, value, values, self) File "/usr/lib/python2.7/optparse.py", line 788, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python2.7/optparse.py", line 810, in take_action parser.print_help() File "/usr/lib/python2.7/optparse.py", line 1669, in print_help file.write(self.format_help().encode(encoding, "replace")) File "/usr/lib/python2.7/codecs.py", line 351, in write data, consumed = self.encode(object, self.errors) UnicodeDecodeError: 'utf8' codec can't decode byte 0xfc in position 346: invalid start byte Seems that lilypond-book runs in a typical python problem, ignoring that the world is more than utf-8. Here is my setting: ~> locale LANG=de_DE LANGUAGE= LC_CTYPE="de_DE" LC_NUMERIC="de_DE" LC_TIME="de_DE" LC_COLLATE="de_DE" LC_MONETARY="de_DE" LC_MESSAGES="de_DE" LC_PAPER="de_DE" LC_NAME="de_DE" LC_ADDRESS="de_DE" LC_TELEPHONE="de_DE" LC_MEASUREMENT="de_DE" LC_IDENTIFICATION="de_DE" LC_ALL=de_DE (For the record, without any tail that means latin1.) So this script do nothing helpful. However, the main tool works well. - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'stable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4.6 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Versions of packages lilypond depends on: ii ghostscript 9.05~dfsg-6 ii guile-1.8 1.8.8+1-8 ii guile-1.8-libs 1.8.8+1-8 ii libc6 2.13-35 ii libfontconfig1 2.9.0-7 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.1-6 ii libglib2.0-0 2.32.3-1 ii libgmp10 2:5.0.5+dfsg-2 ii libltdl7 2.4.2-1.1 ii libpango1.0-0 1.30.0-1 ii libstdc++6 4.7.1-6 ii lilypond-data 2.14.2-3 ii python 2.7.3-2 Versions of packages lilypond recommends: pn lilypond-doc <none> ii texlive-latex-base 2012.20120611-3 lilypond suggests no packages. - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <[email protected]> Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQGcBAEBCgAGBQJQIUBeAAoJEKZ8CrGAGfasOOkL/3mm7EpMnVuTvQeW0d2bPbN7 MTxgBLx0sURAQwQzpzC8tP07PnHT//x8+rOah8l1j3HenTCG/zFUYrFjG8wBZxir tAjH+6PkIB0jB3OqES4tscsSHl6Bb3YzFse6k8PNhpFvsZ0TvWE2hY+QeAnQ9moB tN9a8tn1ED9mPCmVAV19URjcspRxI3OTDIrL1neDWe/OGx/xywdBx/PWAuJyI5Cb eztkDdLrnOD9PiSjL/KyQNZ//JXlm/685+/hf/355GRJJ5Y3PAUDEaDbg24yRaLr uFWrBAImDMbsNhXKnGSQFthnGT0O7Q5fXDd7qmdZ4Kz0AK4uyqQCsDVEZBJuLe0s ynYJ8SQOjQWuzrakrvZBeiBG8lRd8SEkv494C1DynAYzrRcO3dayDZdwWrNx4QhC CLyKzmeAEe3OztCPnf9CrYwYszoSalsGblmRqrzJ9pYqrq7aKu/lB0D68a7Ecv+8 rx130H/qeoMHtRUWvaJZrC1K+LNs33AP8bE3c5UoWA== =gwU9 -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---Looks like this issue has been fixed quite a while ago, and was marked "fixed" in October 2014. So, let's close this bug report for good. :-) Cheers, Anthony
--- End Message ---
