Arch Linux

Description:

If user has modified `/etc/pipewire/pipewire.conf` before upgrading `pipewire` to `0.3.19`, updating the config file fails while it is very easy to miss this conflict. After the upgrade, at least pipewire's pulseaudio support is broken.

It seems that 0.3.19 introduces completely different config file structure and leaving old config behind, leads in with entirely unusable pulseaudio.

While this is really a mistake from user side not to read pacman output closely enough, but it is quite easy to miss one line saying that it skips the config file upgrade and saves new version as `/etc/pipewire/pipewire.conf.pacnew`


Additional info:
* 0.3.19
* /etc/pipewire/pipewire.conf

Steps to reproduce:

- install `pipewire` and `pipewire-pulse` version 0.3.18 (also older should be fine)
- apply the following patch to enable `bluez5` support (manually or `sudo patch -d /etc/pipewire < /path/to/pipewire.patch`)
```
--- /etc/pipewire/pipewire.conf 2021-01-20 17:53:49.668756015 +0100
+++ /etc/pipewire/pipewire.conf 2021-01-20 17:53:40.135368658 +0100
@@ -80,7 +80,7 @@
# conflicts with PulseAudio. If you disable PulseAudio or don't
# load its bluetooth module, you can enable it here with -e bluez5
#
-exec /usr/bin/pipewire-media-session
+exec /usr/bin/pipewire-media-session -e bluez5
#
# You can optionally start the pulseaudio-server here as well
# but it better to start it as a systemd service.
```
- then upgrade pipewire and pipewire-puse to version 0.3.19

Then you can see a warning in the output of the upgrade:
```
warning: /etc/pipewire/pipewire.conf installed as /etc/pipewire/pipewire.conf.pacnew
```

This is quite easy to miss and will lead in broken pulseaudio.