From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pipewire: update to 1.0.6
Date: Thu, 23 May 2024 20:39:53 +0200 [thread overview]
Message-ID: <20240523183953.ED285262DC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50488@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
There is an updated pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages pipewire
https://github.com/void-linux/void-packages/pull/50488
pipewire: update to 1.0.6
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/50488.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-50488.patch --]
[-- Type: text/x-diff, Size: 1400 bytes --]
From dad0053f6d8f45970749344824e51aaa5b5071b2 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Thu, 23 May 2024 13:36:38 -0400
Subject: [PATCH] pipewire: update to 1.0.6
---
srcpkgs/pipewire/template | 4 ++--
srcpkgs/pipewire/update | 1 +
2 files changed, 3 insertions(+), 2 deletions(-)
create mode 100644 srcpkgs/pipewire/update
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 45fb07c8e99b9a..7e9f78a34045ca 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=1.0.5
+version=1.0.6
revision=1
build_style=meson
configure_args="
@@ -38,7 +38,7 @@ license="MIT"
homepage="https://pipewire.org/"
changelog="https://gitlab.freedesktop.org/pipewire/pipewire/-/raw/master/NEWS"
distfiles="https://gitlab.freedesktop.org/pipewire/pipewire/-/archive/${version}/pipewire-${version}.tar.gz"
-checksum=c5a5de26d684a1a84060ad7b6131654fb2835e03fccad85059be92f8e3ffe993
+checksum=aaaaa9825f313f0acc64bd046776da8a2f31e270f20351ecf97438d15aebce79
make_dirs="/var/lib/pipewire 0755 _pipewire _pipewire"
system_accounts="_pipewire"
diff --git a/srcpkgs/pipewire/update b/srcpkgs/pipewire/update
new file mode 100644
index 00000000000000..239ca88a92fbf8
--- /dev/null
+++ b/srcpkgs/pipewire/update
@@ -0,0 +1 @@
+ignore="1.1.*" # ignore v1.2 release candidates
next prev parent reply other threads:[~2024-05-23 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 17:37 [PR PATCH] " cinerea0
2024-05-23 18:39 ` cinerea0 [this message]
2024-05-23 19:02 ` [PR PATCH] [Merged]: " cinerea0
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=20240523183953.ED285262DC@inbox.vuxu.org \
--to=cinerea0@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).