From: faulesocke <faulesocke@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] inkscape: update to 1.1.2.
Date: Mon, 14 Feb 2022 19:55:24 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35623@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
There is a new pull request by faulesocke against master on the void-packages repository
https://github.com/faulesocke/void-packages inkscape
https://github.com/void-linux/void-packages/pull/35623
inkscape: update to 1.1.2.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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)
A patch file from https://github.com/void-linux/void-packages/pull/35623.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-inkscape-35623.patch --]
[-- Type: text/x-diff, Size: 1263 bytes --]
From 933ef5e1261b2d623d74c04fe2edd17c790ea441 Mon Sep 17 00:00:00 2001
From: Urs Schulz <voidpkgs@ursschulz.de>
Date: Mon, 14 Feb 2022 19:33:53 +0100
Subject: [PATCH] inkscape: update to 1.1.2.
---
srcpkgs/inkscape/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/inkscape/template b/srcpkgs/inkscape/template
index 45f48ccda0dc..49cff7effdb9 100644
--- a/srcpkgs/inkscape/template
+++ b/srcpkgs/inkscape/template
@@ -1,8 +1,8 @@
# Template file for 'inkscape'
pkgname=inkscape
-version=1.1.1
-revision=3
-wrksrc="inkscape-${version}_2021-09-20_3bf5ae0d25"
+version=1.1.2
+revision=1
+wrksrc="inkscape-${version}_2022-02-04_0a00cf5339"
build_style=cmake
# builds executables then runs checks
# some tests still fail on musl: https://gitlab.com/inkscape/inkscape/-/issues/2241
@@ -21,7 +21,7 @@ maintainer="Alex Lohr <alex.lohr@logmein.com>"
license="GPL-2.0-only, LGPL-2.1-or-later"
homepage="http://inkscape.org/"
distfiles="https://media.inkscape.org/dl/resources/file/inkscape-${version}.tar.xz"
-checksum=aeca0b9d33b5b1cfa9aa70433bdee6a8c3d020ffafc2e6f0c9a60eed7a7978af
+checksum=3ffe54a06d0b25a4cd8b6eb424536ef1ed205be13443a39cd437c8c7b89b96d1
python_version=3
if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
next reply other threads:[~2022-02-14 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 18:55 faulesocke [this message]
2022-02-14 19:32 ` notthewave
2022-06-24 2:16 ` github-actions
2022-07-09 2:13 ` [PR PATCH] [Closed]: " github-actions
-- strict thread matches above, loose matches on Subject: below --
2022-02-07 4:11 [PR PATCH] " hervyqa
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-35623@inbox.vuxu.org \
--to=faulesocke@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).