Change logs for lilypond source package in Hirsute

  • lilypond (2.22.0-10) unstable; urgency=medium
    
      * debian/rules: Allow "dh_auto_test -a" to fail on hurd-i386 too
    
     -- Anthony Fok <email address hidden>  Tue, 09 Feb 2021 23:09:36 -0700
  • lilypond (2.22.0-9) unstable; urgency=medium
    
      * lilypond-doc: Remove stray symlink /usr/share/info/lilypond/user
        which would otherwise block the /usr/share/info/lilypond dir_to_symlink
        conversion since 2.22.0-6 and prevent lilypond-doc from upgrading.
        Thanks to Nicolas Patrois and Gabriele Stilli for reporting the bug.
        (Closes: #981814)
    
     -- Anthony Fok <email address hidden>  Tue, 09 Feb 2021 18:18:33 -0700
  • lilypond (2.22.0-8) unstable; urgency=medium
    
      * debian/rules: Move debian/guile.reloc prerequisite
        from override_dh_auto_install-indep override_dh_auto_install-arch.
        Fixes bug introduced in a19f5480 when I relocated
        /usr/share/lilypond/2.20.0/etc/relocate/guile.reloc to
        /usr/lib/$DEB_HOST_MULTIARCH/lilypond/2.22.0/etc/relocate/guile.reloc
        but failed to update debian/rules accordingly.
    
     -- Anthony Fok <email address hidden>  Tue, 02 Feb 2021 14:49:35 -0700
  • lilypond (2.22.0-6) unstable; urgency=medium
    
      * debian/control: Build-Depends on fonts-urw-base35 explicitly.
        LilyPond's configure recommends installing "URW++ OTF fonts", and while
        libgs9-common happens to depend on fonts-urw-base35 since 2019-07-24
        with ghostscript (>= 9.27~dfsg-3) for bullseye but not for buster.
      * lilypond-doc.maintscript: dir_to_symlink /usr/share/info/lilypond.
        Fixes Lintian "lilypond-doc: info-document-missing-image-file" warnings.
        This was previously symlink_to_dir, see changelog for 2.18.2-4 from 2014.
      * lilypond-doc.doc-base-special: Remove reference to *.txt files
        which are no longer installed.  Fixes Lintian error "lilypond-doc:
        doc-base-file-references-missing-file lilypond-doc:10
        /usr/share/doc/lilypond/html/Documentation/*.txt*".
      * Refresh and reinstate debian/patches/add_dircategories_to_documentation.
        Fixes Lintian errors info-document-missing-dir-entry and
        info-document-missing-dir-entry, see #648689.  Note that for
        Documentation/{de,en,fr,it}/web.texi, I was unable to apply the patches
        as is, so these files may need to be fixed in the future.
        (Closes: #981491)
      * Remove obsolete debian/preinst (lilypond.preinst)
        that I wrote over 20 years ago to fix my previous packaging error
        regarding LilyPond TeX font installation, but is no longer relevant
        for LilyPond 2.x, and created an unnecessary dependency on tetex-bin
        or texlive-binaries due to its use of kpsewhich...
        Thanks to Mauro Sacchetto for noticing something amiss and reported it.
        (Closes: #943707)
    
     -- Anthony Fok <email address hidden>  Mon, 01 Feb 2021 07:06:06 -0700
  • lilypond (2.22.0-5) unstable; urgency=medium
    
      * debian/control: lilypond-doc: Add "Breaks: lilypond-doc-html (<< 2.21)"
        in addition to the Replaces that was added in 2.21.82-1~exp2 and 2.22.0-1
        because "[n]ormally, Breaks should be used in conjunction with Replaces"
        according to Debian Policy 7.6.
        Thanks to Andreas Beckmann for the detailed bug report (Closes: #979406)
    
     -- Anthony Fok <email address hidden>  Tue, 26 Jan 2021 06:00:57 -0700
  • lilypond (2.22.0-4) unstable; urgency=medium
    
      * debian/control: Build-depends on imagemagick for kfreebsd-any
        otherwise build would not even pass the configure stage
      * debian/rules: Comment out architecture-specific --disable-optimising
        as it does not seem to be needed for any architecture any more
    
     -- Anthony Fok <email address hidden>  Sun, 24 Jan 2021 00:48:09 -0700
  • lilypond (2.22.0-3) unstable; urgency=medium
    
      * debian/rules:
        - Set --enable-optimization on i386 and kfreebsd-i386, and
          set --disable-optimization on hppa and see if it passes the test
        - Add override_dh_auto_test-arch to allow "dh_auto_test -a" to fail
          on hppa, kfreebsd-amd64 and kfreebsd-i386:
          + hppa: fails on snippet-names-e9c0d84b44e6ce39576ac3a756562e43.ly
          + kfreebsd-amd64 and kfreebsd-i386: imagemagick.q16 is missing 
      * debian/control:
        - Skip build-dependency of imagemagick.q16 on kfreebsd-any
    
     -- Anthony Fok <email address hidden>  Sat, 23 Jan 2021 08:03:00 -0700
  • lilypond (2.22.0-2) unstable; urgency=medium
    
      * Workaround missing PATH_MAX on Hurd (lily/lily-guile.cc)
        to fix FTBFS on Hurd.  See debian/patches/0003-Hurd-PATH_MAX.patch
      * Revert "debian/control: Build-depend imagemagick-6.q16 instead of
        imagemagick" for this non-experimental build and see if this would
        resolve the BD-Uninstallable status due to "libheif1 depends on missing:
        - libx265-179:kfreebsd-i386 (>= 3.2)" on kfreebsd-amd64 and kfreebsd-i386
    
     -- Anthony Fok <email address hidden>  Fri, 15 Jan 2021 22:58:17 -0700
  • 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
    
     -- Anthony Fok <email address hidden>  Thu, 14 Jan 2021 02:53:46 -0700
  • lilypond (2.20.0-4) unstable; urgency=medium
    
      * Source-only upload for migration to testing
    
     -- Anthony Fok <email address hidden>  Sun, 06 Dec 2020 23:09:18 -0700
  • lilypond (2.20.0-3) unstable; urgency=medium
    
      * Fix Lintian error bogus-mail-host-in-debian-changelog
      * Bump debhelper dependency to "Build-Depends: debhelper-compat (= 13)"
      * debian/control: Suggests: python3-lxml.
        Thanks to Benjamin Barenblat for the suggestion. (Closes: #904828)
      * debian/control: Replace old package names in dependencies
      * Split the fonts into a separate lilypond-fonts package (Closes: #87700)
      * Add 0006-disable-git-diff-check-in-test-baseline.patch
        to disable "git diff" check in test-baseline
        to avoid inadvertent Debian build failure with .git directory
      * Add "Rules-Requires-Root: no" to debian/control
      * Update debian/update_doc_packages to wrap Depends list
      * Add new language Portuguese for HTML and PDF doc packages
      * Fix Lintian "debian-watch-uses-insecure-uri" info
      * Fix Lintian "missing-build-dependency-for-dh-addon python2" error
    
     -- Anthony Fok <email address hidden>  Sat, 05 Dec 2020 04:42:34 -0700
  • lilypond (2.20.0-2) unstable; urgency=medium
    
      * Patch Guile-1.8 to the latest branch_release-1-8 branch
        found in Guile git repository on Savannah, see patches 1801 to 1825.
        In particular, 1812-Fix-stack-growth-direction-check.patch,
        originally written for Autoconf by Paul Eggert for Autoconf
        and pulled into Guile-2.0 in 2011, fixed a build error with
        -O3 back then, and fixes FTBFS with gcc-10 nowadays,
        due to a bug in find_stack_direction() code in configure.in.
        See http://lists.gnu.org/archive/html/bug-autoconf/2011-06/msg00035.html
        for the whole story. (Closes: #966353)
      * Call /usr/share/dh-python/dh_python2 directly
        in debian/rules since /usr/bin/dh_python2 was removed
      * This rebuild allows dh_python2 to generate the now correct dependency
        on python2:all instead of python:all (Closes: #969723)
      * Add debian/patches/.gitignore to re-include *.patch files
        which were excluded by upstream .gitignore file
      * scm: disable embedded-ps and embedded-svg in -dsafe mode, CVE-2020-17353.
        This is a cherry-pick of upstream's fix, see
        http://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=b84ea47
        (Closes: #968993)
      * Take over as Maintainer from Don Armstrong as suggested by Don.
        Thank you Don for your many years of great work, and we look forward
        to your continued contributions as co-maintainer for many years to come!
    
     -- Anthony Fok <email address hidden>  Wed, 09 Sep 2020 15:41:38 -0600
  • lilypond (2.20.0-1) unstable; urgency=medium
    
      * New upstream version 2.20.0
      * Merge branch 'debian/experimental' into debian/sid
      * Revert "Adopt upstream patch to fix FTBFS with Ghostscript 9.50"
        as it is already included in 2.20.0 release
      * Refresh debian/patches/use_cstring_and_ctype_includes
      * Update debian/copyright
      * Remove build-dependency on autotools-dev, unneeded since
        debhelper-compat (= 10)
    
     -- Anthony Fok <email address hidden>  Wed, 04 Mar 2020 16:36:44 -0700