https://wiki.archlinux.org/index.php/Co … mpty_posts
Closing
]]>1) "pacman -Rns libxfont" to remove libxfont
2) "pacman -Syu" answering No to all the proto replacements - lots of packages updated
3) "pacman -Syu" answering Yes to the proto replacements. - several packages removed, only a few added/updated
I manually installed lixfont2, then removed libxfont and then executed "pacman -Suy" without any issue.
(had this issue on my Raspberry Pi, Arch Linux ARM)
*libxfont2 to be "that guy" to correct a minor typo, then all proceeded as normal on two Arch machines for me.
Kudos, thanks for the tip
I was having the same issue today and when I removed libxfont it resolved the problem. It seems I got libxfont from somewhere on both of my arch systems even though it is not in the repos. As far as I can tell It got removed or upgraded to libxfont2 recently and is now causing problems.
By running this command it should fix your problem by removing the conflicting package.
pacman -Rs libxfont
Thanks, This is my issue too
]]>I was having the same issue today and when I removed libxfont it resolved the problem. It seems I got libxfont from somewhere on both of my arch systems even though it is not in the repos. As far as I can tell It got removed or upgraded to libxfont2 recently and is now causing problems.
By running this command it should fix your problem by removing the conflicting package.
pacman -Rs libxfont
Thnks it works for me
]]>pacman -Rs libxfont
just wanted to say thankyou, this resolved the issue for me..
]]>The second "y" forces ...
Yes, and the general mindset of forcefully overriding pacman's sane default behavior leads to countless problems. Pacman is one of arch linux's greatest strengths. Use it properly. On occasion a second 'y' will be called for, on occasion a second 'u' may be called for, on very rare occasion actual '--force' may be called for. But none of these should be one's default use.
Using these flags needlessly suggests that the user thinks they are smarter than pacman while simultaneously proving that they aren't.
]]>The second "y" forces a refresh of the repo cache in case something else has been updated/added
No it doesn't. You only need this if for some reason your local sync database is corrupt and doesn't recover, or if you have a shitty mirror and change mirrors.
If your sync database is healthy and your mirror is as well, you don't need it twice. You're just created excess and useless bandwidth usage for both the server as well as yourself.
and the second "u" allows for downgrades of software as well as upgrades, which can be necessary if something is being rolled back.
Never happens unless you go from the testing back to the stable repositories (which is an action you yourself consciously have to make).
If a package has already been pushed to the repositories and for some reason requires a downgrade, the package's epoch will be increased: https://wiki.archlinux.org/index.php/PKGBUILD#epoch
TL;DR: They are excess flags, only required for very specific situations. For normal system updates: `pacman -Syu`
]]>Adderall wrote:... then ran sudo pacman -Syyuu again.
There is just no reason for the excess flags. The command to update your system is `pacman -Syu`.
They aren't excess flags. The second "y" forces a refresh of the repo cache in case something else has been updated/added and the second "u" allows for downgrades of software as well as upgrades, which can be necessary if something is being rolled back.
]]>... then ran sudo pacman -Syyuu again.
There is just no reason for the excess flags. The command to update your system is `pacman -Syu`.
]]>I was having the same issue today and when I removed libxfont it resolved the problem. It seems I got libxfont from somewhere on both of my arch systems even though it is not in the repos. As far as I can tell It got removed or upgraded to libxfont2 recently and is now causing problems.
By running this command it should fix your problem by removing the conflicting package.
pacman -Rs libxfont
I used this command, then ran sudo pacman -Syyuu again. Then I just answered 'y' to all those weird prompts, and the problem went away. Thanks man.
]]>