From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] bluez: update to 5.78.
Date: Tue, 24 Sep 2024 15:17:20 +0200 [thread overview]
Message-ID: <20240924131720.5B0FE29BFB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52225@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
There is an updated pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages bluez
https://github.com/void-linux/void-packages/pull/52225
bluez: update to 5.78.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- i686
A patch file from https://github.com/void-linux/void-packages/pull/52225.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bluez-52225.patch --]
[-- Type: text/x-diff, Size: 1259 bytes --]
From 010b860653e549e45dad6bbce3a02913590b31ef Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Tue, 24 Sep 2024 15:17:01 +0200
Subject: [PATCH] bluez: update to 7.78.
---
srcpkgs/bluez/template | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/bluez/template b/srcpkgs/bluez/template
index 2f701242ee680f..51dfb5cc2309cb 100644
--- a/srcpkgs/bluez/template
+++ b/srcpkgs/bluez/template
@@ -1,6 +1,6 @@
# Template file for 'bluez'
pkgname=bluez
-version=5.76
+version=5.78
revision=1
build_style=gnu-configure
configure_args="--with-udevdir=/usr/lib/udev --disable-systemd
@@ -16,7 +16,7 @@ license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="http://www.bluez.org/"
changelog="https://git.kernel.org/pub/scm/bluetooth/bluez.git/plain/ChangeLog"
distfiles="${KERNEL_SITE}/bluetooth/bluez-${version}.tar.xz"
-checksum=55e2c645909ad82d833c42ce85ec20434e0ef0070941b1eab73facdd240bbd63
+checksum=830fed1915c5d375b8de0f5e6f45fcdea0dcc5ff5ffb3d31db6ed0f00d73c5e3
conf_files="/etc/bluetooth/main.conf"
system_groups="bluetooth"
@@ -44,6 +44,8 @@ post_install() {
vsv bluetoothd
vdoc ${FILESDIR}/README.voidlinux
+
+ rm ${DESTDIR}/etc/bluetooth/mesh-main.conf
}
libbluetooth_package() {
next prev parent reply other threads:[~2024-09-24 13:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 8:35 [PR PATCH] " dataCobra
2024-09-24 13:17 ` dataCobra [this message]
2024-09-24 14:11 ` dataCobra
2024-09-24 14:12 ` dataCobra
2024-09-24 14:13 ` [PR PATCH] [Updated] " dataCobra
2024-09-24 14:14 ` dataCobra
2024-10-22 10:58 ` [PR PATCH] [Updated] " dataCobra
2024-10-28 8:24 ` dataCobra
2024-10-28 8:31 ` dataCobra
2024-10-28 8:31 ` dataCobra
2024-10-28 8:34 ` dataCobra
2024-10-30 16:22 ` [PR REVIEW] " leahneukirchen
2024-10-30 16:25 ` dataCobra
2024-10-30 16:44 ` [PR PATCH] [Merged]: " leahneukirchen
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=20240924131720.5B0FE29BFB@inbox.vuxu.org \
--to=datacobra@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).