FS#76885 - [pacman-contrib] pacdiff doesn't recognize .pacnew files from NoUpgrade
Attached to Project:
Community Packages
Opened by Andrea (mane.andrea) - Tuesday, 20 December 2022, 10:48 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 21 December 2022, 22:46 GMT
Opened by Andrea (mane.andrea) - Tuesday, 20 December 2022, 10:48 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 21 December 2022, 22:46 GMT
|
Details
Summary and Info:
Files specified in the field `NoUpgrade` of pacman.conf are installed as `.pacnew` by pacman, as they should. However, when that happens, pacdiff is unable to find them. This means that a user who doesn't notice a file being upgraded (or forgets about it) will miss out on new features. Steps to Reproduce (example): Edit the following line to pacman.conf ``` NoUpgrade=usr/share/X11/xkb/symbols/us ``` Pretend to upgrade that package ``` # pacman -S xkeyboard-config --asdeps [...] warning: /usr/share/X11/xkb/symbols/us installed as /usr/share/X11/xkb/symbols/us.pacnew [...] ``` So far so good. Call pacdiff ``` # pacdiff [no output] ``` See if it exists ``` $ ls /usr/share/X11/xkb/symbols/us.pacnew /usr/share/X11/xkb/symbols/us.pacnew ``` |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 21 December 2022, 22:46 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Wednesday, 21 December 2022, 22:46 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
FS#16764? For example:# DIFFSEARCHPATH=/usr pacdiff -f -o
/usr/share/X11/xkb/symbols/us.pacnew
Perhaps then a follow-up question is: why doesn't pacman's database contain the information about my new files in NoUpgrade? Would that be a reasonable feature request?
In any case, I think this bug report can be closed.
I doubt it. But you can read more about the pacman database structure at [1][2]
[1] https://wiki.archlinux.org/title/pacman#Database_structure
[2] https://bbs.archlinux.org/viewtopic.php?id=265018