From: kartikynwa <kartikynwa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] i3status-rust: update to 0.31.8.
Date: Sat, 08 Jul 2023 07:07:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44917@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
There is a new pull request by kartikynwa against master on the void-packages repository
https://github.com/kartikynwa/void-packages update-i3status-rust
https://github.com/void-linux/void-packages/pull/44917
i3status-rust: update to 0.31.8.
<!-- 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, (x86_64-glibc)
#### Notes
- The updates include breaking changes. Users of v0.22.0 who inadvertently upgrade will see errors and will have to update their configs according to [the changelog](https://github.com/greshake/i3status-rust/blob/master/NEWS.md).
- I am not sure about the pandoc requirement to build the manpage. I looked at existing templates for reference. Some do pandoc-based manpage generation only on certain architectures and usually these packages are marked as `crossbuild=no`. Some pointers on this would be appreciated.
A patch file from https://github.com/void-linux/void-packages/pull/44917.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-i3status-rust-44917.patch --]
[-- Type: text/x-diff, Size: 1469 bytes --]
From 0ec5afcc9ca67d11a96eafe5726d95b85fc1d610 Mon Sep 17 00:00:00 2001
From: Kartik Singh <kartik.ynwa@gmail.com>
Date: Sat, 8 Jul 2023 10:32:15 +0530
Subject: [PATCH] i3status-rust: update to 0.31.8.
---
srcpkgs/i3status-rust/template | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/i3status-rust/template b/srcpkgs/i3status-rust/template
index 788270ca956f..7e4fe8fd6fb1 100644
--- a/srcpkgs/i3status-rust/template
+++ b/srcpkgs/i3status-rust/template
@@ -1,10 +1,10 @@
# Template file for 'i3status-rust'
pkgname=i3status-rust
-version=0.22.0
-revision=2
+version=0.31.8
+revision=1
build_style=cargo
make_check_args="--bins"
-hostmakedepends="pkg-config"
+hostmakedepends="pkg-config pandoc"
makedepends="dbus-devel pulseaudio-devel openssl-devel libsensors-devel"
short_desc="Replacement for i3status, written in Rust"
maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
@@ -12,7 +12,11 @@ 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=31d391a08d45ab877a36479a6f453768303a836efae6ffcf555013b2f12fce2f
+
+post_build() {
+ cargo xtask generate-manpage
+}
post_install() {
vmkdir usr/share/i3status-rust
next reply other threads:[~2023-07-08 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 5:07 kartikynwa [this message]
2023-07-26 6:54 ` [PR PATCH] [Updated] " kartikynwa
2023-07-26 7:24 ` kartikynwa
2023-07-26 7:51 ` kartikynwa
2023-07-26 7:57 ` kartikynwa
2023-07-26 8:25 ` [PR PATCH] [Closed]: " kartikynwa
2023-07-26 8:26 ` kartikynwa
-- strict thread matches above, loose matches on Subject: below --
2023-07-07 7:56 [PR PATCH] " pablomancera
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-44917@inbox.vuxu.org \
--to=kartikynwa@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).