Accepted lilypond 2.22.0-10~bpo10+1 (source) into buster-backports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 10 Feb 2021 01:03:19 -0700
Source: lilypond
Architecture: source
Version: 2.22.0-10~bpo10+1
Distribution: buster-backports
Urgency: medium
Maintainer: Anthony Fok <foka@debian.org>
Changed-By: Anthony Fok <foka@debian.org>
Closes: 852871 943707 981491 981814
Changes:
lilypond (2.22.0-10~bpo10+1) buster-backports; urgency=medium
.
* Rebuild for buster-backports.
.
lilypond (2.22.0-10) unstable; urgency=medium
.
* debian/rules: Allow "dh_auto_test -a" to fail on hurd-i386 too
.
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)
.
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.
.
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
.
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)
Checksums-Sha1:
b126eb5d844c7d9603f62624e7adf5ea86a4de98 4536 lilypond_2.22.0-10~bpo10+1.dsc
2752667cec2eadf28e3012f5efd4d9a9b9ed1b3e 82764 lilypond_2.22.0-10~bpo10+1.debian.tar.xz
e0c940b94d9ae565b07332206396e362f2ab388a 22969 lilypond_2.22.0-10~bpo10+1_amd64.buildinfo
Checksums-Sha256:
604f09ef061dfb3f19a0a16cae1861e1640cf86e77a529a226c7e3dd42fb1195 4536 lilypond_2.22.0-10~bpo10+1.dsc
ced9fa22d4aa9a04721831a82e6dcecad07c92e60ed768a71d45381779847309 82764 lilypond_2.22.0-10~bpo10+1.debian.tar.xz
5a9f327511c8f7afff67ca064f518dfd737c2342f31d47ec9f105bcb09f71545 22969 lilypond_2.22.0-10~bpo10+1_amd64.buildinfo
Files:
28279408d5dfcc3eaf445a9a9c94b817 4536 tex optional lilypond_2.22.0-10~bpo10+1.dsc
d67ac75d2eb81ac02a6371498289cbd8 82764 tex optional lilypond_2.22.0-10~bpo10+1.debian.tar.xz
f2affd46a08deaf4292a11edb61ac24e 22969 tex optional lilypond_2.22.0-10~bpo10+1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmAkFgkQHGZva2FAZGVi
aWFuLm9yZwAKCRDqJQC0EsWaz0ufD/oDhvvQuW2oScksndIuOzcedWfA1EtIlElK
x7FOZec3aqUWPpMiOxmoEY+DxAvfp1a0lyM120kj6G7BNdPEDUzKwdMHq2Tp7bG0
HwxKOp2kEzUBkQLx9wA/59zyODkZUFvd9aTIhMJLHxpkWt+rgIQAIu/Ft3DcMWBr
XIy+QjBSJmeDBxxQJZxkAfZ+BCnglWW+2bAC2DBvRtDeZLUDkL8VhlvmBWp9f4Yg
FT00KWxotRIfaLvnnXg5gkGGciso0KvfJ2584jFRYB0DWPuWSyfU4XMYBzW2Wmwl
N3CSB4r0Y7VI/cvBLY/zQBFVsNcpW0yRb7DyKdhF4fIL4W0UNcgaMPJl2hVF39yd
jbtZv4emzyWCpSZgZ6nI74doeLdv/bC6YRdNN1zu4IQppIkXF7qN2bzLGB+1lFG3
Is1emd6tntWUcWPutjP4ECrozKmsrXVNxrran1iIlrzTfRVzHUH/VOWyjKzt2Hwt
GbkMp5K+xfSlzhPkRJGLC3344bNQmvzgLOwn+sTWI1xmrzwZrwosCr6gs7V8BQMG
evIAUZryOoDmYMZ2aQ3ca7ciRh0PiTsVrkSpw25BPNeYTasarUNclwe4mkJ5h7IB
+6YeOD2HFiGUVZJveEJf0cLj8OPLrO6m4+Okw33l5xV4c3HU7TNHjF6+lFR+ywPG
04+k6ALJIg==
=9vyf
-----END PGP SIGNATURE-----
Reply to: