You are not logged in.
pacman -Syu gets through loading and checking for file conflicts, then :
(118/118) checking for file conflicts [######################################] 100%
error: failed to commit transaction (conflicting files)
qt4: /usr/include/qt4/Qt/Qt3Support exists in filesystem
...
3650 similar lines
[root@glimmer leo]# uname -a
Linux glimmer 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/Linux
Thank you for any suggestions you may have.
Last edited by glimmer (2017-01-13 23:39:00)
Offline
How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.
Offline
Thanks, I have not manually installed anything since the previous system update (pacman -Syu).
Since there are so many files, should I do "pacman -Syu --force"?
Last edited by glimmer (2017-01-13 22:41:50)
Offline
No, you should probably follow the instructions in the link provided. What package owns those files? If you have 3650 files in your filesystem that should belong to packages but are untracked by pacman, there is a serious problem you need to get to the bottom of. Using --force would, at best hide the symptoms of this real problem which could get worse in the future if left untreated, or at worst leave you with a completely broken and unbootable system.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
3756 unowned files with qt4 in path
3644 pacman "exists in filesystem" messages
Even were I to repair all these, or move all and update and luck out, it sounds like it might not get to the root of the problem. Should I try to diagnose from sysem logs? Is it time to back up and reinstall?
Offline
Oh, that's different. Do all of the files belong to the qt4 package? That's not nearly as bad as I was thinking. I was under the impression that your package database was completely broken - if it's just one package that is somehow screwy, you can use --force for that one specific package. But do not use --force with -Syu.
Something odd did happen, but if it was a one time event with one package, then figuring out the root cause may not be worth the trouble. If it is *many* packages however, you'd definitely want to get to the bottom of it.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
thanks, that worked
Offline