How Do I Get Around Broken RPM Fusion Deps?

[dd_wizard]

I was finally able to boot a nightly build with desktop-x86_64-20100211.17.iso. However, when I tried to pre-update totem-pl-parser to get around dependency issues, I got a ton of .so conflicts from RPM Fusion. Since there's no full install iso available, what's the best way to update from F12 to F13? Or should I wait for the dependency issues to get resolved?

dd_wizard

---------- Post added at 03:07 PM CST ---------- Previous post was at 01:10 PM CST ----------

Here's some more information. Using:
sudo yum --skip-broken --disablerepo=* --enablerepo=*rawhide update > yum.txt 2>&1
generates the following:
Packages skipped because of dependency problems:
brasero-2.29.90-1.fc13.x86_64 from rawhide
brasero-libs-2.29.90-1.fc13.x86_64 from rawhide
brasero-nautilus-2.29.90-1.fc13.x86_64 from rawhide
gmime-2.5.1-1.fc13.x86_64 from rawhide
totem-2.29.4-2.fc13.x86_64 from rawhide
totem-mozplugin-2.29.4-2.fc13.x86_64 from rawhide
totem-nautilus-2.29.4-2.fc13.x86_64 from rawhide
totem-pl-parser-2.29.1-1.fc13.x86_64 from rawhide
It looks like totem-pl-parser depends on libgmime-2.4.so.2, which gets replaced by the new gmime. The rest of the packages depend on libtotem-plparser.so.17, which won't install because of the gmime conflict. Any ideas if the system will boot after an update with --skip-broken?

Thanks,
dd_wizard

[madhavdiwan]

There are lots of ways to get around rpmfusion , or any other dependency issues when trying to upgrade from one Fedora version to another .

What do you mean by when I tried to pre-update totem-pl-parser? Do you actually mean using the "preupgrade" command ?

to get around your dependency issues you can:
( this list is in no particular order or preference )

a) disable the rpmfusion repositories by editing the appropriate files in /etc/yum.repos.d or removing the rpmfusion files .. there are multiple ways to do either action
1) remove the rpmfusion repo rpms
2) edit the rpmfusion repo rpms with a text editor and toggle the "enabled=" variable to 0 in each rpmfusion repo file
b) use yum instead of preupgrade and use the --exclude= option with it , or the --skip-broken option ( or use yumex and do the same graphically )
c) remove the offending rpm from your current install
1) you can remove it and use another program that may be the current programs successor ( hopefully it is in the new Fedora versions repositories)
2) if you have the original copy of the rpm that is causing the conflict, you can remove it and then. after a successful upgrade, try to reinstall it. ( make sure you save it somewhere other than inside of yum caches)

I am sure other users here will have other suggestions ( please feel free to add to the suggestions/options and I will happily post it separately when we have a nicely representative list )

---------- Post added at 06:20 PM CST ---------- Previous post was at 06:15 PM CST ----------

yes the system will boot after using yum with --skip-broken

you are not excluding any packages that will be missed.

And besides that you will keep the old Fedora 12 packages/ apps that are already installed ( so you instead of running the new rawhide gmime.. be using the old fedora12 gmime , etc.)

[marvin_ita]

The problem with totem-pl-parser and gmime is not dependent to RPMfusion repos... I've got a clean F13 rawhide installation and have the same problem.

I just opened a bug (https://bugzilla.redhat.com/show_bug.cgi?id=565286) in Bugzilla.

Mattia

[dd_wizard]

Thanks marvin_ita, you beat me to it. I erased totem-pl-parser which erased the two brasero packages, along with totem and the two totem plugins prior to updating to F13. That way gmime updated ok, and no dependency errors occurred during the update. Today, totem-pl-parser and the related packages installed successfully, so your bug report got it fixed pretty quickly. It's nice to report that F13 is running like a charm on my 2.5 year old Toshiba laptop! :D

dd_wizard