Closed meator closed 1 month ago
The polybar Void linux package was lacking /etc/polybar/config.ini in its conf_files, so updates of polybar would have incorrectly overwritten it. This was fixed in https://github.com/void-linux/void-packages/commit/2ff911309930b4b35b13a0c9fe400a52303d5dbe, adding /etc/polybar/config.ini to polybar's conf_files. The problem is that xbps-install will look at the old package's metadata when evaluating conf_files. The old packages had no conf_files, so this update will happily overwrite /etc/polybar/config.ini, even though the sole purpose of https://github.com/void-linux/void-packages/commit/2ff911309930b4b35b13a0c9fe400a52303d5dbe is to prevent that.
polybar
/etc/polybar/config.ini
conf_files
xbps-install
I believe that the conf_files property of the "incoming" package should be prioritized when extracting an update.
oops, duplicate of #342
meator
commented
1 month ago meator
commented
1 month ago
The
polybarVoid linux package was lacking/etc/polybar/config.iniin itsconf_files, so updates ofpolybarwould have incorrectly overwritten it. This was fixed in https://github.com/void-linux/void-packages/commit/2ff911309930b4b35b13a0c9fe400a52303d5dbe, adding/etc/polybar/config.initopolybar'sconf_files. The problem is thatxbps-installwill look at the old package's metadata when evaluatingconf_files. The old packages had noconf_files, so this update will happily overwrite/etc/polybar/config.ini, even though the sole purpose of https://github.com/void-linux/void-packages/commit/2ff911309930b4b35b13a0c9fe400a52303d5dbe is to prevent that.I believe that the
conf_filesproperty of the "incoming" package should be prioritized when extracting an update.