[FFe] Please sync lilypond 2.20.0-1 from Debian

Bug #1867129 reported by Anthony Fok
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lilypond (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please update lilypond (universe, focal) from 2.19.81+really-2.18.2-14 to 2.20.0-1 by syncing from Debian sid.

LilyPond 2.18.2 was released on March 24, 2014, almost 6 years ago, and 2.20.0 (released on March 1, 2020) is a long-awaited and much welcomed release. I am a frequent user of LilyPond myself, and 2.20.0-1 works very well indeed, and for me, at least, fixes a problem in 2.18.2 where LilyPond's generated .ps file would trip up Ghostscript's ps2pdf operation when the beautiful Noto Serif CJK or Noto Sans CJK Chinese fonts are used.

======================================================================

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

======================================================================

NEWS.txt, build log etc. are / will be attached.

Tags: focal
Revision history for this message
Anthony Fok (foka) wrote :
Revision history for this message
Anthony Fok (foka) wrote :

Please see https://buildd.debian.org/status/package.php?p=lilypond for full build logs on various architectures.

Anthony Fok (foka)
tags: added: focal
Revision history for this message
Jeremy Bícha (jbicha) wrote :
Changed in lilypond (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.