From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] py3status: update to 3.31.
Date: Wed, 25 Nov 2020 10:52:44 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26694@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
There is a new pull request by teldra against master on the void-packages repository
https://github.com/teldra/void-packages py3status-update
https://github.com/void-linux/void-packages/pull/26694
py3status: update to 3.31.
A patch file from https://github.com/void-linux/void-packages/pull/26694.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-py3status-update-26694.patch --]
[-- Type: text/x-diff, Size: 1049 bytes --]
From ebaca3bf591a7638e8facef615f767dd3d6318e4 Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Mon, 23 Nov 2020 07:58:50 +0100
Subject: [PATCH] py3status: update to 3.31.
---
srcpkgs/py3status/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/py3status/template b/srcpkgs/py3status/template
index 9db3993929e..a00c2180007 100644
--- a/srcpkgs/py3status/template
+++ b/srcpkgs/py3status/template
@@ -1,7 +1,7 @@
# Template file for 'py3status'
pkgname=py3status
-version=3.30
-revision=2
+version=3.31
+revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3-setuptools python3-pyudev"
@@ -11,7 +11,7 @@ maintainer="teldra <teldra@rotce.de>"
license="BSD-3-Clause"
homepage="https://github.com/ultrabug/py3status"
distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=908585b3994f84890007873d8d9d12a45a3b66b0120b11766d6ee973b63008bb
+checksum=c69bca855559f31fec4a257e76bc3e3cd2d4737f37785b96fa5509b6ee208b3a
do_check() {
python3 -m pytest
reply other threads:[~2020-11-25 9:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-26694@inbox.vuxu.org \
--to=teldra@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).