On 01/05/2010 11:45 AM, Anne Wilson wrote:
On Tuesday 05 January 2010 16:50:26 Nicolas Thierry-Mieg wrote:
Anne Wilson wrote:
For some time now, my CentOS box has been skipping the update of exiv2.
Yesterday I decided to do something about it, so I removed gwenview,
digikam, exiv2 and libexiv2. I then reinstalled gwenview and digikam,
which of course pulled in the two exiv2 packages. The version of exiv2
looked surprisingly familiar, but I assumed that the install would pull
in the latest, so I shouldn't worry. This morning more updates were
announced, and I found that once again exiv2 was being skipped.
I have put a diagnostic file onto http://filebin.ca/swaoqf/centos2.txt -
I hope someone here will be able to tell me what is going wrong and what
I can do about it. Thanks
I haven't checked your log file but I'm guessing you have both rpmforge
and epel active...
I do.
digikam is not in rpmforge, I suspect you're getting it from epel along
with the exiv2 dep, which is perhaps a lower version than the rpmforge
exiv2?
The installed version is
exiv2.i386 0.17.1-1.el5.rf
and the update version on offer is
exiv2.i386 0.19-1.el5.rf
As maintain this stack in epel, I suppose I can update to match.
It's just that since I at least make an effort to maintain compatibility
on the epel-side of things by giving notice of ABI changes to rpmforge,
I'd apprecate some recipricol treatment from rpmforge. What can we do
to make this better?
-- Rex
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
