DNF Upgrade issue with gdk-pixbuf2

Been having a small issue trying to run upgrade

[moksh@resolve ~]$ sudo dnf upgrade   

Error:
 Problem: package gdk-pixbuf2-modules-2.36.12-6.el8_10.x86_64 from @System requires gdk-pixbuf2(x86-64) = 2.36.12-6.el8_10, but none of the providers can be installed
  - cannot install both gdk-pixbuf2-2.36.12-7.el8_10.x86_64 from baseos and gdk-pixbuf2-2.36.12-6.el8_10.x86_64 from @System
  - cannot install both gdk-pixbuf2-2.36.12-7.el8_10.x86_64 from baseos and gdk-pixbuf2-2.36.12-6.el8_10.x86_64 from baseos
  - cannot install the best update candidate for package gdk-pixbuf2-modules-2.36.12-6.el8_10.x86_64
  - cannot install the best update candidate for package gdk-pixbuf2-2.36.12-6.el8_10.x86_64

I did try to use –allowerasing but it wanted to remove lots of packages I need. Any tips?

Try:

dnf clean all
dnf update

if you still have problems after that, please do:

dnf repolist --all

so we can see what repos you have configured.

Thank you, the dnf clean all did the trick.

1 Like

Same issue for me on AlmaLinux, “dnf clean all” didn’t fix it though.

The DNF does cache metadata of the repositories. The ‘clean all’ clears the cache.
If cache is empty or stale, then DNF recreates its cache from repos.

Occasionally, the cache seems “ok”, but is in conflict with actual repo content.
On such occasion an error like in OP can occur and clearing the cache solves it.


However, (meta)data on repo mirror can also be inconsistent, if the mirror is still syncing.
Different mirror sites sync in their own schedule.

Besides, mirrors of “AlmaLinux” use entirely different source than mirrors of Rocky Linux.
The “only” common denominator of these two distros is how DNF (mis)behaves.

As @jlehtone hinted for you it’s more likely you are connecting to mirrors that haven’t synced properly. But since that is an Alma problem, you will have to ask them about it.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.