file /usr/share/locale/ja/LC_MESSAGES/libkdcraw.mo from install of kde-l10n-Japanese-4.1.3-1.fc10.noarch conflicts with file from package libkdcraw-0.1.4-2.fc9.x86_64
There is no libkdcraw package in F10 repo, in what situation does this error occur?
Upgrade (from F-8, F-9). Looks like we goofed and didn't Obsoletes this anywhere.
Rex you have Obsoletes this in kdegraphics-libs: %if 0%{?obsolete_kde3_kipi} Obsoletes: libkdcraw < 0.2.0, libkexiv2 < 0.4.0, libkipi < 0.2.0 Problem still exist because there is no Provides for libkdcraw and other packages in -libs (only -devel have Obsoletes and Provides for this).
True Obsoletes have been added, but I fail to see how a lack of Provides is a problem here.
Let's assume that libkdcraw is the only installed package on F9 (without digikam, kdegraphics*). Updating to F10 will cause problems, because only kdegraphics-libs Obsoletes libkdcraw, as it isn't installed it will not remove libkdcraw, then if you try to install kde-l10n-Japanese you will get errors like in this bug. If kdegraphics-libs will Provides libkdcraw, during update it will be installed replacing libkdcraw and this bug won't appear.
I think you misunderstand how Obsoletes works (or I do) :) As I understand it, Obsoletes will remove the Obsoleted pkg on upgrade. Provides doesn't play into it.
That said, now that the Obsoletes have been added, * Tue Nov 25 2008 Rex Dieter <rdieter> 4.1.3-3 - respin libkdcraw/libkexiv2 patches - Obsoletes: libkdcraw libkexiv2 libkipi (F10+) I don't see anything else to do here -> closing.
Brainstorming out loud: we could consider making separate libkipi, libkexiv2, libkdcraw (sub)pkgs from kdegraphics, which would also help in such cases.
"As I understand it, Obsoletes will remove the Obsoleted pkg on upgrade." <- You are absolutely right. In this case _if_ user _install_ kdegraphics-libs it will remove libkdcraw package, and everything is fine. Try to imagine what will happen if user _won't_ install kdegraphics-libs, libkdcraw won't be removed. We should care about this too, and such scenario was presented in Comment #5
iirc, Obsoletes are considered in 'yum update' too (and during upgrades).