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!
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!
FS#70860 - [pipewire] - pipewire.conf header contains rolling version number
Attached to Project:
Arch Linux
Opened by ua4000 (ua4000) - Friday, 14 May 2021, 16:13 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 23 May 2021, 11:52 GMT
Opened by ua4000 (ua4000) - Friday, 14 May 2021, 16:13 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 23 May 2021, 11:52 GMT
|
Detailspipewire.conf contains a version number in the header.
# Daemon config file for PipeWire version "0.3.26" # This results in a pipewire.conf.pacnew on every package update, when the user has a modified conf but the rest of the config file is unchanged, Can this line or version number be removed from package conf or is this not preferred, as it comes from upstream like this ? |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Sunday, 23 May 2021, 11:52 GMT
Reason for closing: Fixed
Additional comments about closing: upstream moved default config files out of /etc (/etc still takes precedence)
Sunday, 23 May 2021, 11:52 GMT
Reason for closing: Fixed
Additional comments about closing: upstream moved default config files out of /etc (/etc still takes precedence)
pipewire-1_0.3.28-1
I was surprised to find etc/pipewire and the 4 conf files in the package gone ?
No examples conf are included now ?
Is this correct or a bug ?
I wanted to retest my bugreport, because I'm unsure now if I had a modified or a non-modified pipewire.conf