Github messages for voidlinux
 help / color / mirror / Atom feed
From: cultab <cultab@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] piper: update to 0.7.
Date: Mon, 03 Oct 2022 15:50:39 +0200	[thread overview]
Message-ID: <20221003135039.F-DIBOwO8ixxzDs5P1AMI7Z69z7V9_T0EArfWau-qKs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39663@inbox.vuxu.org>

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

There is an updated pull request by cultab against master on the void-packages repository

https://github.com/cultab/void-packages piper
https://github.com/void-linux/void-packages/pull/39663

piper: update to 0.7.
#### Testing the changes
- I tested the changes in this PR: **briefly**, with a compatible gaming mouse

#### Local build testing
- I built this PR locally for my native architecture, (x86-64-glibc)


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

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

From 9be29966ae8f18e80beee156221607491c803eb2 Mon Sep 17 00:00:00 2001
From: cultab <rroarck@gmail.com>
Date: Mon, 3 Oct 2022 15:33:11 +0300
Subject: [PATCH 1/2] piper: update to 0.7.

---
 srcpkgs/piper/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/piper/template b/srcpkgs/piper/template
index 21333273a406..5299d4281ad8 100644
--- a/srcpkgs/piper/template
+++ b/srcpkgs/piper/template
@@ -1,19 +1,19 @@
 # Template file for 'piper'
 pkgname=piper
-version=0.6
-revision=3
+version=0.7
+revision=1
 build_style=meson
 hostmakedepends="gettext libratbag pkg-config glib-devel python3-lxml
  python3-evdev python3-cairo python3-gobject"
 makedepends="python3-devel python3-gobject-devel"
-depends="libratbag gtk+3 python3-lxml python3-evdev python3-cairo python3-gobject"
+depends="libratbag gtk+3 python3-lxml python3-evdev python3-cairo python3-gobject AppStream"
 checkdepends="flake8"
 short_desc="GTK application to configure gaming mice"
 maintainer="bra1nwave <bra1nwave@protonmail.com>"
 license="GPL-2.0-or-later"
 homepage="https://github.com/libratbag/piper"
 distfiles="https://github.com/libratbag/piper/archive/${version}.tar.gz"
-checksum=aa2fb9b63cd926067bdf2842013169e279fe2a159e8575f392fc1f042cdec001
+checksum=65e5058e7d722c463e810de6d9ae79ad7ebf8979f099fec5bcd26c5098a89ded
 
 if [ -z "$XBPS_CHECK_PKGS" ]; then
 	configure_args="-Dtests=false"

From 0f581dc813f1ede0f7447dc7788e436e71d934c5 Mon Sep 17 00:00:00 2001
From: cultab <rroarck@gmail.com>
Date: Mon, 3 Oct 2022 16:02:03 +0300
Subject: [PATCH 2/2] libratbag: update to 0.16.

---
 srcpkgs/libratbag/template | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/libratbag/template b/srcpkgs/libratbag/template
index 370d670157f6..b4fe534bdf74 100644
--- a/srcpkgs/libratbag/template
+++ b/srcpkgs/libratbag/template
@@ -1,6 +1,6 @@
 # Template file for 'libratbag'
 pkgname=libratbag
-version=0.15
+version=0.16
 revision=1
 build_style=meson
 configure_args="-Dtests=false -Dsystemd-unit-dir=''
@@ -9,13 +9,15 @@ hostmakedepends="pkg-config git swig"
 makedepends="elogind-devel eudev-libudev-devel libglib-devel libevdev-devel
  python3-devel json-glib-devel libunistring-devel"
 depends="dbus python3-evdev python3-gobject"
-checkdepends="python3-gobject python3-evdev"
+checkdepends="dbus python3-gobject python3-evdev"
 short_desc="DBus daemon to configure gaming mice"
 maintainer="bra1nwave <bra1nwave@protonmail.com>"
 license="MIT"
 homepage="https://github.com/libratbag/libratbag"
 distfiles="https://github.com/libratbag/libratbag/archive/v${version}.tar.gz"
-checksum=9e6ad8d54daef8cc0f44784bdde9bf5a3879d8a66d11e0b990b87266f81f7329
+checksum=c70b6a259693216e6a57ec3087496e8d6df01d4425b7a06592872b7b123e5fcc
+make_check="ci-skip" # needs system dbus
+make_check_pre="dbus-run-session"
 
 post_install() {
 	vsv ratbagd

  parent reply	other threads:[~2022-10-03 13:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 12:35 [PR PATCH] " cultab
2022-10-03 12:36 ` classabbyamp
2022-10-03 12:37 ` classabbyamp
2022-10-03 12:37 ` classabbyamp
2022-10-03 13:06 ` [PR PATCH] [Updated] " cultab
2022-10-03 13:06 ` cultab
2022-10-03 13:14 ` classabbyamp
2022-10-03 13:15 ` classabbyamp
2022-10-03 13:15 ` classabbyamp
2022-10-03 13:18 ` cultab
2022-10-03 13:18 ` cultab
2022-10-03 13:19 ` [PR PATCH] [Updated] " cultab
2022-10-03 13:22 ` cultab
2022-10-03 13:22 ` cultab
2022-10-03 13:31 ` [PR PATCH] [Updated] " cultab
2022-10-03 13:32 ` cultab
2022-10-03 13:35 ` classabbyamp
2022-10-03 13:36 ` [PR PATCH] [Updated] " cultab
2022-10-03 13:50 ` cultab [this message]
2022-10-03 13:51 ` cultab
2022-10-03 13:52 ` classabbyamp
2022-10-03 13:55 ` [PR PATCH] [Updated] " cultab
2022-10-03 13:58 ` cultab
2022-10-03 14:03 ` [PR REVIEW] " classabbyamp
2022-10-03 14:07 ` [PR PATCH] [Updated] " cultab
2022-10-03 14:12 ` [PR PATCH] [Merged]: " classabbyamp
2022-10-03 14:13 ` [PR REVIEW] " cultab
2022-10-03 14:16 ` classabbyamp
2022-10-03 14:19 ` cultab

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=20221003135039.F-DIBOwO8ixxzDs5P1AMI7Z69z7V9_T0EArfWau-qKs@z \
    --to=cultab@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).