FS#20723 - [kdebase-workspace] changed /usr/share/config/kdm/backgroundrc gets overwritten
Attached to Project:
Arch Linux
Opened by quantax (quantax) - Thursday, 02 September 2010, 18:47 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 03 September 2010, 08:49 GMT
Opened by quantax (quantax) - Thursday, 02 September 2010, 18:47 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 03 September 2010, 08:49 GMT
|
Details
Description:
Most of KDM's configuration is kept in /usr/share/config/kdm/kdmrc. This file is already in the backup array of kdebase-workspace's PKGBUILD. However this is only most of the configuration. The configuration for KDM's Background mode (no fancy theme, just a plain Qt dialog on top of a wallpaper) is kept in /usr/share/config/kdm/backgroundrc. This file gets overwritten when the package is updated. Thus this configuration file should be added to the package's backup files. Additional info: kdebase-workspace 4.5.1 Steps to reproduce: - install kdebase-workspace - change /usr/share/config/kdm/backgroundrc - reinstall kdebase-workspace Fix: Add /usr/share/config/kdm/backgroundrc to the backup array of kdebase-workspace's PKGBUILD. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 03 September 2010, 08:49 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#14252
Friday, 03 September 2010, 08:49 GMT
Reason for closing: Duplicate
Additional comments about closing:
Apparently there is no way to have two sysconf directories at this moment, for example one for "distro" and other for "admin".
If kdm had "distro" configuration files they should not be in the backup array, but the "admin" ones should be, if they were provided by the package at all. But since there is no such distinction, all of kdm's configuration files should be in the backup array in order to prevent them from being overwritten. This includes also /usr/share/config/kdm/backgroundrc.
As for the workarounds: I know how to prevent this from happening on my installation. Nevertheless I thought that pacman should not overwrite files that are meant to be changed by the user -- especially configuration files. That is why I filed this bug report.