As mentioned last week, I waited a bit too long to upgrade my Arch Linux install recently. While overall the upgrade went smooth, I did run into a handful of issues, this one being the second of three.
After resolving the issue with rpm-tools and rpmextract, I hit a snag with another set of packages, dbus-python and extra/python-dbus.
Things seemed simple enough, I was asked if I wanted to replace dbus-python with extra/python-dbus. Having been through this type of thing before, packages get renamed, you favor the new package and call it a day.
Or so I thought. Simply saying y at the prompt, when doing a full upgrade, resulted in an error about the transaction failing to prepare as it couldn’t satisfy the dependencies:
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace dbus-python with extra/python-dbus? [Y/n]
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing alsa-lib (1.2.12-1) breaks dependency 'alsa-lib=1.2.11' required by lib32-alsa-lib
:: installing alsa-plugins (1:1.2.12-1) breaks dependency 'alsa-plugins=1:1.2.7.1' required by lib32-alsa-plugins
-> error installing repo packagesSatisfying dependencies
Since the dependency error was actually pointing out an issue with some alsa-lib packages, I figured I should try to get this resolved outside of the context of a full upgrade.
When in doubt, single the package out.
Knowing that extra/python-dbus was the package that was struggling to install, I went ahead and tried to install it directly, by itself:
% yay -S extra/python-dbus
Sync Explicit (1): python-dbus-1.3.2-4
resolving dependencies...
looking for conflicting packages...
:: python-dbus-1.3.2-4 and dbus-python-1.3.2-3 are in conflict. Remove dbus-python? [y/N] Y
Packages (2) dbus-python-1.3.2-3 [removal] python-dbus-1.3.2-4
Total Download Size: 0.11 MiB
Total Installed Size: 0.60 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
python-dbus-1.3.2-4-x86_64 116.2 KiB 478 KiB/s 00:00 [#####################################################################] 100%
(1/1) checking keys in keyring [#####################################################################] 100%
(1/1) checking package integrity [#####################################################################] 100%
(1/1) loading package files [#####################################################################] 100%
(1/1) checking for file conflicts [#####################################################################] 100%
(2/2) checking available disk space [#####################################################################] 100%
:: Processing package changes...
(1/1) removing dbus-python [#####################################################################] 100%
(1/1) installing python-dbus [#####################################################################] 100%
Optional dependencies for python-dbus
python-gobject: D-Bus services via PyGI [installed]
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...Not much of a shocker, things worked fine. After that I tried another full upgrade and ran into another issue, but I’ll be saving that one for another post.
