Github messages for voidlinux
 help / color / mirror / Atom feed
From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] inkscape: fix update-check
Date: Wed, 05 Jul 2023 13:27:22 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44859@inbox.vuxu.org> (raw)

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

There is a new pull request by Bnyro against master on the void-packages repository

https://github.com/Bnyro/void-packages inkscape
https://github.com/void-linux/void-packages/pull/44859

inkscape: fix update-check
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

The old Regex also detects development releases (1.3), although it's not an official release yet. (Current should be 1.2.2).

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

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

From 0b3984bf3068b33285af4ec7784a298ba5c65911 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Wed, 5 Jul 2023 13:26:39 +0200
Subject: [PATCH] inkscape: fix update-check

---
 srcpkgs/inkscape/update | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/srcpkgs/inkscape/update b/srcpkgs/inkscape/update
index 2a649bb0bbef..0d1faee432dc 100644
--- a/srcpkgs/inkscape/update
+++ b/srcpkgs/inkscape/update
@@ -1,2 +1,2 @@
 site="https://inkscape.org/release/"
-pattern='release/inkscape-\K[0-9.]+(?=/)'
+pattern='Inkscape \K[0-9.]+'

             reply	other threads:[~2023-07-05 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 11:27 Bnyro [this message]
2023-07-05 11:28 ` atk
2023-07-05 12:50 ` mhmdanas
2023-07-05 12:51 ` Bnyro
2023-07-05 12:57 ` mhmdanas
2023-07-08 18:25 ` [PR PATCH] [Merged]: " Duncaen

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-44859@inbox.vuxu.org \
    --to=bnyro@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).