Prior to successfully executing the full system upgrade, I found that /usr/bin/install was a symlink to /bin/install. Using "pacman -Qo /bin/install", I found that the file /bin/install was owned by the coreutils 8.15-1 package. The symlink /usr/bin/install, however, was not owned by any package. The conflict arises because coreutils 8.16-2 wants to put the new install program in /usr/bin instead of its previous location under /bin.
My memory is a bit fuzzy, but I seem to recall running into a problem installing some third party library that had /usr/bin/install hard-coded into its build script and claimed the file didn't exist. I may have manually created the symlink /usr/bin/install to /bin/install as a quick-fix, then forgot to remove it. In retrospect, I could have confirmed/refuted this hypothesis by comparing the time stamp on the symlink /usr/bin/install to /bin/install. If the symlink was created well after /bin/install, then I'm probably to blaim; on the other hand, if the symlink was created essentially at the time /bin/install was created, then most likely the creators of the coreutils package forgot to claim ownership of the symlink.
]]>Getting the following error:
(85/85) checking for file conflicts [###########################] 100%
error: failed to commit transaction (conflicting files)
coreutils: /usr/bin/install exists in filesystem
I am reluctant to delete/move /usr/bin/install for fear of breaking the system ..
Anyone help here?