From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-SecretStorage: update to 3.3.3
Date: Wed, 28 Jun 2023 00:27:20 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44669@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
There is a new pull request by chrysos349 against master on the void-packages repository
https://github.com/chrysos349/void-packages python3-SecretStorage
https://github.com/void-linux/void-packages/pull/44669
python3-SecretStorage: update to 3.3.3
#### Testing the changes
- I tested the changes in this PR: **NO**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-LIBC)
A patch file from https://github.com/void-linux/void-packages/pull/44669.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-SecretStorage-44669.patch --]
[-- Type: text/x-diff, Size: 1258 bytes --]
From 0d25b797b88783691c73006057d0390299857580 Mon Sep 17 00:00:00 2001
From: chrysos349 <chrysostom349@gmail.com>
Date: Wed, 28 Jun 2023 01:26:26 +0300
Subject: [PATCH] python3-SecretStorage: update to 3.3.3
---
srcpkgs/python3-SecretStorage/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-SecretStorage/template b/srcpkgs/python3-SecretStorage/template
index ad42d8b1afa7..b5d88e6889d5 100644
--- a/srcpkgs/python3-SecretStorage/template
+++ b/srcpkgs/python3-SecretStorage/template
@@ -1,7 +1,7 @@
# Template file for 'python3-SecretStorage'
pkgname=python3-SecretStorage
-version=3.3.1
-revision=3
+version=3.3.3
+revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3-jeepney python3-cryptography"
@@ -11,8 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-3-Clause"
homepage="https://github.com/mitya57/secretstorage"
distfiles="${PYPI_SITE}/S/SecretStorage/SecretStorage-${version}.tar.gz"
-checksum=fd666c51a6bf200643495a04abb261f83229dcb6fd8472ec393df7ffc8b6f195
-make_check=ci-skip
+checksum=2403533ef369eca6d2ba81718576c5e0f564d5cca1b58f73a8b23e7d4eeebd77
do_check() {
dbus-run-session -- python3 -m unittest discover -s tests
next reply other threads:[~2023-06-27 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 22:27 chrysos349 [this message]
2023-06-29 9:21 ` [PR PATCH] [Closed]: " ahesford
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-44669@inbox.vuxu.org \
--to=chrysos349@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).