From: kartikynwa <kartikynwa@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: i3status-rust: update to 0.31.8.
Date: Wed, 26 Jul 2023 10:25:50 +0200 [thread overview]
Message-ID: <20230726082550.lqI39S0htZOd4wszcs_vYjJnxhIW01Z8PvSKwJbWGCM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44917@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
There's a closed pull request on the void-packages repository
i3status-rust: update to 0.31.8.
https://github.com/void-linux/void-packages/pull/44917
Description:
<!-- 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.
next prev parent reply other threads:[~2023-07-26 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 5:07 [PR PATCH] " kartikynwa
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 ` kartikynwa [this message]
2023-07-26 8:26 ` kartikynwa
-- strict thread matches above, loose matches on Subject: below --
2023-07-07 7:56 [PR PATCH] " pablomancera
2023-09-16 5:31 ` [PR PATCH] [Closed]: " 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=20230726082550.lqI39S0htZOd4wszcs_vYjJnxhIW01Z8PvSKwJbWGCM@z \
--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).