Professional Photo Management with the Power of Open Source

digiKam Software Collection 2.0.0 beta6 is out…

by digiKam

Dear all digiKam fans and users!

digiKam team is proud to announce the 6th digiKam Software Collection 2.0.0 beta release!

With this release, digiKam include a lots of bugs fixes to progress in stability for future production use.

digiKam include since 2.0.0-beta5 a new tool to export on RajCe web service.


digiKam include since 2.0.0-beta4 Group of items feature and MediaWiki export tool.



digiKam include since 2.0.0-beta3 Color Labels and Pick Labels feature to simplify image cataloging operations in your photograph workflow.


Also, digiKam include since 2.0.0-beta2 the Tags Keyboard Shorcuts feature to simplify tagging operations in your photograph workflow.


digiKam software collection 2.0.0 include all Google Summer of Code 2010 projects, as XMP sidecar support, Face Recognition, Image Versioning, and Reverse Geocoding. All this works have been processed during Coding Sprint 2010. You can find a resume of this event at this page.


This beta release is not yet stable. Do not use yet in production. Please report all bugs to KDE bugzilla following indications from this page. The release plan can be seen at this url.


See the list of digiKam file closed with this release into KDE bugzilla.

See the list of Kipi-plugins file closed with this release into KDE bugzilla.

digiKam software collection tarball can be downloaded from SourceForge Repository


Happy digiKam testing…

PPA for digiKam

It would be a great advantage, both for users, testers and you as developers to keep two ppa’s for digiKam:

Stable - only stable releases
Beta - only beta releases

And no other software than what is needed to get it working so that it do not influence anything else in an installation.

This would allow anyone with a *buntu system to keep their preferred ppa in the list and automatically get new versions when they are available. I think this would increase both the user base and tester base and eventually help making digiKam an even better program (if possible!!).

Upstream -> Downstream | Developers -> Distributors

It isn’t responsible, duty or demand for the upstream to maintain repository for users. Developers have own development style than distributors who are in downstream.

The development goes: Upstream -> Downstream
Distributors responsible, duty and demand is to maintain precompiled binary packages for their users. They pull the code from upstream, package it and then place it to repositories for users to easily install and use. When upstream does something, downstreams pulls code changes and compiled new packages and so on.

The ideal ecosystem works that every code development happens in upstream. If upstream does not accept something, then downstream can do it by themselfs but they just cuts off their users (clients etc) from the development in upstream and slows down users.

Ubuntu users are minority in Linux world, not the biggest. They are just users among other distribution users and it is Canonicals job to compile precompiled packages for their users as stable. And then Ubuntu fans who have PPA to compile patched or development version of the software. But every user who use PPA are at their own.

Upstream does not take responsibility what so ever how users wants their packages.

A limited view of the world…

I think you have a very limited view of the world…

PPA’s does not need to be maintained by packagers alone (or fans). As the Ubuntu repositories updates slowly, the PPA’s give users the opportunity to stay closer to the new releases.

A good example is Mozilla. There are PPA’s for stable, beta and alpha packages.

How big marketshare Ubuntu has can probably be talked a lot about. But I think nobody would ever count it as irrelevant. It is probably by far, the biggest distribution out there. And with the various derivatives, it is even bigger.

A PPA made by the developers, or someone approved by them so that you announce that you know that this is a safe PPA is something very valuable and it makes sure users can relax and trust what they get.

It is also valuable to the digiKam project to know that users gets the new releases as soon as possible and can report back bugs immediately.

Fans come and go. A project like this needs stability. And the only way to get stability is for this project to offer packages for the major distributions directly.

Why bother with a website? Why not just keep an ftp server and a mailing list? Why bother with Facebook pages? A website like this with comments, a Facebook group, Twitter - all of this is direct contact with end users. If you really think that devs should not interact with end users, then an ftp server and a mailing list is all you need. But this is not the world we live in now. We now live in a world where direct contact is crucial to any project. You might think that you do not have time or resources to keep a PPA up to date. But just ask around, and I am sure there are people that would like to help. Just keep the control of the PPA inside the project. Don’t let it be under the control of someone else that lets it die if he do not have time anymore. When it is under the control of the digiKam project, you just replace the one that do the work - not the PPA.

