FS#58333 - [neofetch] Pacman overwrites config file while updating

Attached to Project: Community Packages
Opened by kpc21 (kpc21) - Tuesday, 24 April 2018, 11:26 GMT
Last edited by Morten Linderud (Foxboron) - Tuesday, 24 April 2018, 14:56 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Morten Linderud (Foxboron)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The Neofetch tool uses a config file located at: /etc/neofetch/config.conf or (per-user) ~/.config/neofetch/config.conf.

I created a custom config and I was happily using it.

However, the last update of the package included also a modification in the config file, which resulted in overwriting its contents by Pacman with the default version. I am unhappy because my custom config is gone /is there any way to recover it or do I have to make it again from scratch?/.

From what I understand, the config files should be specified in the PKGBUILD file in the backup line as explained here: https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave#Package_backup_files to avoid overwriting them during an update and saving its new version with a .pacnew extension instead.
This task depends upon

Closed by  Morten Linderud (Foxboron)
Tuesday, 24 April 2018, 14:56 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with 3.4.0-2
Comment by Eli Schwartz (eschwartz) - Tuesday, 24 April 2018, 12:01 GMT
Deleted data is deleted data... This shouldn't have happened (backup files are indeed the correct solution here) but if you kept backups with e.g. snap-pac or etckeeper you'd be able to recover it anyway.

Loading...