From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] fonttools: update to 4.39.3.
Date: Wed, 10 May 2023 18:14:06 +0200 [thread overview]
Message-ID: <20230510161406._YmNL9vRe0uEWnOc8GBsyL4_0d6wagRa-FlzysyILUY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43426@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
There is an updated pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages fonttools
https://github.com/void-linux/void-packages/pull/43426
fonttools: update to 4.39.3.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
A patch file from https://github.com/void-linux/void-packages/pull/43426.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fonttools-43426.patch --]
[-- Type: text/x-diff, Size: 1358 bytes --]
From 5bbda43a8c6c91b70d8aad93b42b10fe9cdcec10 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Fri, 14 Apr 2023 00:37:54 +0530
Subject: [PATCH] fonttools: update to 4.39.4.
---
srcpkgs/fonttools/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/fonttools/template b/srcpkgs/fonttools/template
index e655bff17ec7..6d2160272853 100644
--- a/srcpkgs/fonttools/template
+++ b/srcpkgs/fonttools/template
@@ -1,6 +1,6 @@
# Template file for 'fonttools'
pkgname=fonttools
-version=4.38.0
+version=4.39.4
revision=1
build_style=python3-module
make_check_args="--deselect Tests/otlLib/optimize_test.py::test_main
@@ -13,8 +13,8 @@ maintainer="svenper <svenper@tuta.io>"
license="MIT, OFL-1.1, BSD-3-Clause"
homepage="https://github.com/fonttools/fonttools"
changelog="https://raw.githubusercontent.com/fonttools/fonttools/main/NEWS.rst"
-distfiles="https://github.com/fonttools/fonttools/archive/${version}.tar.gz"
-checksum=764c569221fb437d0c3937d19d3e38e137d324f225fb30e54ef0aaa2d6f7a289
+distfiles="https://github.com/fonttools/fonttools/archive/refs/tags/${version}.tar.gz"
+checksum=9fab7f15ad7a0b5cd040331090b726c81d8b0d7b043bb348c7dc242d901b4ee5
replaces="python-fonttools>=0 python3-fonttools>=0"
provides="python-fonttools-${version}_${revision} python3-fonttools-${version}_${revision}"
next prev parent reply other threads:[~2023-05-10 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:08 [PR PATCH] " icp1994
2023-05-10 16:14 ` icp1994 [this message]
2023-05-17 11:46 ` [PR PATCH] [Merged]: fonttools: update to 4.39.4 leahneukirchen
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=20230510161406._YmNL9vRe0uEWnOc8GBsyL4_0d6wagRa-FlzysyILUY@z \
--to=icp1994@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).