Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] aisleriot: update to 3.22.24.
Date: Sun, 17 Jul 2022 21:35:19 +0200	[thread overview]
Message-ID: <20220717193519.E7CdzfjSR-AV269BbIREWl9C6JBnojsE6Q-IfkdhWqI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37965@inbox.vuxu.org>

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

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

https://github.com/oreo639/void-packages aisleriot
https://github.com/void-linux/void-packages/pull/37965

aisleriot: update to 3.22.24.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


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

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

From f8ebfee87b9fb26c92f5fe6ce546c36ac85899b6 Mon Sep 17 00:00:00 2001
From: oreo639 <31916379+Oreo639@users.noreply.github.com>
Date: Sun, 10 Jul 2022 01:21:16 -0700
Subject: [PATCH] aisleriot: use gettext instead of intltool

Upstream droped the dependency on intltool in favor of just plain gettext.
https://gitlab.gnome.org/GNOME/aisleriot/-/issues/13
---
 srcpkgs/aisleriot/template | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/srcpkgs/aisleriot/template b/srcpkgs/aisleriot/template
index d76029e58b19..a791f3a41a8e 100644
--- a/srcpkgs/aisleriot/template
+++ b/srcpkgs/aisleriot/template
@@ -6,7 +6,7 @@ build_style=meson
 # build requires assertions to be turned on -> n_debug=false
 configure_args="-Dtheme_pysol_path=/usr/share/PySolFC/cardsets -Dtheme_pysol=true
  -Dtheme_kde=false -Db_ndebug=false"
-hostmakedepends="desktop-file-utils glib-devel guile intltool itstool pkg-config
+hostmakedepends="desktop-file-utils glib-devel guile gettext itstool pkg-config
  pysolfc-cardsets"
 makedepends="guile-devel libcanberra-devel librsvg-devel"
 depends="guile yelp"

  parent reply	other threads:[~2022-07-17 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10  8:24 [PR PATCH] " oreo639
2022-07-10  8:31 ` [PR PATCH] [Updated] " oreo639
2022-07-17 19:35 ` oreo639 [this message]
2022-07-17 19:50 ` [PR PATCH] [Closed]: aisleriot: use gettext instead of intltool ericonr
2022-07-17 19:50 ` ericonr

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=20220717193519.E7CdzfjSR-AV269BbIREWl9C6JBnojsE6Q-IfkdhWqI@z \
    --to=oreo639@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).