[PR PATCH] bluez-alsa: fix d-bus config file

[PR PATCH] bluez-alsa: fix d-bus config file

[voidlinux-github]

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

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

https://github.com/amak79/void-packages bluez-alsa
https://github.com/void-linux/void-packages/pull/15821

bluez-alsa: fix d-bus config file
bluez-alsa 2.0.0 is unable to start and produces the following error:
```
bluealsa: Couldn't acquire D-Bus name: org.bluealsa
```
This is caused by the Void provided D-Bus config file `/etc/dbus-1/system.d/bluez_alsa.conf`. It uses the incorrect D-Bus service name `org.bluez` instead of `org.bluealsa` that bluez-alsa 2.0.0 uses.

This pull request deletes the Void provided config file and instead relies on the upstream one (`/etc/dbus-1/system.d/bluealsa.conf`) that bluez-alsa 2.0.0 installs. It also fixes the upstream config file to work with the `bluez_alsa` user instead of `root`.

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

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

From 7721d029afea26171f9b674516335f091cd867c8 Mon Sep 17 00:00:00 2001
From: amak <amak.git@outlook.com>
Date: Sun, 27 Oct 2019 13:02:44 +1100
Subject: [PATCH] bluez-alsa: fix d-bus config file

---
 srcpkgs/bluez-alsa/files/bluez_alsa.conf | 7 -------
 srcpkgs/bluez-alsa/template              | 5 +++--
 2 files changed, 3 insertions(+), 9 deletions(-)
 delete mode 100644 srcpkgs/bluez-alsa/files/bluez_alsa.conf

diff --git a/srcpkgs/bluez-alsa/files/bluez_alsa.conf b/srcpkgs/bluez-alsa/files/bluez_alsa.conf
deleted file mode 100644
index b1de0810c6f..00000000000
--- a/srcpkgs/bluez-alsa/files/bluez_alsa.conf
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
- "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
-<busconfig>
-  <policy user="_bluez_alsa">
-    <allow send_destination="org.bluez"/>
-  </policy>
-</busconfig>
diff --git a/srcpkgs/bluez-alsa/template b/srcpkgs/bluez-alsa/template
index af02e7a1583..6db7d9cf858 100644
--- a/srcpkgs/bluez-alsa/template
+++ b/srcpkgs/bluez-alsa/template
@@ -1,7 +1,7 @@
 # Template file for 'bluez-alsa'
 pkgname=bluez-alsa
 version=2.0.0
-revision=1
+revision=2
 build_style=gnu-configure
 configure_args="--enable-aac --disable-hcitop --enable-debug"
 hostmakedepends="pkg-config automake libtool"
@@ -21,7 +21,8 @@ pre_configure() {
 }
 
 post_install() {
-	vinstall ${FILESDIR}/bluez_alsa.conf 644 etc/dbus-1/system.d/
+	vsed -i ${DESTDIR}/etc/dbus-1/system.d/bluealsa.conf \
+		-e 's:user="root":user="_bluez_alsa":'
 
 	vlicense LICENSE
 	vsv bluez-alsa

Re: [PR PATCH] [Merged]: bluez-alsa: fix d-bus config file

[voidlinux-github]

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

There's a merged pull request on the void-packages repository

bluez-alsa: fix d-bus config file
https://github.com/void-linux/void-packages/pull/15821

Description:
bluez-alsa 2.0.0 is unable to start and produces the following error:
```
bluealsa: Couldn't acquire D-Bus name: org.bluealsa
```
This is caused by the Void provided D-Bus config file `/etc/dbus-1/system.d/bluez_alsa.conf`. It uses the incorrect D-Bus service name `org.bluez` instead of `org.bluealsa` that bluez-alsa 2.0.0 uses.

This pull request deletes the Void provided config file and instead relies on the upstream one (`/etc/dbus-1/system.d/bluealsa.conf`) that bluez-alsa 2.0.0 installs. It also fixes the upstream config file to work with the `bluez_alsa` user instead of `root`.