sudo pacman -Su
[sudo] password for artix:
:: Starting full system upgrade...
:: Replace compositeproto with world-testing/xorgproto? [Y/n] y
:: Replace damageproto with world-testing/xorgproto? [Y/n] y
:: Replace fixesproto with world-testing/xorgproto? [Y/n] y
:: Replace fontsproto with world-testing/xorgproto? [Y/n] y
:: Replace inputproto with world-testing/xorgproto? [Y/n] y
:: Replace kbproto with world-testing/xorgproto? [Y/n] y
:: Replace randrproto with world-testing/xorgproto? [Y/n] y
:: Replace recordproto with world-testing/xorgproto? [Y/n] y
:: Replace renderproto with world-testing/xorgproto? [Y/n] y
:: Replace scrnsaverproto with world-testing/xorgproto? [Y/n] y
:: Replace videoproto with world-testing/xorgproto? [Y/n] y
:: Replace xextproto with world-testing/xorgproto? [Y/n] y
:: Replace xf86dgaproto with world-testing/xorgproto? [Y/n] y
:: Replace xf86vidmodeproto with world-testing/xorgproto? [Y/n] y
:: Replace xineramaproto with world-testing/xorgproto? [Y/n] y
:: Replace xproto with world-testing/xorgproto? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: libxfont: removing fontsproto breaks dependency 'fontsproto>=2.1.3'
If I respond "y" to all there is a missing dependency, if I respond "n" to all then you can go about upgrading current packages.
There is another thread about this - I had to do it in three steps.
1) remove libxfont
2) redo the upgrade, answering No to all the replace questions
3) then redo and answer Yes to all the replace questions.
Worked that way for me on two separate machines.
I think you can skip step 2 if you do step 1
Trying step 1, I get:
[artix ~]# pacman -R libxfont2
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: xorg-server: removing libxfont2 breaks dependency 'libxfont2'
[artix ~]#
Then I tried (on a whim):
[artix ~]# pacman -R libxfont2 xorg-server
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: displaymanager-openrc: removing xorg-server breaks dependency 'xorg-server'
[artix ~]#
I'd like to try the update; I am apparently having some problems with xorg (long freezes).
If you really wish to remove a package the command to use is
sudo pacman -Rdd libxfont2
translate?
actually that should be added to the man page
You can use pacman --help command:
pacman -R --help
It is in Archwiki:
https://wiki.archlinux.org/index.php/pacman#Removing_packages
I do not wish to duplicate vast Archwiki.
https://wiki.archlinux.org/
Why are you guys removing libxfont2, it is libxfont that has the conflict with the protobunch. At least my installed libxfont2 has no issues. Removing libxfont with simple -R is adequate as it is an orphan, nothing depends on it. It was left behind I assume during some xorg update which brought libxfont2.
Do as step1 says
then jump to 3
leave libxfont2 alone.
I think it is because I never had libxfont installed in the first place, so when that step failed, I figured you must have meant libxfont2. My bad assumption.
So there is no libxfont on my system, and only libxfont2, how do I proceed? I.e., do I want to replace these or not -- most times, I am not faced with this sort of fork in the road when doing upgrades (it does happen very rarely, but even then, I'm usually able to intuit what to do; in this case there seems to be dozens of repo paths involved).
I'm pretty sure I just force removed (-Rdd) libxfont2 on one of my machines and then updated everything. I think whatever libxfont2 provides is included in xorgproto, so it's not a big deal.
libxfont2 is a rasterization library
xorgproto is a combination of proto-col headers
So you are now running xorg-server without a rasterization library
Unless on someone's installation libxfont2 had a conflict with removing all the old -proto pkgs (protocol headers), which nobody here seems to have reproduced, why deprive your xorg server of a dependency?
libxfont, again and again, was a separate second package different than libxfont2. libxfont (without the 2) had the problem with installing xorgproto and replacing the old xxx-proto pkgs, NOT libxfont2!
It seems some of you who had fresher installations and did not have the old libxfont alongside with libxfont2 are getting confused by all of this and removing libxfont2 for no good reason.
Did you actually try the update? The only reason people need to remove libxfont is that it causes a blocker. If you don't have it installed, and libxfont2 is not causing any problem, they you should just be able to do the upgrade without a problem.
oye
Today, I was able to apply the update without incident, although I did have to remove a package first because it was causing some conflict or another.