You are not logged in.

#1 2020-05-25 18:08:14

logic_guy76
Member
Registered: 2020-05-24
Posts: 4

[SOLVED] Need help resolving dependency conflicts

I am trying to get my Arch Linux 32 system going again after about a 1-1/2 year hiatus.  I successfully updated the keyring using these commands:
pacman-key --refresh-keys
pacman -S archlinux32-keyring

I also successfully upgraded pacman.

I noticed that, about a year ago, a major upgrade was introduced to Arch Linux 32 with the addition of the pentium4 architecture.  This system does indeed have a pentium4 processor so I changed /etc/pacman.conf to have architecture=pentium4.

Next, I tried doing a full upgrade with
pacman -Qqn | pacman -S -
and I get these messages: 

# pacman -Qqn | pacman -S -
warning: archlinux32-keyring-20200408-1.0 is up to date -- reinstalling
warning: iscan-2.30.3.1-1 is up to date -- reinstalling
warning: mozilla-common-1.4-5.0 is up to date -- reinstalling
warning: pacman-5.2.1-5.0 is up to date -- reinstalling
warning: sound-theme-freedesktop-0.8-3.0 is up to date -- reinstalling
warning: xorg-font-utils-7.6-5.0 is up to date -- reinstalling
warning: xorg-fonts-alias-1.0.3-2.0 is up to date -- reinstalling
:: systemd-libs and libsystemd are in conflict. Remove libsystemd? [y/N] y
:: xorg-mkfontscale and xorg-mkfontdir are in conflict. Remove xorg-mkfontdir? [y/N] y
warning: dependency cycle detected:
warning: harfbuzz will be installed before its freetype2 dependency
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: systemd will be installed before its libelf dependency

resolving dependencies...
looking for conflicting packages...

Packages (596) adobe-source-code-pro-fonts-2.030ro+1.050it-5.0  alsa-topology-conf-1.2.2-2.0  alsa-ucm-conf-1.2.2-1.0 ... (lots more) ... zstd-1.4.4-1.0

Total Installed Size:  3237.13 MiB
Net Upgrade Size:       578.71 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
xorgproto: /usr/include/X11/DECkeysym.h exists in filesystem (owned by xproto)
xorgproto: /usr/include/X11/HPkeysym.h exists in filesystem (owned by xproto)
xorgproto: /usr/include/X11/Sunkeysym.h exists in filesystem (owned by xproto)
xorgproto: /usr/include/X11/X.h exists in filesystem (owned by xproto)
(lots more similar messages about xorgproto)
libx11: /usr/include/X11/extensions/XKBgeom.h exists in filesystem (owned by kbproto)
Errors occurred, no packages were upgraded.

Any suggestion about how to resolve these conflicts?
Thanks,
Charles Bailey

Last edited by levi (2020-05-26 20:34:43)

Offline

#2 2020-05-25 21:34:47

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 952

Re: [SOLVED] Need help resolving dependency conflicts

I would suggest doing a pacman -Syu rather than a pacman -Qqn into a pacman -S.  A number of packages have changed names or been subsumed into more comprehensive packages, so installing the same list of packages as you had a year or two ago is likely to be problematic.

You'll still likely encounter problems though.  Observe entries here which end 'requires manual intervention'.  You might need to follow those mitigations if you have any of those packages installed.

You can then do a pacman -Qqn into a pacman -S to catch any packges you have installed that are still i686.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Online

#3 2020-05-26 06:01:39

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 601

Re: [SOLVED] Need help resolving dependency conflicts

Like levi, I would recommend running `pacman -Syu` first.
Note, that putting `Architecture = pentium4` is not necessary, `Architecture = auto` should[1] autodetect the architecture.

regards,
deep42thought

[1] We have test machines, where the test fails and i686 gets used, although, pentium4 would be supported.

Offline

#4 2020-05-26 15:57:16

logic_guy76
Member
Registered: 2020-05-24
Posts: 4

Re: [SOLVED] Need help resolving dependency conflicts

I was able to fix some of the xorgproto conflicts by removing some of the conflicting packages.  I eventually got down to where the only conflicts left were in xproto and kbproto, but I couldn't remove them because they were dependencies of libx11 and libx11 was a dependency of a whole bunch of stuff.  It appeared that the new version of libx11 depends on xorgproto but not on xproto and kbproto so I forced a delete of those last two with
pacman -Rdd xproto kbproto
Then I was able to install xorgproto without any conflicts and I was also able to upgrade libx11.
Finally, I did pacman -Syu and it downloaded about 579 packages and ran through the whole install process without any errors.  I rebooted and lo and behold my Arch Linux system is working again.  Good job administrators!

Offline

#5 2020-05-26 20:35:17

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 952

Re: [SOLVED] Need help resolving dependency conflicts

Good to hear.  I've modified the thread title to record that you're all happy now, assuming you are with this.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Online

Board footer

Powered by FluxBB