From: DAINRA <DAINRA@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libXft: update to 2.3.6
Date: Sat, 10 Sep 2022 22:37:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39218@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
There is a new pull request by DAINRA against master on the void-packages repository
https://github.com/DAINRA/void-packages libXft
https://github.com/void-linux/void-packages/pull/39218
libXft: update to 2.3.6
#### 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-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/39218.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libXft-39218.patch --]
[-- Type: text/x-diff, Size: 1100 bytes --]
From 0ce050797a5be4278e5dabaffdeb2f7a65c4ff23 Mon Sep 17 00:00:00 2001
From: Costea Adrian Nicolae <an.costea.2015@gmail.com>
Date: Sat, 10 Sep 2022 23:27:43 +0300
Subject: [PATCH] libXft: update to 2.3.6
---
srcpkgs/libXft/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libXft/template b/srcpkgs/libXft/template
index 263597769d19..406d3b8eeba3 100644
--- a/srcpkgs/libXft/template
+++ b/srcpkgs/libXft/template
@@ -1,6 +1,6 @@
# Template file for 'libXft'
pkgname=libXft
-version=2.3.4
+version=2.3.6
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config"
@@ -9,8 +9,8 @@ short_desc="Library for configuring and customizing font access"
maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://www.x.org"
-distfiles="${XORG_SITE}/lib/${pkgname}-${version}.tar.bz2"
-checksum=57dedaab20914002146bdae0cb0c769ba3f75214c4c91bd2613d6ef79fc9abdd
+distfiles="${XORG_SITE}/lib/${pkgname}-${version}.tar.gz"
+checksum=b7e59f69e0bbabe9438088775f7e5a7c16a572e58b11f9722519385d38192df5
post_install() {
vlicense COPYING
next reply other threads:[~2022-09-10 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 20:37 DAINRA [this message]
2022-09-10 21:37 ` [PR REVIEW] " classabbyamp
2022-09-10 21:48 ` [PR PATCH] [Updated] " DAINRA
2022-09-10 21:52 ` [PR PATCH] [Merged]: " classabbyamp
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-39218@inbox.vuxu.org \
--to=dainra@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).