From: unknowncartridge <unknowncartridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gimp: update to 2.10.34
Date: Sat, 06 May 2023 21:53:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43774@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
There is a new pull request by unknowncartridge against master on the void-packages repository
https://github.com/unknowncartridge/void-packages gimp
https://github.com/void-linux/void-packages/pull/43774
gimp: update to 2.10.34
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures:
- x86_64-musl
- armv6l
- aarch64
- aarch64-musl
A patch file from https://github.com/void-linux/void-packages/pull/43774.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gimp-43774.patch --]
[-- Type: text/x-diff, Size: 1541 bytes --]
From cef112f31c71d767f9021586ddde88f792615561 Mon Sep 17 00:00:00 2001
From: unknowncartridge <violetnetwork@disroot.org>
Date: Sat, 6 May 2023 15:57:09 +0300
Subject: [PATCH] gimp: update to 2.10.34
---
srcpkgs/gimp/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/gimp/template b/srcpkgs/gimp/template
index 8e68f2403d8f..d47a0f208542 100644
--- a/srcpkgs/gimp/template
+++ b/srcpkgs/gimp/template
@@ -1,7 +1,7 @@
# Template file for 'gimp'
pkgname=gimp
-version=2.10.32
-revision=4
+version=2.10.34
+revision=1
build_style=gnu-configure
configure_args="--disable-check-update --datadir=/usr/share"
hostmakedepends="automake gegl gettext-devel glib-devel gtk+-devel intltool
@@ -19,7 +19,7 @@ maintainer="fosslinux <fosslinux@aussies.space>"
license="GPL-3.0-only"
homepage="https://www.gimp.org"
distfiles="https://download.gimp.org/pub/gimp/v${version%.*}/gimp-${version}.tar.bz2"
-checksum=3f15c70554af5dcc1b46e6dc68f3d8f0a6cc9fe56b6d78ac08c0fd859ab89a25
+checksum=84004642d351b398a4293cd7fd3592044a944f05bb52850ee6068f247c657aa3
python_version=2
lib32disabled=yes
no_generic_pkgconfig_link=yes
@@ -27,7 +27,7 @@ no_generic_pkgconfig_link=yes
pre_configure() {
NOCONFIGURE=1 autoreconf -fi
if [ "$CROSS_BUILD" ]; then
- vsed -i 's:^py_prefix=`:py_prefix='"$XBPS_CROSS_BASE"'`:' configure
+ vsed -i 's:^py_prefix=$(:py_prefix='"$XBPS_CROSS_BASE"'):' configure
fi
# don't allow configure to set DATADIRNAME=lib
vsed -i 's/DATADIRNAME=lib/DATADIRNAME=share/' configure
next reply other threads:[~2023-05-06 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 19:53 unknowncartridge [this message]
2023-05-06 20:12 ` [PR REVIEW] " classabbyamp
2023-05-07 1:02 ` [PR PATCH] [Updated] " unknowncartridge
2023-05-08 5:08 ` biopsin
2023-06-14 17:38 ` [PR PATCH] [Merged]: " Duncaen
-- strict thread matches above, loose matches on Subject: below --
2023-03-03 12:13 [PR PATCH] " biopsin
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-43774@inbox.vuxu.org \
--to=unknowncartridge@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).