On Tuesday 05 January 2010 17:59:31 Nicolas Thierry-Mieg wrote: > OK, here's the situation AFAICT, based on one of my systems where > digikam from epel is installed: > > digikam (digikam-0.9.5-1.el5.x86_64 from epel) requires libkexiv2.so.3 . > ŧhis is provided by the epel libkexiv2-0.1.7-1.el5.x86_64 , which > requires libexiv2.so.4 . > The older rpmforge exiv2-0.17.1-1.el5.rf.x86_64 version provides this, > while the newer exiv2-0.19-1.el5.rf.x86_64 provides libexiv2.so.6 > instead (note the version difference). > > Therefore installing digikam from epel pulls in the older exiv2 from > rpmforge, instead of the newer one (which would not meet the libkexiv2 > dependency, hence libkexiv2 and digikam could not be installed). > > Conclusion: your system is fine as is, if you want digikam you need to > keep the older exiv2. Skipping the exiv2 update is ok. It will only be a > problem if at some point you want to install something that requires the > newer libexiv2.so.6 . > Thanks for the explanation. OK - I've lived with this for quite some time, without any obvious problems, so I'll just go on ignoring the 'skip' warnings.
Anne -- KDE Community Working Group New to KDE Software? - get help from http://userbase.kde.org
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
