Accepted lilypond 2.24.0-2 (source) into unstable
- To: debian-devel-changes@lists.debian.org
- Subject: Accepted lilypond 2.24.0-2 (source) into unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Sun, 29 Jan 2023 02:40:45 +0000
- Debian: DAK
- Debian-architecture: source
- Debian-archive-action: accept
- Debian-changes: lilypond_2.24.0-2_source.changes
- Debian-source: lilypond
- Debian-suite: unstable
- Debian-version: 2.24.0-2
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ftp-master.debian.org; s=smtpauto.fasolo; h=Date:Message-Id: Content-Transfer-Encoding:Content-Type:Subject:MIME-Version:To:Reply-To:From: Cc:Content-ID:Content-Description:In-Reply-To:References; bh=SJG1TCGnr1mThkTlmof7FFRrPra6859w9VUlOe7/mtw=; b=cFcEpa6KoW3hnuQ3/3BlPqQHE8 mzxBcH9Jggo5EDi8atwbgG/8TAJMEBZ9/ojjSvnqRKZvhR5deRBwFxVcs6CyrRDJsDeQ/a0jxYURs wVJVjfAA+48zD1XRV8y+8kdrQ/Bew1C6YtGdBNV78oVudxtJFpLrHhAi6QGdES0vjqd8XbkFbtFrq lwdbwjN55uoxVCDy7LFSYY1nQy8MyP7Za36fws+VCWhGBC7Etgd80HOXvERFlBjkFl/xRKZaX9yTz uCCi/g9YAMUNIKOveoduxfuMJ5YPMXp0DVS2giRQjgiF0NC1C1LNArdJO5myn64HuC5zhcRUB0CXn ZWKrWsQg==;
- Mail-followup-to: debian-devel@lists.debian.org
- Message-id: <E1pLxcb-005OTN-3V@fasolo.debian.org>
- Reply-to: debian-devel@lists.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 28 Jan 2023 17:10:08 -0700
Source: lilypond
Architecture: source
Version: 2.24.0-2
Distribution: unstable
Urgency: medium
Maintainer: Anthony Fok <foka@debian.org>
Changed-By: Anthony Fok <foka@debian.org>
Changes:
lilypond (2.24.0-2) unstable; urgency=medium
.
* debian/rules: Remove "$(MAKE) install-info" to avoid symlink issue.
Since v2.23.3 (thus v2.24.0), the install-info target behaviour changed
to copy images instead of using symlink, while install-doc target now
depends on the install-info-noimages which keeps the old behaviour
that our Debian packaging desires. Running "$(MAKE) install-doc" alone
is sufficient. This fixes lilypond-doc upgrade error "unable to open
'/usr/share/info/lilypond/00/lily-12276734.png.dpkg-new': No such file
or directory". See https://gitlab.com/lilypond/lilypond/-/issues/6110
and commit 6e8293f5eef359de1097ef7e3a183fd3ac630fa7 for details.
Checksums-Sha1:
1e89e8146d02bb1cdb8de949f843a7d43842cecd 4121 lilypond_2.24.0-2.dsc
c70136d1f685e1763f9d648fb5bf690c61d48eab 47132 lilypond_2.24.0-2.debian.tar.xz
73b1701e7e034574abb5f5dcc4588243b1c0fe1f 23031 lilypond_2.24.0-2_amd64.buildinfo
Checksums-Sha256:
fa1a0e49af743f3e3fd1268398c4d883d8b00044844f22379c430e94d2e89ff6 4121 lilypond_2.24.0-2.dsc
fdc9215f69dedc9d8c5bdd40bb5c38e5cad91ae7c9eaa41104f0c4ba5140537c 47132 lilypond_2.24.0-2.debian.tar.xz
a71c770ad464d2d05f5a0940c481989fd8119a7fa93c77249a438fe37a9bba8c 23031 lilypond_2.24.0-2_amd64.buildinfo
Files:
75aa68b1279ec70035a1453d2d547c10 4121 tex optional lilypond_2.24.0-2.dsc
b9416b52aedd19ad0437c404195d48a0 47132 tex optional lilypond_2.24.0-2.debian.tar.xz
885ad23b16f9c4079070cbff5f752e52 23031 tex optional lilypond_2.24.0-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAmPV0Z4QHGZva2FAZGVi
aWFuLm9yZwAKCRDqJQC0EsWazziKD/44gJB6FCLz7HvO1wOBCNIEWqgZxlyxOScl
W59+xSqv4GFVgsGS5KXs30ozv56q33zciONb6uuvGESHIj2VhCO3sDNml+Iolemb
DRWZTQr/w/eYlsF6yFx0tWqisfJWmIgmqWI4ChYdnmK5YFnOTAvVPYqMf1fij0eF
H+chbZoVXwmWJepakk15IhLempMnxe/d+YHHCdBrf8o971D4tRuS4gmMtdhSPbID
VWyBnFxWDcKvjbIKeX7rQZcPujOj2XXOR73tVbXijwGJKZSUHUIGVlsvD3AcG+1e
5QleAGCFvVGiRsU8RDJQFx9AJJNQoa1hTyq7I18/F8vpyXHa/xgLf92TXAZ0xKI9
NhZ4aXcn+SDTq8Ms0w6davbrVpqm5DAnMIC8AdbBh+LXi2VjwpZX9ls5jDM3SnAk
YFOpVPO309k4GoWPFcgDJuzXqOuqvLzjCjv5+UVS9X8+/aZqF0PDRV2XEDLhfk3q
hB8tEmRsgoRxAu+v68uB2KC5/vgLsVve+ZVQ6Oh3TjE2TylgmDILp71368bQOeb+
+5UXDxkkC8DghnhbQ05tl0F66P8ZyqoSdy9KoSf9uSnAvbxQHmEROiShQwOTpeC3
On5GaaWLFnpRv7uxBL+01/ciLLl1GU7QdjsG1IcMXhjxaEHupIXylEaWlC/xPBVq
r2B9dmG5Lw==
=Gva5
-----END PGP SIGNATURE-----