Github messages for voidlinux
 help / color / mirror / Atom feed
From: hechos <hechos@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] i3status-rust: update to 0.21.2
Date: Thu, 20 Jan 2022 23:19:25 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35149@inbox.vuxu.org> (raw)

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

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

https://github.com/hechos/void-packages master
https://github.com/void-linux/void-packages/pull/35149

i3status-rust: update to 0.21.2
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
YES
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/35149.patch is attached

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

From fd08f2482cbb126cd5de18523523b5269541c13e Mon Sep 17 00:00:00 2001
From: hechos <martin.damian.fernandez@gmail.com>
Date: Thu, 20 Jan 2022 19:18:42 -0300
Subject: [PATCH] i3status-rust: update to 0.21.2

---
 srcpkgs/i3status-rust/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/i3status-rust/template b/srcpkgs/i3status-rust/template
index d58ecb206a22..f0995d5da79f 100644
--- a/srcpkgs/i3status-rust/template
+++ b/srcpkgs/i3status-rust/template
@@ -1,6 +1,6 @@
 # Template file for 'i3status-rust'
 pkgname=i3status-rust
-version=0.20.7
+version=0.21.2
 revision=1
 build_style=cargo
 make_check_args="--bins"
@@ -12,7 +12,7 @@ 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/v${version}.tar.gz"
-checksum=995efe21ecf03e532cff9140cab1d4de9a35f91204d9e9edf0bfe3a22fedf5a0
+checksum=f246d48144fe7a43c190c596f2c4e39b275461de692b31cac16148244e73323f
 
 post_install() {
 	vmkdir usr/share/i3status-rust

             reply	other threads:[~2022-01-20 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 22:19 hechos [this message]
2022-01-20 22:21 ` abenson
2022-01-21 14:26 ` [PR PATCH] [Merged]: " ericonr
  -- strict thread matches above, loose matches on Subject: below --
2022-01-20 22:09 [PR PATCH] " hechos

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