From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-send2trash: update to 1.8.0
Date: Fri, 15 Jul 2022 13:06:27 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38085@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
There is a new pull request by Eloitor against master on the void-packages repository
https://github.com/Eloitor/void-packages python3-send2trash
https://github.com/void-linux/void-packages/pull/38085
python3-send2trash: update to 1.8.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
-
#### Local build testing
- I built this PR locally for my native architecture, x86_64
A patch file from https://github.com/void-linux/void-packages/pull/38085.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-send2trash-38085.patch --]
[-- Type: text/x-diff, Size: 1108 bytes --]
From b6165e40b8e566860017bb993ec4ab7ed107740c Mon Sep 17 00:00:00 2001
From: Eloi Torrents <eloi.torrentsj@gmail.com>
Date: Fri, 15 Jul 2022 10:56:35 +0000
Subject: [PATCH] python3-send2trash: update to 1.8.0
---
srcpkgs/python3-send2trash/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-send2trash/template b/srcpkgs/python3-send2trash/template
index 8768c2c98264..e0d8dbcef85f 100644
--- a/srcpkgs/python3-send2trash/template
+++ b/srcpkgs/python3-send2trash/template
@@ -1,6 +1,6 @@
# Template file for 'python3-send2trash'
pkgname=python3-send2trash
-version=1.5.0
+version=1.8.0
revision=5
wrksrc="send2trash-${version}"
build_style=python3-module
@@ -11,7 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-3-Clause"
homepage="https://github.com/hsoft/send2trash"
distfiles="https://github.com/hsoft/send2trash/archive/${version}.tar.gz"
-checksum=7cebc0ffc8b6d6e553bce9c6bb915614610ba2dec17c2f0643b1b97251da2a41
+checksum=937b038abd9f1e7b8c5d7a116be5dc4663beb71df74dcccffe56cacf992c7a9c
post_install() {
vlicense LICENSE
next reply other threads:[~2022-07-15 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 11:06 Eloitor [this message]
2022-07-15 11:07 ` [PR PATCH] [Updated] " Eloitor
2022-07-15 11:11 ` Eloitor
2022-07-15 11:19 ` ishaanbhimwal
2022-07-15 11:37 ` [PR PATCH] [Updated] " Eloitor
2022-07-15 11:42 ` Eloitor
2022-07-15 11:44 ` [PR PATCH] [Updated] " Eloitor
2022-07-15 15:55 ` classabbyamp
2022-07-15 16:14 ` [PR PATCH] [Updated] " Eloitor
2022-07-15 16:28 ` [PR PATCH] [Merged]: " classabbyamp
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-38085@inbox.vuxu.org \
--to=eloitor@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).