Github messages for voidlinux
 help / color / mirror / Atom feed
From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bandwhich: update to 0.21.1
Date: Mon, 16 Oct 2023 10:16:00 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46715@inbox.vuxu.org> (raw)

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

There is a new pull request by tranzystorek-io against master on the void-packages repository

https://github.com/tranzystorek-io/void-packages bandwhich
https://github.com/void-linux/void-packages/pull/46715

bandwhich: update to 0.21.1
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


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

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

From dd1137386e270264e9f049f2583ff879659f3615 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Mon, 16 Oct 2023 10:12:20 +0200
Subject: [PATCH] bandwhich: update to 0.21.1

---
 srcpkgs/bandwhich/template | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/bandwhich/template b/srcpkgs/bandwhich/template
index 69ae550b6bef7..bb4e289b64117 100644
--- a/srcpkgs/bandwhich/template
+++ b/srcpkgs/bandwhich/template
@@ -1,16 +1,15 @@
 # Template file for 'bandwhich'
 pkgname=bandwhich
-version=0.21.0
+version=0.21.1
 revision=1
 build_style=cargo
-make_check_args="-- --skip tests::cases::ui::layout_under_50_width_under_50_height"
 short_desc="Terminal bandwidth utilization tool"
 maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
 license="MIT"
 homepage="https://github.com/imsnif/bandwhich"
 changelog="https://raw.githubusercontent.com/imsnif/bandwhich/main/CHANGELOG.md"
 distfiles="https://github.com/imsnif/bandwhich/archive/refs/tags/v${version}.tar.gz"
-checksum=f9c50c340372593bf4c54fcf2608ef37c2c56a37367b2f430c27cce3ea947828
+checksum=8ba9bf6469834ad498b9fd17f86759a16793b00a6ef44edd6e525ec40adcb0b0
 
 post_install() {
 	vlicense LICENSE.md

             reply	other threads:[~2023-10-16  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  8:16 tranzystorek-io [this message]
2023-10-17  7:16 ` [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-46715@inbox.vuxu.org \
    --to=tranzystorek-io@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).