Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pango: update to 1.50.11
Date: Sun, 20 Nov 2022 03:42:39 +0100	[thread overview]
Message-ID: <20221120024239.fYMVahW3-SojXHZtAdvKmo9aoDHvE9G1cRtKFaQbRy4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40156@inbox.vuxu.org>

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

There is an updated pull request by cinerea0 against master on the void-packages repository

https://github.com/cinerea0/void-packages pan
https://github.com/void-linux/void-packages/pull/40156

pango: update to 1.50.11
#### Testing the changes
- I tested the changes in this PR: **YES**


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

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

From 9d30e54e762ce8193163a008d0588cfa1f209136 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Sat, 19 Nov 2022 21:42:06 -0500
Subject: [PATCH] pango: update to 1.50.12

---
 .../pango/patches/fix-segfault-no-font.patch  | 21 -------------------
 srcpkgs/pango/template                        |  8 +++----
 2 files changed, 4 insertions(+), 25 deletions(-)
 delete mode 100644 srcpkgs/pango/patches/fix-segfault-no-font.patch

diff --git a/srcpkgs/pango/patches/fix-segfault-no-font.patch b/srcpkgs/pango/patches/fix-segfault-no-font.patch
deleted file mode 100644
index 4aec1d27b237..000000000000
--- a/srcpkgs/pango/patches/fix-segfault-no-font.patch
+++ /dev/null
@@ -1,21 +0,0 @@
-diff --git a/pango/pango-layout.c b/pango/pango-layout.c
-index a1c47203..b8eeede0 100644
---- a/pango/pango-layout.c
-+++ b/pango/pango-layout.c
-@@ -5707,13 +5707,14 @@ pango_layout_run_get_extents_and_height (PangoLayoutRun *run,
-         }
-       else
-         {
--          double xscale, yscale;
-+          double xscale = 0, yscale = 0;
- 
-           if (!metrics)
-             metrics = pango_font_get_metrics (run->item->analysis.font,
-                                               run->item->analysis.language);
- 
--          pango_font_get_scale_factors (run->item->analysis.font, &xscale, &yscale);
-+          if (G_LIKELY(run->item->analysis.font))
-+            pango_font_get_scale_factors (run->item->analysis.font, &xscale, &yscale);
-           *height = pango_font_metrics_get_height (metrics) * MAX (xscale, yscale);
-         }
-     }
diff --git a/srcpkgs/pango/template b/srcpkgs/pango/template
index d244222b0e36..2ede2bb66459 100644
--- a/srcpkgs/pango/template
+++ b/srcpkgs/pango/template
@@ -1,7 +1,7 @@
 # Template file for 'pango'
 pkgname=pango
-version=1.50.10
-revision=2
+version=1.50.12
+revision=1
 build_style=meson
 build_helper=gir
 configure_args="-Dintrospection=$(vopt_if gir enabled disabled)"
@@ -13,8 +13,8 @@ maintainer="cinerea0 <cinerea0@protonmail.com>"
 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%.*}/${pkgname}-${version}.tar.xz"
-checksum=7e5d2f1e40854d24a9a2c4d093bafe75dcdbeccdf1de43e4437332eabed64966
+distfiles="${GNOME_SITE}/pango/${version%.*}/pango-${version}.tar.xz"
+checksum=caef96d27bbe792a6be92727c73468d832b13da57c8071ef79b9df69ee058fe3
 make_check=no  # doesn't pass its own tests
 
 # Package build options

  parent reply	other threads:[~2022-11-20  2:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 14:06 [PR PATCH] " cinerea0
2022-10-25 19:12 ` oreo639
2022-10-25 19:12 ` oreo639
2022-10-26  1:54 ` [PR PATCH] [Updated] " cinerea0
2022-11-20  2:42 ` cinerea0 [this message]
2022-11-29  1:58 ` [PR PATCH] [Merged]: pango: update to 1.50.12 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=20221120024239.fYMVahW3-SojXHZtAdvKmo9aoDHvE9G1cRtKFaQbRy4@z \
    --to=cinerea0@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).