Github messages for voidlinux
 help / color / mirror / Atom feed
From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] py3status: update to 3.36.
Date: Sun, 04 Apr 2021 20:36:06 +0200	[thread overview]
Message-ID: <20210404183606.wSA82JMAvhhw9b7CRpQZOIMKacHcxr4EkylfnI6eo4o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30004@inbox.vuxu.org>

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

There is an updated pull request by teldra against master on the void-packages repository

https://github.com/teldra/void-packages update-py3status
https://github.com/void-linux/void-packages/pull/30004

py3status: update to 3.36.
#### Have the results of the proposed changes been tested?
- [x] I generally don't use the affected packages but briefly tested this PR

#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [x] armv7l
  - [x] armv6l-musl


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

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

From 21e418554f21600b9561db4e34f7712e42e13a50 Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Sun, 4 Apr 2021 20:36:01 +0200
Subject: [PATCH] py3status: update to 3.36.

#### Have the results of the proposed changes been tested?
- [x] I generally don't use the affected packages but briefly tested this PR

#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [x] armv7l
  - [x] armv6l-musl
---
 srcpkgs/py3status/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/py3status/template b/srcpkgs/py3status/template
index dbc52049950e..b9bfc3158f65 100644
--- a/srcpkgs/py3status/template
+++ b/srcpkgs/py3status/template
@@ -1,6 +1,6 @@
 # Template file for 'py3status'
 pkgname=py3status
-version=3.35
+version=3.36
 revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -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=8069e35ff7dead4feecdd714b6c36985c4dbfd2cc133ff0ae6d190e99549f55b
+checksum=d5c26058217975014e0b5590b4a0df535b3e7969455bdf566d96d801ae46fbba
 
 do_check() {
 	python3 -m pytest

  reply	other threads:[~2021-04-04 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 18:08 [PR PATCH] " teldra
2021-04-04 18:36 ` teldra [this message]
2021-04-04 22:44 ` ericonr
2021-04-04 22:46 ` [PR PATCH] [Closed]: " ericonr
2021-04-05  0:15 ` teldra

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=20210404183606.wSA82JMAvhhw9b7CRpQZOIMKacHcxr4EkylfnI6eo4o@z \
    --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).