Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75584 - [bluez] Don't install /etc/bluetooth/main.conf

Attached to Project: Arch Linux
Opened by Dennis Kadioglu (dkadioglu) - Friday, 12 August 2022, 09:01 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 12 August 2022, 13:48 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
As far as I can see, the config file /etc/bluetooth/main.conf includes only commented default settings. According to https://www.spinics.net/lists/linux-bluetooth/msg97284.html, the config file is not installed by default by upstream and should only be installed by packages, if there is a reason for it. I kindly want to ask for the reason, that the config file is installed by the package. If there is no reason, I would like to propose to not install it anymore.
Reasoning for my proposal: As I have to modify a specific setting in the config file, whenever bluez is updated, I have to merge the config files (main.conf and main.conf.pacnew). Absolutely doable but, it would be great if this could be omitted.
Thank you very much for packaging bluez!

Additional info:
* package version(s) 5.65

Steps to reproduce:
Change the config file /etc/bluetooth/main.conf and update bluez -> the new file /etc/bluetooth/main.conf.pacnew has to be merged with the existing /etc/bluetooth/main.conf.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Friday, 12 August 2022, 13:48 GMT
Reason for closing:  Not a bug
Comment by Andreas Radke (AndyRTR) - Friday, 12 August 2022, 13:48 GMT
backup=('etc/bluetooth/main.conf')

That config file is under backup control for a good reason. Any update would overwrite your changes without this.

And we ship the upstream default config file to show possible options. That's how we deal with all packages.

Loading...