From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pango: update to 1.51.0
Date: Mon, 16 Oct 2023 14:34:44 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46722@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
There is a new pull request by chrysos349 against master on the void-packages repository
https://github.com/chrysos349/void-packages pango
https://github.com/void-linux/void-packages/pull/46722
pango: update to 1.51.0
@cinerea0
required for newer gnome apps
#### 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)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl x
- armv7l x
- armv6l-musl x
A patch file from https://github.com/void-linux/void-packages/pull/46722.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pango-46722.patch --]
[-- Type: text/x-diff, Size: 1285 bytes --]
From 57a2814618b1a8fae7a704b81e0345890033948e Mon Sep 17 00:00:00 2001
From: chrysos349 <chrysostom349@gmail.com>
Date: Mon, 16 Oct 2023 15:20:11 +0300
Subject: [PATCH] pango: update to 1.51.0
---
srcpkgs/pango/template | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/srcpkgs/pango/template b/srcpkgs/pango/template
index 934c92537f398..482b163bf20b5 100644
--- a/srcpkgs/pango/template
+++ b/srcpkgs/pango/template
@@ -1,6 +1,6 @@
# Template file for 'pango'
pkgname=pango
-version=1.50.14
+version=1.51.0
revision=1
build_style=meson
build_helper=gir
@@ -14,18 +14,12 @@ license="LGPL-2.1-or-later"
homepage="https://www.pango.org/"
changelog="https://gitlab.gnome.org/GNOME/pango/-/raw/main/NEWS"
distfiles="${GNOME_SITE}/pango/${version%.*}/pango-${version}.tar.xz"
-checksum=1d67f205bfc318c27a29cfdfb6828568df566795df0cb51d2189cde7f2d581e8
-make_check=no # doesn't pass its own tests
+checksum=74efc109ae6f903bbe6af77eaa2ac6094b8ee245a2e23f132a7a8f0862d1a9f5
# Package build options
build_options="gir"
build_options_default="gir"
-post_install() {
- rm -rf -- ${DESTDIR}/usr/share/installed-tests
- rm -rf -- ${DESTDIR}/usr/libexec/installed-tests
-}
-
pango-xft_package() {
short_desc+=" - X font rendering"
pkg_install() {
next reply other threads:[~2023-10-16 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 12:34 chrysos349 [this message]
2023-10-16 12:36 ` paper42
2023-10-16 12:36 ` [PR PATCH] [Closed]: " paper42
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-46722@inbox.vuxu.org \
--to=chrysos349@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).