Github messages for voidlinux
 help / color / mirror / Atom feed
From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fontconfig: update to 2.13.96.
Date: Fri, 24 Jun 2022 14:51:54 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37670@inbox.vuxu.org> (raw)

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

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

https://github.com/zlice/void-packages fontconfig_2.13.96
https://github.com/void-linux/void-packages/pull/37670

fontconfig: update to 2.13.96.

#### Testing the changes
- I tested the changes in this PR: **yes**

- I built this PR locally for my native architecture, **x86_64**


#### Comments

Besides being from 2018, there are a few bugs related to `~/.local/share/fonts` causing font rebuilds of some sort in Firefox. This leads to crashes and random windows/menus closing. Updating to this so far seems to have fixed that with minor testing.

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

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

From cf584a0c999170909a15247141c0b3730bebde5b Mon Sep 17 00:00:00 2001
From: zlice <zlice555@gmail.com>
Date: Fri, 24 Jun 2022 08:49:16 -0400
Subject: [PATCH] fontconfig: update to 2.13.96.

---
 srcpkgs/fontconfig/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/fontconfig/template b/srcpkgs/fontconfig/template
index 89c0cf5ea240..452368da94e6 100644
--- a/srcpkgs/fontconfig/template
+++ b/srcpkgs/fontconfig/template
@@ -1,18 +1,18 @@
 # Template file for 'fontconfig'
 pkgname=fontconfig
-version=2.13.1
-revision=3
+version=2.13.96
+revision=1
 build_style=gnu-configure
 configure_args="--enable-static --enable-docs --with-cache-dir=/var/cache/${pkgname}"
 hostmakedepends="gperf pkg-config"
-makedepends="expat-devel freetype-devel libuuid-devel"
+makedepends="expat-devel freetype-devel libuuid-devel python3"
 conf_files="/etc/fonts/fonts.conf"
 short_desc="Library for configuring and customizing font access"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="http://www.fontconfig.org"
-distfiles="${FREEDESKTOP_SITE}/${pkgname}/release/${pkgname}-${version}.tar.bz2"
-checksum=f655dd2a986d7aa97e052261b36aa67b0a64989496361eca8d604e6414006741
+distfiles="${FREEDESKTOP_SITE}/${pkgname}/release/${pkgname}-${version}.tar.xz"
+checksum=d816a920384aa91bc0ebf20c3b51c59c2153fdf65de0b5564bf9e8473443d637
 
 pre_build() {
 	# trick to regenerate hash functions :-)

             reply	other threads:[~2022-06-24 12:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 12:51 zlice [this message]
2022-06-24 12:54 ` [PR PATCH] [Updated] " zlice
2022-06-24 13:04 ` zlice
2022-06-24 13:07 ` zlice
2022-06-27 15:42 ` [PR PATCH] [Updated] " zlice
2022-06-27 15:53 ` zlice
2022-06-27 15:56 ` zlice
2022-06-27 15:56 ` [PR PATCH] [Closed]: " zlice

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-37670@inbox.vuxu.org \
    --to=zlice@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).