Full ACK

Full ACK

Felt like giving a response

Felt like giving a response to this post as I feel like my PPA have become more or less the unofficial PPA for Digikam 2.0 when it comes to Ubuntu.

I have had this request once in a while to break out Digikam to a PPA of its own but the purpose of my PPA is to provide packages for Ubuntu that I anyway make for myself, friends or by request. I get this request for almost every software you find in my PPA from time to time. If you like to use just Digikam from it then just grab that and inactivate the PPA until you want to update it again. I just want all my packages to work as any other user so that’s of course my main goal.

When it comes to Digikam 2.0 beta6 I have had about 800 downloads of it for Ubuntu 11.04 and would say that there is almost as many unique Digikam users of the PPA (most people tend to download the packages one time and have it in apt cache on their computer even if they reinstall the same package). I have had little complain about the packages them self but that is of course no guarantee for the future.

Still, using PPAs can make unwanted effects to a system so it’s better to feel confident enough to know what’s in them and maybe also track records of how it is to use it. Combinations of different PPAs can also make stuff conflict but that usually gives problems with upgrading, updating or installing and apt, aptitude, kpackagekit, synaptic or any other package manager will let you know when that happens before any system breaks (fingers crossed).

If someone want to setup a special purpose digikam PPA they are as alway in the Linux world free to fork/copy Digikam packages in my PPA or make their own and just upload that somewhere. I’m even happy to help out but I will keep doing what I’m doing with mine as long as I feel it’s needed.

Happy Digikaming!

Thank you!

Maybe you should add the link to your ppa :-)

It is great that you keep a PPA for your own stuff, but it would be better to have a dedicated ppa for digiKam for several reasons.

You might for some reason, some day, decide that you do not want to have digiKam there anymore. All the users would then have to go hunting for a new fan that have a PPA. An official PPA would be a lot better. If whoever that maintain it decide to stop doing so, someone else can step in as the official one will not be tied to a fan somewhere in the world.

A dedicated ppa for digiKam alone makes it less likely that people get new version of software they did not plan on upgrading for various reasons. It allows you to turn on a PPA and leave it on. Most users are able to do an add-apt-repository, but sooner or later you forget to turn the ppa off after an update and suddenly you get a lot of updates you did not want.

Understand me right - I love the job you are doing. If I was able to maintain a PPA, I would set up the digiKam PPA myself, but I have no clue how to do it. I am not a programmer.

Compiling beta on OSX 10.6

I haven’t been able to compile the digikam beta since beta-2 under OSX 10.6 with macports, XCode 4, and a Mac Mini 64 bit system. Has anybody elese succeeded in doing this?


I use also a macbook, and i compile digiKam and co like you through macport (at least to resolve dependencies).

I checkout code from digikam Software Compilation :


… And all work fine :



still having problems

As I am still having problems, could you explicitly list the steps you performed for both checking out the code from kde.org and to compile using cmake? I want to make sure I didn’t miss anything here.


I need more info…

when you checkout digiKam SC, run bootstrap.macports and give a trace of cmake results…



I deleted my old repositories and rebuilt from scratch, and everything appears to be working now.

For the record, here is what I did:

git clone kde:digikam-software-compilation
cd digikam-software-compilation
sudo make install

The same happened to me!

And I did exactly that, and it worked! thank you!

What version of libkipi

What version of libkipi should I use for compiling, from Kubuntu 11.04 repositories or from digikam-2.0.0-beta6.tar.bz2? If I remove libikipi8, it also removes Ksnapshot and Gwenview (and digikam)?

Thank you.

none especially..

There no specific version to use, excepted a version > 1.0.

To get whole dependencies of libraries managed by digiKam team, use Software Compilation repository :




You can edit the way google map thing has. It can achieve such things most people want to get personalized. I want to grab this. How does one avail this type free of fee?

Congratulations for getting

Congratulations for getting closer to 2.0

Are there any news on the Windows builds front? I am unfortunately stuck with no functional Linux install on my laptop, and no time to put it together soon :(

try this one…