From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] helvum: update to 0.4.0.
Date: Sun, 02 Apr 2023 10:58:50 +0200 [thread overview]
Message-ID: <20230402085850.9pPGN4ik5henMcw10QzeSjLzDjdPFJaK9SmjTPWRmAo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43173@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
There is an updated pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages update/helvum-0.4.0
https://github.com/void-linux/void-packages/pull/43173
helvum: update to 0.4.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/43173.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/helvum-0.4.0-43173.patch --]
[-- Type: text/x-diff, Size: 2029 bytes --]
From 36dc2502e8c265b1c1aac5ae6a9beae3b4e6794a Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Fri, 17 Feb 2023 12:40:52 -0500
Subject: [PATCH] helvum: update to 0.4.0, orphan.
0x5c has agreed to adopt it
---
srcpkgs/helvum/patches/i686-pipewire.patch | 11 -----------
srcpkgs/helvum/template | 8 ++++----
2 files changed, 4 insertions(+), 15 deletions(-)
delete mode 100644 srcpkgs/helvum/patches/i686-pipewire.patch
diff --git a/srcpkgs/helvum/patches/i686-pipewire.patch b/srcpkgs/helvum/patches/i686-pipewire.patch
deleted file mode 100644
index bd08b0e217b3..000000000000
--- a/srcpkgs/helvum/patches/i686-pipewire.patch
+++ /dev/null
@@ -1,11 +0,0 @@
---- a/Cargo.toml
-+++ b/Cargo.toml
-@@ -14,7 +14,7 @@
- # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
-
- [dependencies]
--pipewire = "0.4"
-+pipewire = "0.5"
- gtk = { version = "0.4.1", package = "gtk4" }
- glib = { version = "0.15.1", features = ["log"] }
-
diff --git a/srcpkgs/helvum/template b/srcpkgs/helvum/template
index 6c5e27bfefc1..1f3c89a66717 100644
--- a/srcpkgs/helvum/template
+++ b/srcpkgs/helvum/template
@@ -1,17 +1,17 @@
# Template file for 'helvum'
pkgname=helvum
-version=0.3.4
-revision=2
+version=0.4.0
+revision=1
build_style=cargo
hostmakedepends="pkg-config clang libclang"
makedepends="gtk4-devel pipewire-devel glib-devel"
depends="pipewire"
short_desc="GTK patchbay for pipewire"
-maintainer="classabbyamp <void@placeviolette.net>"
+maintainer="0x5c <dev@0x5c.io>"
license="GPL-3.0-only"
homepage="https://gitlab.freedesktop.org/pipewire/helvum"
distfiles="https://gitlab.freedesktop.org/pipewire/helvum/-/archive/${version}/helvum-${version}.tar.gz"
-checksum="e19054f3bcd1ba234c451134fe7f4c6afee35f108c122642c1d502fc16785c02"
+checksum=e93afa788d3e50bae489db888ecf0d79e5735b8f4f8b29fe4174540b0872b622
post_install() {
# Normally, meson would do this, but it's simpler to use the cargo build style and do this manually
next prev parent reply other threads:[~2023-04-02 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 8:43 [PR PATCH] " classabbyamp
2023-04-02 8:58 ` classabbyamp [this message]
2023-04-02 9:11 ` [PR PATCH] [Merged]: helvum: update to 0.4.0, orphan classabbyamp
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=20230402085850.9pPGN4ik5henMcw10QzeSjLzDjdPFJaK9SmjTPWRmAo@z \
--to=classabbyamp@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).