Problem: glib-networking-2.60.1-2.fc30.i686 has inferior architecture

Last metadata expiration check: 0:30:40 ago on Tue 14 May 2019 07:59:19 AM EDT.
Error: 
 Problem: glib-networking-2.60.1-2.fc30.i686 has inferior architecture
  - cannot install both glib-networking-2.60.2-1.fc30.x86_64 and glib-networking-2.60.1-2.fc30.x86_64
  - cannot install both glib-networking-2.60.1-2.fc30.x86_64 and glib-networking-2.60.2-1.fc30.x86_64
  - cannot install the best update candidate for package glib-networking-2.60.1-2.fc30.i686
  - cannot install the best update candidate for package glib-networking-2.60.1-2.fc30.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)

If I do --allowerasing it wants to uninstall:
glib-networking i686 2.60.1-2.fc30 @fedora 553 k
gtk3 i686 3.24.8-1.fc30 @fedora 20 M
libdbusmenu-gtk3 i686 16.04.0-11.fc30 @fedora 108 k
libsoup i686 2.66.1-2.fc30 @fedora 1.3 M
rest i686 0.8.1-5.fc30 @fedora 226 k
steam i686 1.0.0.61-1.fc30 @rpmfusion-nonfree-updates 2.8 M

1 Like

I’m experiencing the same problem. This seems to be related to steam having 32 bit dependencies. I think an updated steam rpm package would be required to fix it. Thankfully simply skipping the update for glib-networking does not seem to have a negative impact. Given the popularity of the steam package, I’m guessing it wont take too long for this to all get sorted out.

Which repository do you have for Steam?

Not sure about OP, but mine is from rpmfusion

After poking around dnf for a bit, I think my original thought about steam being the problem was incorrect. It appears there is not an updated 32 bit version of glib-networking yet, upon which steam, gtk3 and others depend. As soon as that package gets built to match the version of the 64 bit glib-networking then the updates should go through as normal.

1 Like

Excuse me. I didn’t check. So there is an updated glib-networking package for x86_64, while for i686 there is still an old version and steam needs the updated version? If that’s the case, I think that you could file a bug.

https://bugzilla.redhat.com/show_bug.cgi?id=1708975

1 Like

This was updated today.