Github messages for voidlinux
 help / color / mirror / Atom feed
From: brihadeesh <brihadeesh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] river: update to 0.1.3.
Date: Tue, 17 May 2022 15:37:47 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37164@inbox.vuxu.org> (raw)

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

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

https://github.com/brihadeesh/void-packages river_0.1.3
https://github.com/void-linux/void-packages/pull/37164

river: update to 0.1.3.
river: update to 0.1.3

<!-- Uncomment relevant sections and delete options which are not applicable -->

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


#### Update
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**


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

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

From 77276c115b7941a4afdc5aa656d89b16e9fd7cc2 Mon Sep 17 00:00:00 2001
From: Brihadeesh S <brihadeesh.santharam@gmail.com>
Date: Tue, 17 May 2022 19:05:23 +0530
Subject: [PATCH] river: update to 0.1.3.

river: update to 0.1.3
---
 srcpkgs/river/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/river/template b/srcpkgs/river/template
index 9cf3abe4b85b..ae09ae54b34f 100644
--- a/srcpkgs/river/template
+++ b/srcpkgs/river/template
@@ -1,6 +1,6 @@
 # Template file for 'river'
 pkgname=river
-version=0.1.1
+version=0.1.3
 revision=1
 build_style=zig-build
 configure_args="$(vopt_if xwayland -Dxwayland)"
@@ -12,7 +12,7 @@ maintainer="Isaac Freund <mail@isaacfreund.com>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/riverwm/river"
 distfiles="${homepage}/releases/download/v${version}/river-${version}.tar.gz"
-checksum=2a0bcd4670ed9ebd39c279f2bf10803fc65c9f3ee2307ce40728df23ce914d18
+checksum=f63444c300ab554ef3ca0d904a6b124a832c8397d474ef067bdde911c981c79f
 
 build_options="xwayland"
 build_options_default="xwayland"

             reply	other threads:[~2022-05-17 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 13:37 brihadeesh [this message]
2022-05-17 13:42 ` brihadeesh
2022-05-17 13:42 ` [PR PATCH] [Closed]: " brihadeesh
2022-05-17 13:44 ` brihadeesh
2022-05-17 14:15 ` ifreund
2022-05-19  5:33 ` brihadeesh
2022-05-19  5:33 ` [PR PATCH] [Closed]: " brihadeesh

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