From: mdkcore0 <mdkcore0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fontconfig: update to 2.14.1
Date: Tue, 25 Oct 2022 22:43:54 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40163@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
There is a new pull request by mdkcore0 against master on the void-packages repository
https://github.com/mdkcore0/void-packages update-fontconfig
https://github.com/void-linux/void-packages/pull/40163
fontconfig: update to 2.14.1
#### 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-libc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv7l (crossbuild)
- i686-libc (crossbuild)
A patch file from https://github.com/void-linux/void-packages/pull/40163.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-fontconfig-40163.patch --]
[-- Type: text/x-diff, Size: 1094 bytes --]
From 304ce77af9bcc2c304ae4bbb44f6b5a78d79bb6a Mon Sep 17 00:00:00 2001
From: Rodrigo Oliveira <mdkcore@qtrnn.io>
Date: Tue, 25 Oct 2022 16:33:10 -0300
Subject: [PATCH] fontconfig: update to 2.14.1
---
srcpkgs/fontconfig/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/fontconfig/template b/srcpkgs/fontconfig/template
index 75597231084c..636df1d5da7b 100644
--- a/srcpkgs/fontconfig/template
+++ b/srcpkgs/fontconfig/template
@@ -1,6 +1,6 @@
# Template file for 'fontconfig'
pkgname=fontconfig
-version=2.14.0
+version=2.14.1
revision=1
build_style=gnu-configure
configure_args="--enable-static --enable-docs --with-cache-dir=/var/cache/${pkgname}"
@@ -13,7 +13,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="http://www.fontconfig.org"
distfiles="${FREEDESKTOP_SITE}/${pkgname}/release/${pkgname}-${version}.tar.xz"
-checksum=dcbeb84c9c74bbfdb133d535fe1c7bedc9f2221a8daf3914b984c44c520e9bac
+checksum=298e883f6e11d2c5e6d53c8a8394de58d563902cfab934e6be12fb5a5f361ef0
post_install() {
if [ "$CROSS_BUILD" ]; then
next reply other threads:[~2022-10-25 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 20:43 mdkcore0 [this message]
2023-01-21 16:06 ` [PR PATCH] [Merged]: " ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40163@inbox.vuxu.org \
--to=mdkcore0@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).