From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: lilypond: update to 2.23.80
Date: Thu, 10 Nov 2022 21:21:25 +0100 [thread overview]
Message-ID: <20221110202125.oTKqhiNo4B4AxLtxpzMeHZZAFPmSrmTm7pnX5NmHcuQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38674@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
There's a merged pull request on the void-packages repository
lilypond: update to 2.23.80
https://github.com/void-linux/void-packages/pull/38674
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- armv7l-musl
- i686
- aarch64
New font package urw-core35-fonts, because lilypond doesn’t bundle the required OTF fonts anymore and the URW++ ones are used in favour of the TeX Gyre fonts, see
https://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=5689c2721530c6ded22b6291ebb06d10adb5bc28
There is no release, unfortunately, but I hope it is ok to make an exception in this case. :)
prev parent reply other threads:[~2022-11-10 20:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 20:10 [PR PATCH] Lilypond newbluemoon
2022-08-15 3:58 ` lilypond: update to 2.23.11 newbluemoon
2022-08-15 9:39 ` icp1994
2022-08-21 12:56 ` [PR PATCH] [Updated] " newbluemoon
2022-08-21 13:02 ` newbluemoon
2022-08-28 19:51 ` [PR PATCH] [Updated] " newbluemoon
2022-08-28 20:15 ` lilypond: update to 2.23.12 newbluemoon
2022-09-22 7:10 ` [PR REVIEW] " classabbyamp
2022-09-26 4:50 ` [PR PATCH] [Updated] " newbluemoon
2022-09-26 4:53 ` [PR REVIEW] lilypond: update to 2.23.13 newbluemoon
2022-09-26 5:02 ` classabbyamp
2022-09-26 5:11 ` newbluemoon
2022-09-26 5:15 ` classabbyamp
2022-10-04 6:30 ` [PR PATCH] [Updated] " newbluemoon
2022-10-12 5:03 ` newbluemoon
2022-10-12 5:10 ` lilypond: update to 2.23.14 newbluemoon
2022-10-12 5:21 ` classabbyamp
2022-10-12 5:25 ` newbluemoon
2022-10-12 5:46 ` classabbyamp
2022-11-04 4:50 ` [PR PATCH] [Updated] " newbluemoon
2022-11-09 19:39 ` lilypond: update to 2.23.80 classabbyamp
2022-11-09 19:49 ` [PR PATCH] [Updated] " newbluemoon
2022-11-09 19:51 ` newbluemoon
2022-11-10 6:12 ` classabbyamp
2022-11-10 20:03 ` [PR PATCH] [Updated] " newbluemoon
2022-11-10 20:19 ` newbluemoon
2022-11-10 20:21 ` classabbyamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221110202125.oTKqhiNo4B4AxLtxpzMeHZZAFPmSrmTm7pnX5NmHcuQ@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).