kipi and libkdcraw updates for development

[José Matos]

When updating in rawhide I get this:

# yum update --skip-broken
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package libkdcraw.i386 0:0.1.4-1.fc9 set to be updated
---> Package kipi-plugins.i386 0:0.1.5-1.fc9 set to be updated
--> Processing Dependency: libkdcraw.so.2 for package: digikam
--> Processing Dependency: libkdcraw.so.2 for package: kphotoalbum
--> Finished Dependency Resolution
digikam-0.9.3-2.fc9.i386 from installed has depsolving problems
--> Missing Dependency: libkdcraw.so.2 is needed by package
digikam-0.9.3-2.fc9.i386 (installed)
kphotoalbum-3.1.0-2.fc9.i386 from installed has depsolving problems
--> Missing Dependency: libkdcraw.so.2 is needed by package
kphotoalbum-3.1.0-2.fc9.i386 (installed)
--> Running transaction check
---> Package libkdcraw.i386 0:0.1.4-1.fc9 set to be updated
--> Processing Dependency: libkdcraw.so.3 for package: kipi-plugins
--> Finished Dependency Resolution
kipi-plugins-0.1.5-1.fc9.i386 from kde-unstable has depsolving problems
--> Missing Dependency: libkdcraw.so.3 is needed by package
kipi-plugins-0.1.5-1.fc9.i386 (kde-unstable)

Packages skipped because of dependency problems:
kipi-plugins-0.1.5-1.fc9.i386 from kde-unstable
libkdcraw-0.1.4-1.fc9.i386 from kde-unstable

Are the other packages waiting for the freeze to be over?

Regards,

[Rex Dieter]

...

Post by José Matos
kipi-plugins-0.1.5-1.fc9.i386 from kde-unstable
libkdcraw-0.1.4-1.fc9.i386 from kde-unstable
Are the other packages waiting for the freeze to be over?

Oops, those slipped into the repo, but shouldn't have. I'll remove them.

long story: new versions that break api/abi. Bad, mm-kay? :)

-- Rex


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[José Matos]

long story: new versions that break api/abi.  Bad, mm-kay? :)

No problem. :-)
I saw your message in fedora-devel (test?) about this issue and I thought
that you were using the unstable repo as a testbed for the new libraries. So
those results seemed natural.

Since no packages were installed life goes on. :-)

-- Rex