[PR PATCH] lilypond: update to 2.22.0

[PR PATCH] lilypond: update to 2.22.0

[newbluemoon]

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

There is a new pull request by newbluemoon against master on the void-packages repository

https://github.com/newbluemoon/void-packages lilypond
https://github.com/void-linux/void-packages/pull/27849

lilypond: update to 2.22.0


A patch file from https://github.com/void-linux/void-packages/pull/27849.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lilypond-27849.patch --]
[-- Type: text/x-diff, Size: 2310 bytes --]

From 00ea80362b9b245fd52b2f06d4c77b2394f316b8 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Tue, 12 Jan 2021 07:27:44 +0100
Subject: [PATCH 1/2] lilypond: update to 2.22.0

---
 srcpkgs/lilypond/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/lilypond/template b/srcpkgs/lilypond/template
index 9d400b673cb..c3be0ae65c0 100644
--- a/srcpkgs/lilypond/template
+++ b/srcpkgs/lilypond/template
@@ -1,6 +1,6 @@
 # Template file for 'lilypond'
 pkgname=lilypond
-version=2.21.82
+version=2.22.0
 revision=1
 build_wrksrc="build"
 build_style="gnu-configure"
@@ -16,8 +16,8 @@ short_desc="Music engraving program"
 maintainer="newbluemoon <blaumolch@mailbox.org>"
 license="GPL-3.0-or-later, GFDL-1.3-or-later"
 homepage="https://lilypond.org/"
-distfiles="https://lilypond.org/downloads/sources/v2.21/lilypond-${version}.tar.gz"
-checksum=f0bd17cccee771ed4a2e0db1ec81c98d9f52e47090e5dcc085de65dd8cc4bdd9
+distfiles="https://lilypond.org/downloads/sources/v2.22/lilypond-${version}.tar.gz"
+checksum=64ddd03171d247adc243e01a3be3ec2610d97c62b893c253ad02ac50694b0f4e
 python_version=3
 
 if [ -n "${CROSS_BUILD}" ]; then

From c3dfd4bc9260f4d61eb72047307d8e00fe9462c0 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Tue, 12 Jan 2021 07:28:31 +0100
Subject: [PATCH 2/2] lilypond-doc: update to 2.22.0

---
 srcpkgs/lilypond-doc/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/lilypond-doc/template b/srcpkgs/lilypond-doc/template
index 7c1184d9964..3d5a809a961 100644
--- a/srcpkgs/lilypond-doc/template
+++ b/srcpkgs/lilypond-doc/template
@@ -1,6 +1,6 @@
 # Template file for 'lilypond-doc'
 pkgname=lilypond-doc
-version=2.21.82
+version=2.22.0
 revision=1
 create_wrksrc=yes
 short_desc="Documentation for the lilypond music engraving program"
@@ -8,7 +8,7 @@ maintainer="newbluemoon <blaumolch@mailbox.org>"
 license="GPL-3.0-or-later, GFDL-1.3-or-later"
 homepage="http://lilypond.org/"
 distfiles="http://lilypond.org/downloads/binaries/documentation/lilypond-${version}-1.documentation.tar.bz2"
-checksum=f8cb74f452472b38fd1e67a09405efd0f52d38b3b85a62c5e998a698dd82c2b7
+checksum=2698a407424e29abf834d12376fb33aa1bfa2afa8b7f3537120b0817b982bd8f
 
 do_install() {
 	vmkdir usr

Re: lilypond: update to 2.22.0

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/27849#issuecomment-763254935

Comment:
Not sure why tests failed in CI, would be nice to track down. I could run them successfully locally :)

Re: [PR PATCH] [Merged]: lilypond: update to 2.22.0

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 160 bytes --]

There's a merged pull request on the void-packages repository

lilypond: update to 2.22.0
https://github.com/void-linux/void-packages/pull/27849

Description:

Re: lilypond: update to 2.22.0

[newbluemoon]

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

New comment by newbluemoon on void-packages repository

https://github.com/void-linux/void-packages/pull/27849#issuecomment-763356357

Comment:
Maybe the test fails because of some parallelism issue. The test runs multiple instances of lilypond to create some output files which are then compared to a baseline; maybe a check is run before an output file is created. I can try to disable parallelism for checking with the next update.

However, the intention of the test is to compare changes a developer made against a release version; i.e. a baseline is created regarding the release and the test checks if/how the developer’s changes deviate from that baseline.
So other than checking that lilypond runs correctly the test here is of not much use, because the baseline and what is checked against it is the same, apparently. ;)