Your message dated Thu, 14 Jan 2021 10:20:34 +0000 with message-id <[email protected]> and subject line Bug#852871: fixed in lilypond 2.22.0-1 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-1 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: Thu, 14 Jan 2021 02:53:46 -0700 Source: lilypond Architecture: source Version: 2.22.0-1 Distribution: unstable Urgency: medium Maintainer: Anthony Fok <[email protected]> Changed-By: Anthony Fok <[email protected]> Closes: 746005 852871 951801 979839 Changes: lilypond (2.22.0-1) unstable; urgency=medium . * New upstream version 2.22.0 (Closes: #979839, #951801) * Remove embedded guile-1.8 and migrate to system guile-2.2 (Closes: #746005, #852871) * debian/gbp.conf: Remove guile18 component * debian/{control,rules}: Migrate from python2 to python3 * debian/rules: - Run "make doc" with "-j" option in addition to CPU_COUNT as suggested in INSTALL.txt for even faster build - Remove "nuke the parser files" workaround as lily/out/parser.* no longer exist in upstream source - Remove empty override_dh_auto_test-arch as the tests no longer fail without built documentation - Remove override_dh_auto_test-indep as the added "make test-baseline" is not suited for automated Debian builds - Try to "git restore configure" in override_dh_auto_clean * debian/control: - lilypond-doc: Add Replaces: lilypond-doc-html (<< 2.21.82-1~) to avoid upgrade error due to web files reorganization - Build-depend imagemagick-6.q16 instead of imagemagick. "imagemagick" became a dummy package in Debian 9 "stretch", and the aspcud resolver used by experimental buildd would install graphicsmagick-imagemagick-compat (which Provides: imagemagick) which is not that compatible after all and caused lilypond to FTBFS - Remove Authors paragraph from package description as the development team is much larger than before - Bump Standards-Version to 4.5.1 (no change) * debian/lilypond.docs: Rename README.txt to README.md as per upstream * Adjust documentation install file lists for LilyPond 2.21/2.22: - debian/doc_languages.txt: Add PDF package for Portuguese - debian/update_doc_packages: Adjust install file lists for new version - debian/lilypond-doc.install: Remove the no-longer-existing usr/share/doc/lilypond/html/Documentation/*.txt entry - Run "debian/rules update-doc-packages" - Add debian/not-installed to avoid dh_missing errors with debhelper 13 * debian/patches: Delete obsolete patches and disable others for now * debian/remove_w3c_callback: Recognize https too, to fix Lintian privacy-breach-w3c-valid-html errors * Adjust debian/lilypond-doc.install and debian/rules so that the PNG files stay with lilypond-doc package * debian/README.Debian: Minor editing * Cherry-pick upstream fixes for potential crashes with Guile 2.2 - 0001-Protect-against-GC-when-constructing-a-System.patch - 0002-System-Initialize-all-member-variables.patch Checksums-Sha1: cf8313d328e6bb7c99584ab786a5847b2856a4b0 4081 lilypond_2.22.0-1.dsc cc27af8efa977e632932d2633e665381fe24f44e 49320 lilypond_2.22.0-1.debian.tar.xz 61ecd1f6bbbb7c6504c11856a6dcf140b384ac17 13942 lilypond_2.22.0-1_source.buildinfo Checksums-Sha256: 2be2e6c7f27807368a3230a2d0c912429cff7cf894366c8028361450d951dd92 4081 lilypond_2.22.0-1.dsc d3990d84eb50fb2261a807d91687a43bcf4c8dbaa471b95a968dbeb84913f215 49320 lilypond_2.22.0-1.debian.tar.xz 0071df91c6b9320d822a0349f10310831f2ad2e6fb5987a60c0be806ab714d5f 13942 lilypond_2.22.0-1_source.buildinfo Files: 7aea8a028c6deddd798dac49088fd75e 4081 tex optional lilypond_2.22.0-1.dsc 13a87a0d824778503cb5f711394c4f55 49320 tex optional lilypond_2.22.0-1.debian.tar.xz d2abfe5ddf3d9ba51a0ce85282f9e858 13942 tex optional lilypond_2.22.0-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmAAFQUQHGZva2FAZGVi aWFuLm9yZwAKCRDqJQC0EsWaz8nyEACdwYlm2YjYtmGr166sb+iWVwBdTDzXs7nm sR3vct0DEKTW+lqoBYIJGfZJe9UIw9HoknBC85gztFIrntwccoON/0ipW4DMeV+Z 68/zlPZ15htDguEC0WNkGVmBy43d7JgfKYlVHky35ZZM0fUKjKuCJ76MmbR5WvwU hyzeO3/6aiOKiQXhM193aa9ap3NK5xoEyAXtMvOiz/cAp8ZXmmjifBWLciRZVi2r uPhGhUtvMFAhxosA0xBQpoGzfrW87r5RSqerO/7PTwyGVv8e3ljnnmLpr418joBB gGRl7m0+BRHsjkNcTJRiNaRwo6rsg9dYuljr6S/zu4tEfud4mv10LL3dU6EvxOBl ALUvUwIbG69bt1zjHTOo1jYY7SaGJetDFcDXwvRnM9P+QKHovFp7GQjRl8tRaIuW M62FDzYCCap0VSIUsLEvB5aEy78e2vyWEr5oXfqyxviVJwr7sRFaOBKFYBM7vMVz Iy58SmGuiE7CMLG87s02lrFRVLDEAO/ewJju5hPqEc/Asj0cU7MeeE/KlVWjnTcC FZ1R2V6r8yFoLdXyGw4NVdg7HbRd+SXU6dLBhwI+Y1LR8NsK6BDpG7BAgoaURC37 9PTK+AEaR18HeRcAV2AlQ+TmR+AWeTmoTojgy8h74wDUa2g1BDZukkn9BMl8GUt0 JPo6SjA8OQ== =Egci -----END PGP SIGNATURE-----
--- End Message ---
