Your message dated Tue, 02 Feb 2021 20:55:55 +0000 with message-id <[email protected]> and subject line Bug#852871: fixed in lilypond 2.22.0-7 has caused the Debian Bug report #852871, regarding lilypond: /usr/bin/lilypond.real depends on libguile.so.17, not listed as dependency 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.) -- 852871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852871 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: lilypond Version: 2.18.2-6 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrading lilypond 2.18.2-4.1 -> 2.18.2-6, so aptitude did: [REMOVE, NOT USED] guile-1.8:amd64 1.8.8+1-10+b1 [REMOVE, NOT USED] guile-1.8-libs:amd64 1.8.8+1-10+b1 ldd lists libguile.so.17 as a dependency of /usr/bin/lilypond.real * What exactly did you do (or not do) that was effective (or ineffective)? reinstalled guile-1.8 and guile-1.8-libs * 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 unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.10.0-rc5+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages lilypond depends on: ii ghostscript 9.20~dfsg-2 ii libc6 2.24-9 ii libfontconfig1 2.11.0-6.7 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:7-20170118-1 ii libglib2.0-0 2.50.2-2 ii libgmp10 2:6.1.2+dfsg-1 ii libltdl7 2.4.6-2 ii libpango-1.0-0 1.40.3-3 ii libpangoft2-1.0-0 1.40.3-3 ii libstdc++6 6.3.0-5 ii lilypond-data 2.18.2-6 pn python:any <none> Versions of packages lilypond recommends: ii lilypond-doc 2.18.2-6 ii texlive-latex-base 2016.20170123-1 lilypond suggests no packages. -- debconf-show failed
--- End Message ---
--- Begin Message ---Source: lilypond Source-Version: 2.22.0-7 Done: Anthony Fok <[email protected]> We believe that the bug you reported is fixed in the latest version of lilypond, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anthony Fok <[email protected]> (supplier of updated lilypond package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 02 Feb 2021 13:21:42 -0700 Source: lilypond Architecture: source Version: 2.22.0-7 Distribution: unstable Urgency: medium Maintainer: Anthony Fok <[email protected]> Changed-By: Anthony Fok <[email protected]> Closes: 852871 Changes: lilypond (2.22.0-7) unstable; urgency=medium . * Add debian/lilypond-doc.lintian-overrides to override info-document-not-compressed error and info-document-missing-image-file warnings * Fix handling of file names with non-ASCII characters for Guile 2.x. See https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and these cherry-picked patches: - 0004-Revert-Issue-4125-Disable-character-set-recognition.patch - 0005-Write-input-file-for-Ghostscript-as-UTF-8.patch Thanks to Jonas Hahnfeld for the fix. * Bundle our own guile-1.8 again, dropping dependency on guile-2.2-dev. Core developer Jonas Hahnfeld wrote: There are other problems, including the much worse startup time and performance. But you're sold on staying with Guile 2.2 for Debian 11? I fear this gives users a wrong impression because it's shipping something "half-baked"... See https://gitlab.com/lilypond/lilypond/-/issues/6089 This reverts commit c1a0c9179857599fc495d93f6d7579b64bd127b6, with the following changes for LilyPond 2.22 series: - Add "component = guile18" to debian/gbp.conf - Replace ${env:LILYPOND_VERSION} with * where possible for simplicity - Move /usr/bin/lilypond{,-invoke-editor}.real to /usr/lib/$DEB_HOST_MULTIARCH/lilypond/2.22.0/bin/lilypond{,-invoke-editor} (Closes: #852871) - Drop 0101-read_relocation_dir-in-lilypond_datadir-too.patch, and relocate /usr/share/lilypond/2.20.0/etc/relocate/guile.reloc to /usr/lib/$DEB_HOST_MULTIARCH/lilypond/2.22.0/etc/relocate/guile.reloc - Drop 0006-disable-git-diff-check-in-test-baseline.patch - debian/rules: + Set and export GUILE_CFLAGS, GUILE_LIBS and PKG_CONFIG_PATH too so that our copy of libguile.h may be found during LilyPond build + Build Guile 1.8 with $(MAKE) -j$(CPU_COUNT) for reduced build time * Commit Guile 1.8 source code, extracted to guile18/, to our git repository. The guile18/ directory was extracted with the command: tar -C guile18 --strip-components=1 -xf ../lilypond_2.22.0.orig-guile18.tar.gz Checksums-Sha1: ed170a325e6095a0547baa54e7a86c1337c2661c 4500 lilypond_2.22.0-7.dsc 13b37383e69d96123630fc7519af4cd8b0feadb0 2510038 lilypond_2.22.0.orig-guile18.tar.gz b65dd54aa45f5ffc7fc09e56935f24223ff6b521 18023031 lilypond_2.22.0.orig.tar.gz c4a5e9680572d9f75a03c7a1ac7d99d9018efe3a 82564 lilypond_2.22.0-7.debian.tar.xz 819e58bd396a8e02289761ef7c1875ba074a5632 13805 lilypond_2.22.0-7_source.buildinfo Checksums-Sha256: 298f6be0bc9c8721aabaa55a60636465e135e9375e939b2c44ebc4983e20eb9e 4500 lilypond_2.22.0-7.dsc 55ff45dd426c58ef7a5530b4e701c2a6a1e54043c2b69c64206fc105ddd247db 2510038 lilypond_2.22.0.orig-guile18.tar.gz 64ddd03171d247adc243e01a3be3ec2610d97c62b893c253ad02ac50694b0f4e 18023031 lilypond_2.22.0.orig.tar.gz f67ba08979a6bb296a60800fcd1aadb1e018b8ee51be9fdb8bd1d8e372f718ea 82564 lilypond_2.22.0-7.debian.tar.xz 791f61e0f7e2342a6534312ef97100c407688e2847e1370299713d6e75c343ef 13805 lilypond_2.22.0-7_source.buildinfo Files: b472ed4a798f3489a778c8408652c276 4500 tex optional lilypond_2.22.0-7.dsc 2863f46023dd38e33ac37978302c078f 2510038 tex optional lilypond_2.22.0.orig-guile18.tar.gz 4b0d869873b0120bda2e8bd94e1a628a 18023031 tex optional lilypond_2.22.0.orig.tar.gz 319ff292010da60c640eccb2784acbed 82564 tex optional lilypond_2.22.0-7.debian.tar.xz f4ba0fd4dee317d0fad6a78b54a72dee 13805 tex optional lilypond_2.22.0-7_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmAZtMkQHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWazxcUD/9r57Zmur+LUfPkiNhBlU4AMmP4uWFrZSS3 TQXdom765t8XmrYEXA5TVM+RS5peZ4g17dKZnGoUuUFGsQ/7NbisOJnVLEodbm5G TJveOCLroUm7ONc4ewUOVzp7FE49pVgdfGNDV7H2BrvWSgvRr0TuO4i6wZHfvag1 fs5o/THEatRIjPpJk/oE02mTHTeAlzlEF8d80F+S9aut+9OgWT2+yXX5lSbJEe2q 4yz+C3cyaHCKxScuIBNI28OHQDhy4FjR04PVSkzV4ntkrw8yqZeSy8JqZihrt5M+ 24bwUQ50xk+l7d/X8rm6r2DRlMsOMl1waWmAm63jsqMVpZA9lQqOmwNJd6QyKkJD NJKFKRAuobMhlfyDn+aCTzkYXSPibwQbZUvXGTQ6Gi1va0P0iMuectVwKvqlwOEc de1c2IU2Tu9MDmI+8dXWzQl9rKV4nrAqG0IHAYYx5npE0v1vWrHeL4A9oEXP6Fyy 0HDSOpI619ZUJoZPfgj80JvEkByuF3pg/S+P6VH/+My6548QHk0ab5Zlxb4hvWCW o5MGJ3OWRNkmEKMCYjh6YbuPaSm9YoxLmoUArJHsPcaxv5xc0zeqdirpS8N87Z9h jD3rymouvtXwzTZtxhRcYPZhyn/U+idGTvDgM8Urilz89bg1ZZwqWMzVma3v9zL2 qHnWDKG2Dg== =/Aq1 -----END PGP SIGNATURE-----
--- End Message ---
