From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] urlscan: update to 1.0.0.
Date: Thu, 06 Jul 2023 19:47:44 +0200 [thread overview]
Message-ID: <20230706174744.hiJvq42oCbwiSmjp0vnPJ86iPydqLtOOGxCZAkc0v1w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44883@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages urlscan-1.0.0
https://github.com/void-linux/void-packages/pull/44883
urlscan: update to 1.0.0.
<!-- 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
Been updating this package the last 2 releases, so if @Crestwave doesn't mind I can maintain the package.
A patch file from https://github.com/void-linux/void-packages/pull/44883.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-urlscan-1.0.0-44883.patch --]
[-- Type: text/x-diff, Size: 1373 bytes --]
From 5367293c236c5dd772a0ccb1000da491f9a49f9f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Thu, 6 Jul 2023 18:40:01 +0100
Subject: [PATCH] urlscan: update to 1.0.0.
---
srcpkgs/urlscan/template | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/urlscan/template b/srcpkgs/urlscan/template
index e609b70f065c..e72c1cc10842 100644
--- a/srcpkgs/urlscan/template
+++ b/srcpkgs/urlscan/template
@@ -1,14 +1,17 @@
# Template file for 'urlscan'
pkgname=urlscan
-version=0.9.10
-revision=2
-build_style=python3-module
-hostmakedepends="python3-setuptools"
+version=1.0.0
+revision=1
+build_style=python3-pep517
+hostmakedepends="hatchling hatch-vcs python3-installer python3-wheel"
depends="python3-urwid"
-checkdepends="python3-urwid"
short_desc="View/select the URLs in an email message or file"
-maintainer="Crestwave <crest.wave@yahoo.com>"
+maintainer="André Cerqueira <acerqueira021@gmail.com>"
license="GPL-2.0-or-later"
homepage="https://github.com/firecat53/urlscan"
distfiles="https://github.com/firecat53/urlscan/archive/${version}.tar.gz"
-checksum=0fbaf7f820fc6ff20c6f1a429c98cb240f1da7eabceed5e3d88740558e81cd2d
+checksum=b12da2c3ee45ae21c80eed2fc40866b3b0b82a39e70ce1ad458b65af7334728a
+
+pre_build(){
+ export SETUPTOOLS_SCM_PRETEND_VERSION="${version}"
+}
next prev parent reply other threads:[~2023-07-06 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 17:45 [PR PATCH] " motorto
2023-07-06 17:46 ` [PR PATCH] [Updated] " motorto
2023-07-06 17:47 ` motorto [this message]
2023-07-06 17:49 ` motorto
2023-07-06 18:17 ` [PR REVIEW] " icp1994
2023-07-06 18:17 ` icp1994
2023-07-06 22:55 ` motorto
2023-07-06 22:55 ` [PR PATCH] [Updated] " motorto
2023-07-08 18:09 ` [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=20230706174744.hiJvq42oCbwiSmjp0vnPJ86iPydqLtOOGxCZAkc0v1w@z \
--to=motorto@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).