Hide Forgot
Description of problem: The latest version of pipewire installs configuration files in /usr/share instead of /etc/pipewire. This was announced on bodhi, so this is intentional, but is this correct? The guidelines say that config files should go to sysconfdir, not datadir. (The man page for pipewire.conf also still says that the configuration directory is in /etc/pipewire.) Additionally, users (like me), now have a /etc/pipewire that is no longer owned by any package and so will never be cleaned up. Version-Release number of selected component (if applicable): pipewire-0.3.28-1.fc34.x86_64 How reproducible: Always Steps to Reproduce: 1. Update a F34/rawhide system 2. 3. Actual results: Configuration files are installed in /usr/share/pipewire instead of /etc/pipewire Expected results: Configuration files should be installed in /etc/pipewire. Additional info:
It is intentional and in line with other packages (dbus) that now can run without any configuration in /etc or /home. The idea is that wiping /etc or /home brings the configuration back to factory settings. If a modification needs to be made, the backup config file (in /usr/share) should be copied to either /etc/pipewire for systemwide config or $HOME/.config/pipewire for user config. Some bugs remain though: - The documentation needs to be updated. - a note will be put in the /usr/share config files to explain this - the fedora package will be updated to own the /etc/pipewire directory.
*** Bug 1963935 has been marked as a duplicate of this bug. ***
Is there any particular reason why the config files in /etc were removed before updating the documentation and without a very prominent announcement of this new policy? Given that there's a whole lot of reasons why people like me tend to expect editable config files in /etc (the FHS, decades of tradition, 99% other packages doing it that way), there should IMHO be a big red blinking banner somewhere telling all the confused users that they need to go digging for files in /usr/share and hand-copy them over because RPM can't be bothered to put them into /etc anymore. At the very least, it would be great if the package shipped at least an /etc/pipewire/README explaining what's going on and where to find the config files.
FEDORA-2021-5a5f27d6b3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5a5f27d6b3
FEDORA-2021-5a5f27d6b3 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5a5f27d6b3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5a5f27d6b3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-5a5f27d6b3 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
This decision to put config in /usr/share/ caused my system's sound to silently (I know...) break on upgrade to F35, and this has the potential to affect many people. I filed a separate bug here: https://bugzilla.redhat.com/show_bug.cgi?id=2031328