FS#55892 - pacman overwrote /etc/ file when original, current, and new differed, instead of making a .pacnew
Attached to Project:
Pacman
Opened by Jorge Luis Martinez Gomez (jol) - Friday, 06 October 2017, 23:05 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 23:18 GMT
Opened by Jorge Luis Martinez Gomez (jol) - Friday, 06 October 2017, 23:05 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 06 October 2017, 23:18 GMT
|
Details
Summary and Info:
I have a custom /etc/i3/config file that was overwritten when upgrading i3-wm from version 4.13-1 to 4.14.1-1. I don't know if this is happening with other packages, but I'm expecting it (will check later). This is only an annoyance for me because I have my configuration files backed up, but I worry that other people might be losing theirs. This is why I put severity on High (should it be Critical?). The file differed between the package versions: $ diff -u <(tar xOf /var/cache/pacman/pkg/i3-wm-4.13-1-x86_64.pkg.tar.xz etc/i3/config) <(tar xOf /var/cache/pacman/pkg/i3-wm-4.14.1-1-x86_64.pkg.tar.xz etc/i3/config) --- /proc/self/fd/11 2017-10-06 15:48:50.968207750 -0700 +++ /proc/self/fd/12 2017-10-06 15:48:50.968207750 -0700 @@ -1,6 +1,6 @@ # i3 config file (v4) # -# Please see http://i3wm.org/docs/userguide.html for a complete reference! +# Please see https://i3wm.org/docs/userguide.html for a complete reference! # # This config file uses keycodes (bindsym) and was written for the QWERTY # layout. I was expecting for a .pacnew file to be created for the new package's file, in this scenario. I think my pacman.conf file differs from the default only in activating ILoveCandy, the multilib repository, and adding my own repository. I can share it if anyone likes. Steps to Reproduce: 1. Have a custom /etc/i3/config. 2. Upgrade the package. 3. Check if /etc/i3/config is still the custom file. I can share the old version package too, if anyone wants it to reproduce this bug. |
This task depends upon
Comment by
Jorge Luis Martinez Gomez (jol) -
Friday, 06 October 2017, 23:16 GMT
Never mind. Turns out this is not a pacman bug, but one with i3-wm
PKGBUILD. I thought .pacnew's were for everything under /etc/, but
it turns out that it's only for those in the PKGBUILD's backup
array, and i3-wm hasn't defined it.