Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] waypipe: update to 0.7.0.
Date: Thu, 09 Jul 2020 09:25:21 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23490@inbox.vuxu.org> (raw)

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

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

https://github.com/ericonr/void-packages waypipe
https://github.com/void-linux/void-packages/pull/23490

waypipe: update to 0.7.0.
This is a breaking change in that it needs to be updated on both sides of the connection. Should I create an install msg to warn about this? It shouldn't be necessary, since if you try to launch it without updating one of the sides it errors out. Tested between two x86_64 musl devices.

A patch file from https://github.com/void-linux/void-packages/pull/23490.patch is attached

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

From f11bf7b0672ca816a4e01150ec8c36104a0f9966 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Thu, 9 Jul 2020 04:23:15 -0300
Subject: [PATCH] waypipe: update to 0.7.0.

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

diff --git a/srcpkgs/waypipe/template b/srcpkgs/waypipe/template
index 9b07a2530cc..229137b8e36 100644
--- a/srcpkgs/waypipe/template
+++ b/srcpkgs/waypipe/template
@@ -1,6 +1,6 @@
 # Template file for 'waypipe'
 pkgname=waypipe
-version=0.6.1
+version=0.7.0
 revision=1
 wrksrc="${pkgname}-v${version}"
 build_style=meson
@@ -16,7 +16,7 @@ maintainer="Érico Nogueira <ericonr@disroot.org>"
 license="MIT"
 homepage="https://gitlab.freedesktop.org/mstoeckl/waypipe"
 distfiles="https://gitlab.freedesktop.org/mstoeckl/waypipe/-/archive/v${version}/${pkgname}-v${version}.tar.gz"
-checksum=95114f0f4e52cbd8d054c3119265d9006c9f39550961dea58f72b984075d7bce
+checksum=ce14508af422acc212b4eee6faae4c84e082abd8b3b85655bec36e942200b9fa
 
 post_install() {
 	vlicense COPYING LICENSE

             reply	other threads:[~2020-07-09  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  7:25 ericonr [this message]
2020-07-09 13:42 ` sgn
2020-07-09 15:48 ` [PR PATCH] [Updated] " ericonr
2020-07-20  4:24 ` [PR PATCH] [Merged]: " abenson

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