Github messages for voidlinux
 help / color / mirror / Atom feed
From: pascal-huber <pascal-huber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-s-tui: update to 1.1.4
Date: Sun, 15 Jan 2023 12:33:54 +0100	[thread overview]
Message-ID: <20230115113354.D_FbLdBi8XuU14Zukv-PWgtGD-8PYD2fGhUG407mr1o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41639@inbox.vuxu.org>

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

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

https://github.com/pascal-huber/void-packages python3-s-tui_1.1.4
https://github.com/void-linux/void-packages/pull/41639

python3-s-tui: update to 1.1.4
#### 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-glibc
- I built this PR locally for these architectures:
  - x86_64-musl
  - aarch64 (crossbuild)
  - armv7l (crossbuild)
  - 

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-s-tui_1.1.4-41639.patch --]
[-- Type: text/x-diff, Size: 1276 bytes --]

From 7a7beb12542b0f36c07b921d78899965ba7a0a26 Mon Sep 17 00:00:00 2001
From: Pascal Huber <pascal.huber@resolved.ch>
Date: Sat, 14 Jan 2023 14:26:04 +0100
Subject: [PATCH] python3-s-tui: update to 1.1.4

---
 srcpkgs/python3-s-tui/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/python3-s-tui/template b/srcpkgs/python3-s-tui/template
index 302c6b69c934..a6e58aa326a8 100644
--- a/srcpkgs/python3-s-tui/template
+++ b/srcpkgs/python3-s-tui/template
@@ -1,14 +1,14 @@
 # Template file for 'python3-s-tui'
 pkgname=python3-s-tui
-version=1.1.3
-revision=3
+version=1.1.4
+revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
-depends="python3-setuptools stress python3-urwid python3-psutil"
-checkdepends="$depends"
+depends="stress-ng python3-urwid python3-psutil"
+checkdepends="${depends} python3-pytest"
 short_desc="Terminal based CPU stress and monitoring utility"
 maintainer="shizonic <realtiaz@gmail.com>"
 license="GPL-2.0-only"
 homepage="https://amanusk.github.io/s-tui"
 distfiles="https://github.com/amanusk/s-tui/archive/v${version}.tar.gz"
-checksum=1281b3560f6e2de29f26f7b014c7a1b35121718d96de27e5fe75f6eddc12a762
+checksum=aeebcf7b04beb8526c98d675ae2b2f106fd1e00343b0c37c78b4a84c31561d0b

  parent reply	other threads:[~2023-01-15 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 13:39 [PR PATCH] " pascal-huber
2023-01-15 10:58 ` [PR REVIEW] " paper42
2023-01-15 11:28 ` pascal-huber
2023-01-15 11:29 ` [PR PATCH] [Updated] " pascal-huber
2023-01-15 11:33 ` pascal-huber [this message]
2023-01-15 11:37 ` pascal-huber
2023-01-15 11:46 ` [PR REVIEW] " pascal-huber
2023-01-15 11:55 ` [PR PATCH] [Merged]: " paper42

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=20230115113354.D_FbLdBi8XuU14Zukv-PWgtGD-8PYD2fGhUG407mr1o@z \
    --to=pascal-huber@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).