Software Updater in F7 can not resolve dependencies; therefore installs nothing

aero_b · 08-24-2007, 04:55 PM

Hi,

Recent History:
I'm running Fedora 7 and everything seems to be going fine. I did run into trouble last time I let the Software Updater update fglrx: it screwed my graphics up completely to the point that I just uninstalled everything related to fglrx, ati and beryl (using Add/Remove software) and followed the instructions at another forum (click here) from the beginning. Now I've got my Desktop on a cube and even my native resolution works (1440x900, which was hard to get to work with my ATI X1300).

Current Problem:
Following all that fiddling, I am now running into the problem that Software Updater cannot resolve dependencies and therefore does not install anything. This means that the updates are slowly accumulating in that list of Available Updates...

Clues:
Here's what comes from clicking "Details" in the error message:

Code:

Missing Dependency: libdts.so.0()(64bit) is needed by package xine-lib-extras-nonfree
Missing Dependency: libx264.so.54()(64bit) is needed by package ffmpeg-libs
Missing Dependency: libdts.so.0()(64bit) is needed by package vlc
Missing Dependency: libx264.so.54()(64bit) is needed by package vlc
Missing Dependency: libdts.so.0()(64bit) is needed by package ffmpeg-libs

Packages to be installed/updated:
The problem is, "vlc" and "ffmpeg-libs" are not in the list of available updates so I think libdts.so and libx264.so may be dependencies of dependencies or something...

The packages that were in the list the first time this happened are:
* gstreamer-plugins-ugly
* libdca
* vcdimager
* x264
* xvidcore

Help!
I know I wrote a lot but I hope it's enough info and that you'll appreciate how organised it is

. If there were at least a way to figure out which one is screwing it up and to remove it from my "Available Updates" list so that the problem doesn't prevent me from installing other updates, that would be a start.

Thanks!

jay73 · 08-24-2007, 09:12 PM

I remember running into a similar issue some months ago. It turned out that there was a conflict between two repositories (I believe freshRPMs and one of the official ones). When I disabled one of those, the update went just fine.

aero_b · 08-24-2007, 11:05 PM

That did the trick, thanks! I disabled the freshRPMs repository and updates worked.

For other newbs out there, here's what I did:

Code:

$ su-
# cd /etc/yum.repos.d
# vi freshrpms.repo

Then in the text editor, change "Enabled = 1" to "Enabled = 0" (for example, I had to press Insert to be able to change the text, then after editing it press Esc, then ":wq" to give the command to save [w = write] and quit [q = quit]).

That should do it.

(Now to find out if updating messed with my graphics again... I decided not to get the Kernel update just yet to avoid trouble.)

jay73 · 08-24-2007, 11:44 PM

You know that it can be a lot easier to edit files like that? Just do

sudo gedit /etc/yum.repos.d/freshrpms.repo

You may need to set up sudo first, though. In order to do so, run

visudo

and look for the line that says root ALL(ALL) ALL, then create an identical one on the next line but with your username instead of "root".

As for the graphics, this is just what will happen all the time. The thing is that graphics drivers match a specific kernel, so everytime you install a new kernel, you need to remove the old driver and reinstall a new one. On Fedora, that can be quite painless if you use livna to install both the new kernel and the new fglrx driver.

cyberchuck · 09-06-2007, 08:16 AM

I had the same trouble (libdts etc).

I made sure I had the "livna" repository enabled, then:

% yum remove x264 libdca faad2
[ libdca & faad2 were installed as ".fc7" versions ]

% yum install k3b-extras-nonfree
[ ended up grabbing things mostly from Livna ]

Voila!

PTrenholme · 09-06-2007, 09:32 AM

Quote:

Originally Posted by jay73

[snip] As for the graphics, this is just what will happen all the time. The thing is that graphics drivers match a specific kernel, so every time you install a new kernel, you need to remove the old driver and reinstall a new one.[/snip]

He might want to look at the dkms package for automating the verifying and re-building of kernel modules during the boot process. (dkms runs as a service.) You use its configuration file to point it to the source code of the module, and, when the kernel version changes, it automatically recompiles the module for the new (or different) version, and installs it.

Quote:

Originally Posted by jay73

On Fedora, that can be quite painless if you use livna to install both the new kernel and the new fglrx driver.[/snip]

Thats only true if livna has released a version for the kernel he's using. Since he stated that he'd compiled his own kernel from sources, it's unlikely that livna would support it.

slackergeek · 09-29-2007, 12:21 PM

Yes, on Fedora Core 7 it was a YUM conflict, disabling the freshrpms.repo resolved the libdca dependency on my system.