FS#39725 - [pacman] missing package files after upgrade
Attached to Project:
Pacman
Opened by Rasmus Thystrup Karstensen (rathka) - Wednesday, 02 April 2014, 23:28 GMT
Last edited by Allan McRae (Allan) - Wednesday, 19 November 2014, 07:14 GMT
Opened by Rasmus Thystrup Karstensen (rathka) - Wednesday, 02 April 2014, 23:28 GMT
Last edited by Allan McRae (Allan) - Wednesday, 19 November 2014, 07:14 GMT
|
Details
Summary and Info:
I have occasionally experienced that files from an upgraded package are missing from the filesystem. Last time I ran into this problem, the files from the following packages was missing: libsystemd libutil-linux which led to the my system failing to boot. I upgraded three x64 systems at roughly the same time, but only two of them had the issue. Re-installing the packages with missing files solves the problem. To counter this, I now run this command after each update: pacman -Ql | while read line; do [ -e "${line#*\ }" ] || echo ${line}; done to ensure that no system libraries is missing. The above command currently finds some broken symlinks and missing license files on all of my x64 systems. Steps to Reproduce: I have run into this problem a couple of times, but have not been able to reproduce it after occurrence. I guess reproducing it would require a snapshot of the system before upgrading (pacman -Suy), which I do not have the capacity for. Suggestion: Would it be possible to include the functionality from the command above, when running "pacman -Suy"? or is there a simple way of defining custom scripts to run after a system update? |
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 19 November 2014, 07:14 GMT
Reason for closing: Works for me
Wednesday, 19 November 2014, 07:14 GMT
Reason for closing: Works for me
I'm more concerned about what is wrong with your system... Did you shut down properly?
On my last update (5 minutes ago) "pacman -Qqk" listed: "talloc /usr/lib/python2.7/site-packages/talloc.so"
reinstalling talloc solved the problem.
I have experienced missing files on a few occations since I reported the bug, but not with any system critical files.
[root@Ennasus tmp]# pacman -Qqk
js17 /usr/lib/libmozjs-17.0.so
js17 /usr/lib/pkgconfig/mozjs-17.0.pc
libusbmuxd /usr/lib/libusbmuxd.so
libusbmuxd /usr/lib/pkgconfig/libusbmuxd.pc
talloc /usr/lib/python2.7/site-packages/talloc.so
reinstalling the packages resolved the problem
That's the third system I have confirmed this bahaviour on.
I'm finding this strange that one user sees it on three systems, but no-one else has reported it or can replicate.