Github messages for voidlinux
 help / color / mirror / Atom feed
From: klardotsh <klardotsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] i3status-rust: Update to 0.32.3.
Date: Fri, 29 Dec 2023 09:22:28 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47968@inbox.vuxu.org> (raw)

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

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

https://github.com/klardotsh/void-packages klardotsh/update-i3status-rust
https://github.com/void-linux/void-packages/pull/47968

i3status-rust: Update to 0.32.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES** (I just spent something like an hour updating my TOML config to the new schema since everything was broken... believe me, I'd know if this package was broken after that slog 😃)

<!--
#### 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/47968.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-klardotsh/update-i3status-rust-47968.patch --]
[-- Type: text/x-diff, Size: 1308 bytes --]

From 990e2bab711ceb297f4f4ffd08f7e8082f09bd35 Mon Sep 17 00:00:00 2001
From: Josh Klar <josh@klar.sh>
Date: Fri, 29 Dec 2023 00:20:53 -0800
Subject: [PATCH] i3status-rust: Update to 0.32.3.

---
 srcpkgs/i3status-rust/template | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/i3status-rust/template b/srcpkgs/i3status-rust/template
index 5e51b37ac809d..3c78a13013b1a 100644
--- a/srcpkgs/i3status-rust/template
+++ b/srcpkgs/i3status-rust/template
@@ -1,7 +1,7 @@
 # Template file for 'i3status-rust'
 pkgname=i3status-rust
-version=0.22.0
-revision=4
+version=0.32.3
+revision=1
 build_style=cargo
 make_check_args="--bins"
 hostmakedepends="pkg-config"
@@ -12,12 +12,10 @@ license="GPL-3.0-only"
 homepage="https://github.com/greshake/i3status-rust"
 changelog="https://raw.githubusercontent.com/greshake/i3status-rust/master/NEWS.md"
 distfiles="https://github.com/greshake/i3status-rust/archive/refs/tags/v${version}.tar.gz"
-checksum=cd28a90ccb2f9faaaef1e528619f1018981609d77f409abe4877350d810d3324
+checksum=6a2c37d0e424d666f297d7ec36279b54a522acf5bf77af883be1991513e4da61
 
 post_install() {
 	vmkdir usr/share/i3status-rust
 	vcopy ${wrksrc}/files/icons usr/share/i3status-rust/
 	vcopy ${wrksrc}/files/themes usr/share/i3status-rust/
-
-	vman man/i3status-rs.1
 }

             reply	other threads:[~2023-12-29  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29  8:22 klardotsh [this message]
2024-01-07  6:23 ` icp1994
2024-01-09 19:36 ` [PR PATCH] [Closed]: " klardotsh
  -- strict thread matches above, loose matches on Subject: below --
2023-12-22  6:03 [PR PATCH] i3status-rust: update " desertsagebrush

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-47968@inbox.vuxu.org \
    --to=klardotsh@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).