Yum dependency: beats me!

linmix · 10-09-2005, 02:33 PM

I've been trying to update with yum, but a general updated as per cron job fail because of a dependency. So I tried to solve it. Here's what happened.

Code:

[linmix@linmix ~]$ sudo yum update physfs
Password:
Setting up Update Process
Setting up repositories
updates-released          100% |=========================|  951 B    00:00
base                      100% |=========================| 1.1 kB    00:00
fedora-extras             100% |=========================| 1.1 kB    00:00
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package physfs.i386 0:1.0.1-2.fc4 set to be updated
--> Running transaction check
--> Processing Dependency: libphysfs-1.0.so.0 for package: trigger
--> Finished Dependency Resolution
Error: Missing Dependency: libphysfs-1.0.so.0 is needed by package trigger

trigger? don't see that in the list anywhere.

Code:

[linmix@linmix ~]$ rpm -q trigger
trigger-0.5.1-2.rhfc4.nr

so I have it installed and probably it needs libphysfs-1.0.so.0

Code:

[linmix@linmix ~]$ slocate libphysfs
/usr/lib/libphysfs-1.0.so.0
/usr/lib/libphysfs-1.0.so.0.0.0

I have it on my system. Then why does it complain?

Code:

[linmix@linmix ~]$ sudo yum provides libphysfs
Password:
Searching Packages:
Setting up repositories
updates-released          100% |=========================|  951 B    00:00
base                      100% |=========================| 1.1 kB    00:00
fedora-extras             100% |=========================| 1.1 kB    00:00
Reading repository metadata in from local files
Importing Additional filelist information for packages
filelists.xml.gz          100% |=========================| 2.9 MB    28:05
updates-re: ################################################## 981/981
Added 401 new packages, deleted 498 old in 28.41 seconds
filelists.xml.gz          100% |=========================| 2.3 MB    28:12
fedora-ext: ################################################## 2436/2436
Added 2436 new packages, deleted 0 old in 22.73 seconds


physfs.i386                              1.0.1-2.fc4            fedora-extras
Matched from:
/usr/lib/libphysfs-1.0.so.1.0.0
/usr/lib/libphysfs-1.0.so.1
libphysfs-1.0.so.1


physfs.i386                              1.0.1-2.fc4            fedora-extras
Matched from:
/usr/lib/libphysfs-1.0.so.1.0.0
/usr/lib/libphysfs-1.0.so.1
libphysfs-1.0.so.1


physfs-devel.i386                        1.0.1-2.fc4            fedora-extras
Matched from:
/usr/lib/libphysfs.a
/usr/lib/libphysfs.so


physfs.i386                              1.0.0-1.rhfc4.nr       installed
Matched from:
/usr/lib/libphysfs-1.0.so.0
/usr/lib/libphysfs-1.0.so.0.0.0
libphysfs-1.0.so.0

So the physfs update will install a new version of libphyfs and trigger needs the old version. But there is no update available for trigger and theoretically both libs could be present in the system without causing havoc, right? The only optoin I can think of is blacklisting physfs, but there must be a more intelligent sollution to lkeep my cronjob operational... care to give me a hint?

linmix · 02-21-2006, 05:16 PM

OK, I've come a bit further in my understanding of yum and I think I can explain what happened there. Yum complains of dependencies for 2 reasons:

A needed dendency is not available in the active repos.

This could happen e.g. when you install a package from dag and don't have dries and freshrpms enabled - or fedora-extras. Since these rely on each other to provide dependencies they are not really 'independent' repos but more like a triad
a dependency which needs to be updated to install a new app or update of an already installed app is needed by another app. Updating this dependecy would allow the new app to work, but would break others and so isn't allowed.

In my case the second option applied.