[SOLVED] Problem with dependencies when updating.

[Ludwig Van]

Hi! Last night when i was updating fedora via yumex i got the following message.

14:06:59 : YUM: Yum Version : 3.4.3
14:06:59 : YUM: Loaded plugins: auto-update-debuginfo, langpacks, post-transaction-actions,
14:07:00 : Getting available updates
14:07:07 : 8 packages returned
14:07:07 : Getting available obsoletes
14:07:07 : 0 packages returned
14:07:07 : Adding Packages to view
14:07:07 : Added 8 Packages to view
14:08:18 : YUM: --> Running transaction check
14:08:18 : YUM: ---> Package firefox.i686 0:9.0.1-1.fc16 will be updated
14:08:18 : YUM: ---> Package firefox.i686 0:10.0-1.fc16 will be an update
14:08:18 : YUM: ---> Package gpm-libs.i686 0:1.20.6-18.fc16 will be updated
14:08:18 : YUM: ---> Package gpm-libs.i686 0:1.20.6-21.fc16 will be an update
14:08:19 : YUM: ---> Package gstreamer-plugins-bad-free.i686 0:0.10.22-2.fc16.1 will be updated
14:08:19 : YUM: ---> Package gstreamer-plugins-bad-free.i686 0:0.10.22-2.fc16.2 will be an update
14:08:19 : YUM: ---> Package libvpx.i686 0:0.9.7.1-1.fc16 will be updated
14:08:19 : YUM: --> Processing Dependency: libvpx.so.0 for package: ffmpeg-libs-0.8.8-1.fc16.i686
14:08:19 : YUM: ---> Package libvpx.i686 0:1.0.0-1.fc16 will be an update
14:08:19 : YUM: ---> Package selinux-policy.noarch 0:3.10.0-74.fc16 will be updated
14:08:20 : YUM: ---> Package selinux-policy.noarch 0:3.10.0-75.fc16 will be an update
14:08:20 : YUM: ---> Package selinux-policy-targeted.noarch 0:3.10.0-74.fc16 will be updated
14:08:20 : YUM: ---> Package selinux-policy-targeted.noarch 0:3.10.0-75.fc16 will be an update
14:08:20 : YUM: ---> Package xulrunner.i686 0:9.0.1-1.fc16 will be updated
14:08:20 : YUM: ---> Package xulrunner.i686 0:10.0-1.fc16 will be an update
14:08:20 : YUM: ---> Package ypbind.i686 3:1.33-9.fc16 will be updated
14:08:20 : YUM: ---> Package ypbind.i686 3:1.33-11.fc16 will be an update
14:08:25 : YUM: --> Finished Dependency Resolution
14:09:01 : ERROR: Dependency resolving completed with errors
14:09:01 : ERROR: Package: ffmpeg-libs-0.8.8-1.fc16.i686 (@rpmfusion-free-updates)
Requires: libvpx.so.0
Removing: libvpx-0.9.7.1-1.fc16.i686 (@koji-override-0/$releasever)
libvpx.so.0
Updated By: libvpx-1.0.0-1.fc16.i686 (updates)
Not found

I tried to select each package by itself but the message still popped up..
What should I do?

[leigh123linux]

Try

su
yum --enablerepo rpmfusion-free-updates-testing update

[Davarish]

Ι have the exact same problem. leighs suggestion didn't help unfortunately. I tried some other things like rpm -Va --nofiles --nodigest and --skip-broken but nothing seems to change the situation. Of course I did yum clean all after every command but still nothing. The strange thing is that yesterday and today I did a lot of updates. It just can't update those 6-7 packages left giving this error about livpx. Don't have the slightest idea what might cause the problem. Any help would be greatly appreciated. Thanks!

[lightman47]

fwiw - suspect a bug in the updates. Usually when this happens I wait several days and try again. In the past, I'd tried all the tricks to make the update go, only to find I'd hosed my system.

[Davarish]

Here is a solution a found. Removing the package libvacodec52. Now the only thing that is left, is to find out why I had this package installed. In other words, what app needs it to work properly. So far so good though

[smr54]

In my case, Leigh's solution isn't working and I don't have libvacodec52 installed. Reckon I'll have to wait and hope it gets fixed.

[Davarish]

sorry for the typo man! It is libavcodec not libvacodec. check it out again

[leigh123linux]

Originally Posted by smr54

In my case, Leigh's solution isn't working and I don't have libvacodec52 installed. Reckon I'll have to wait and hope it gets fixed.

I believe I've posted the solution to the error in post #1

[root@main_pc leigh]# yum --enablerepo rpmfusion-free-updates-testing list ffmpeg-libs
Loaded plugins: langpacks, presto, refresh-packagekit, remove-with-leaves, show-leaves
Installed Packages
ffmpeg-libs.x86_64                                0.8.9-1.fc16                                @rpmfusion-free-updates-testing
Available Packages
ffmpeg-libs.i686                                  0.8.8-1.fc16                                rpmfusion-free-updates         
[root@main_pc leigh]#

[root@main_pc leigh]# rpm -q --requires ffmpeg-libs |grep vpx
libvpx.so.1()(64bit)  
[root@main_pc leigh]#

@ Davarish

Have you checked to see if you repos are up to date as your solution is gibberish and makes no sense.

[root@main_pc leigh]# yum provides /usr/lib64/libavcodec.so.53
Loaded plugins: langpacks, presto, refresh-packagekit, remove-with-leaves, show-leaves
ffmpeg-libs-0.8.5-2.fc16.x86_64 : Libraries for ffmpeg
Repo        : rpmfusion-free
Matched from:
Filename    : /usr/lib64/libavcodec.so.53



ffmpeg-libs-0.8.8-1.fc16.x86_64 : Libraries for ffmpeg
Repo        : rpmfusion-free-updates
Matched from:
Filename    : /usr/lib64/libavcodec.so.53



ffmpeg-libs-0.8.9-1.fc16.x86_64 : Libraries for ffmpeg
Repo        : @rpmfusion-free-updates-testing
Matched from:
Filename    : /usr/lib64/libavcodec.so.53



[root@main_pc leigh]#

[root@main_pc leigh]# yum list *\avcodec\*
Loaded plugins: langpacks, presto, refresh-packagekit, remove-with-leaves, show-leaves
Available Packages
xmms2-avcodec.x86_64                                        0.7-3.fc16                                        rpmfusion-free
[root@main_pc leigh]#

[Davarish]

I believe they are! How can I check that? I use testing repos and get updates from the main sarvers

[LongTimeDabbler]

1. For some reason when I tried Leigh's solution from the command line the already installed Firefox 9.0.x complained about dependencies. However, when I did the exact equivalent from the yumex GUI (and checked the free-updates-testing repo) all went fine.
2. Going forward should the free-updates-testing repo remain enabled - it was not enabled for me prior to this - or was this a one time only sort of thing?

[DBelton]

Leigh,

Davarish is correct. IF he installed libavcodec52 from atrpms, then it does indeed cause a conflict and needs to be removed before the update will work.

[Ludwig Van]

Problem sovled for me with leigh's solution. Shall I uncheck the repo now? (testing repos are a bit unstable right?) and shall I mark this topic as solved?