[SOLVED] Wine install on F17, protected multilib

[jarrett]

Hi,
I'm trying to install wine on F17 however I am running into some problems with protected multilib versions.

Error: Protected multilib versions: fontconfig-2.8.0-6.fc17.i686 != fontconfig-2.8.0-7.fc17.x86_64
Error: Protected multilib versions: libdrm-2.4.33-1.fc17.i686 != libdrm-2.4.33-3.fc17.x86_64
Error: Protected multilib versions: libpciaccess-0.13-2.fc17.i686 != libpciaccess-0.13.1-1.fc17.x86_64
Error: Protected multilib versions: glib2-2.32.1-1.fc17.i686 != glib2-2.32.3-1.fc17.x86_64
Error: Protected multilib versions: libxcb-1.8-2.fc17.i686 != libxcb-1.8.1-1.fc17.x86_64
Error: Protected multilib versions: libgphoto2-2.4.11-3.fc17.i686 != libgphoto2-2.4.14-1.fc17.x86_64
Error: Protected multilib versions: openldap-2.4.30-2.fc17.i686 != openldap-2.4.31-2.fc17.x86_64
Error: Protected multilib versions: 2:libogg-1.2.2-4.fc17.i686 != 2:libogg-1.3.0-1.fc17.x86_64

yum update says nothing needs updating.
repos enabled:
f17, f17 updates, rpm fusion free, rpm fusion free updates, rpm fusion nonfree, rpm fusion nonfree updates.

Help?

PS: I finally found my way back to Fedora after not using it for a couple of years. I like the Gnome 3 shell thing. Been using Arch with KDE since last time I had fedora running. Cheers!

[DBelton]

you probably installed some of the packages before F17 disabled the updates-testing repo, so you got newer versions than are available in the standard fedora and updates repo.

Try enabling the updates-testing repo and run it again.

yum --enablerepo=updates-testing install wine

[jarrett]

Originally Posted by DBelton

you probably installed some of the packages before F17 disabled the updates-testing repo, so you got newer versions than are available in the standard fedora and updates repo.

Try enabling the updates-testing repo and run it again.

yum --enablerepo=updates-testing install wine

yah, that did the trick, thank you!!

[DBelton]

Also, unless you enable the updates-testing repo, you won't get many updates at all until after the F17 release. The only updates getting pushed into the stable repo are the critical blocker bug fixes, all the other updates are going to be in updates-testing until after the release.

I usually go back and re-enable the updates-testing repo after the update disables it right before a release.

[jarrett]

On that note, when the final version is released do I need to update my repo sources?

[DBelton]

if you manually edit your repo files to enable updates-testing, then you would need to manually edit it again when the final version is released if you wish to go back and disable it. The update has already happened that disabled it, future updates should leave it how you have it now.

But other than that, there is no reason you should need to update your repo files just because the final version is released.

(Rpmfusion has also disabled their updates-testing repos with an update as well, if you have those installed)

[jarrett]

alright, thanks buddy!