You are not logged in.
Pages: 1
I have noticed that some binaries have not been working in recent days. The first being rsync, and the latest being meson. When attempting to reinstall the packages both came up with conflicting files errors. Following the instructions at pacman troubleshooting, I was able to confirm that none of the conflicting files were owned by any package and was able to safely remove them. However when trying to reinstall meson there were tens of conflicting files, more than I wanted to check individually. I ended up using the --overwrite switch, but was wondering if there was a better solution since arch wiki recommends against this. Also there definitely could be other broken binaries on my system that I am not aware of, plagued with the same problem. Is there a better way to find all packages that are broken in this way, remove the conflicting files, then reinstall them?
Thanks for your help.
Last edited by winlawson (2024-05-05 18:37:02)
Offline
Did pacman report meson and rsync as being installed when you tried to reinstall the packages? Has the system hung particularly during a pacman update? Please post the link the second command below generates.
# LC_ALL=C pacman -Qkk 2>&1 | grep -v ', 0 altered files' | tee /tmp/broken_packages.txt
cat /tmp/broken_packages.txt | curl -F 'file=@-' 0x0.stOffline
Sorry for the late response, I had my notification settings messed up. Here is the output: http://0x0.st/XKlk.txt
Thank you in advance for any help!
Offline
db5.3: no mtree file
libbsd: no mtree file
llvm-libs: no mtree file
wget: no mtree filepacman -S --dbonly db5.3 libbsd llvm-libs wgetwarning: filesystem: /root (Permissions mismatch)stat /rootOnline
Thanks for the help
Offline
Did you fix the /root permissions?
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online
Pages: 1