From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] fontconfig: version bump 2.17.1 -> 2.18.3
Date: Fri, 13 Nov 2026 09:38:49 +0100 [thread overview]
Message-ID: <20261113083849.1378546-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261020133226.3435884-1-s.pueschel@pengutronix.de>
Thanks, applied as 2c33e3363254719d5794cea44333140e9283cf79.
Michael
[sent from post-receive hook]
On Fri, 13 Nov 2026 09:38:49 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> https://gitlab.freedesktop.org/fontconfig/fontconfig/-/releases/2.18.0
> https://gitlab.freedesktop.org/fontconfig/fontconfig/-/releases/2.18.1
> https://gitlab.freedesktop.org/fontconfig/fontconfig/-/releases/2.18.2
> https://gitlab.freedesktop.org/fontconfig/fontconfig/-/releases/2.18.3
>
> The Unicode CaseFolding.txt file was updated and therefore it's year of
> the license has changed (2023 -> 2025) and the wording now also includes
> that the license can also be found in the terms of use link.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20261020133226.3435884-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/fontconfig.make b/rules/fontconfig.make
> index 573a549dd94f..8232dd1184fe 100644
> --- a/rules/fontconfig.make
> +++ b/rules/fontconfig.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_FONTCONFIG) += fontconfig
> #
> # Paths and names
> #
> -FONTCONFIG_VERSION := 2.17.1
> -FONTCONFIG_SHA256 := 82e73b26adad651b236e5f5d4b3074daf8ff0910188808496326bd3449e5261d
> +FONTCONFIG_VERSION := 2.18.3
> +FONTCONFIG_SHA256 := 9ae01e1d53acdef56010c5451cd34aa41d325b2faccd8606448d8fa01b2496b3
> FONTCONFIG := fontconfig-$(FONTCONFIG_VERSION)
> FONTCONFIG_SUFFIX := tar.gz
> FONTCONFIG_URL := https://gitlab.freedesktop.org/fontconfig/fontconfig/-/archive/$(FONTCONFIG_VERSION)/$(FONTCONFIG).$(FONTCONFIG_SUFFIX)
> @@ -26,7 +26,7 @@ FONTCONFIG_LICENSE_FILES := \
> file://COPYING;md5=00252fd272bf2e722925613ad74cb6c7 \
> file://src/ftglue.c;startline=1;endline=8;md5=789386c3d7c853bbce055520a11aaeb9 \
> file://src/fcatomic.h;startline=4;endline=24;md5=89c79dedb0fb324bfa2fae6b7bf7f673 \
> - file://fc-case/CaseFolding.txt;startline=3;endline=6;md5=335eb5842569668c6fe6ea50d00157ef
> + file://fc-case/CaseFolding.txt;startline=3;endline=6;md5=8d4dc0a22d82d97b135f6cb760c6fc90
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2026-11-13 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 13:32 [ptxdist] [PATCH] " Sven Püschel
2026-11-13 8:38 ` Michael Olbrich [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=20261113083849.1378546-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@pengutronix.de \
/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