digikam package is not installable due to depedency in a kde3.5 package no longer available

Bug #262957 reported by Alexia Death
20
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Fix Released
Critical
Jonathan Riddell

Bug Description

Binary package hint: digikam

sudo apt-get install digikam

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  digikam: Depends: kdebase-kio-plugins but it is not installable
E: Broken packages
---
This is prevents digikam being installed. Digikam is important part of many photo interested linux users KDE or not. I have installed digikam 1.0 betas. They are nowhere near sable enough to be used in production.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Just needs that removed as a depend. It should run fine without it even though it won't be able to use the kio slaves the package provides.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

...or not. Several of it's build depends are at KDE 4.1.x now. We'll see how this all pans out.

Revision history for this message
Alexia Death (alexiade) wrote :

Not so simple... Digikam uses kio slaves to show their image thumbnails. Without kio-slaves digikam may run, but you wont get any images. And image manager without display of images is rather useless.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Riddell has fixing it on his todo list, since upstream doesn't want us to switch over to the KDE4 version yet.

Changed in digikam:
status: New → Confirmed
Revision history for this message
Alexia Death (alexiade) wrote :

Great! Will be waiting for the moment digikam is installable again. May take a while tho because this requires kde 3.5 libraries in the system somewhere off the default path. The upside is, when it is solved for digikam it is solved for everything else that for one reason or another is not yet upgradable to 4.1 version.

Changed in digikam:
assignee: nobody → jr
importance: Undecided → Critical
status: Confirmed → In Progress
Revision history for this message
Alexia Death (alexiade) wrote :

At this point digikam is installable again but as predicted, not showing any images without its kio slaves... the same thing happens if digikam is built with a wrong KDE prefix.

Revision history for this message
Mike (mike-prog99) wrote :

Just done an apt-get install digikam and from what I can see its all up and running just fine?

Revision history for this message
Alexia Death (alexiade) wrote :

Looks fixed to me aswell. go my images. YAY!

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Yup, has been fixed.

Changed in digikam:
status: In Progress → Fix Released
Revision history for this message
Alexia Death (alexiade) wrote :

Some of the recent updates have broken it for me again. Trying to use it yesterday, it turned out to be uninstalled and the only way that could have happened was the recent dist-upgrade, and me not taking a close enough look at removed packages list. On install the weirdest thing that was removed was gwenwiew. After it was installed again I was back to the state where digikam runs but shows now images. Typical state for wrong prefix/missing kio slaves.

Revision history for this message
Alexia Death (alexiade) wrote :

The last comment contains a typo in a bad place, sorry. Digikam shows no images. None are listed in albums and no thumbnails shown.

Revision history for this message
Alexia Death (alexiade) wrote :

And now it works again... Sorry for the panic.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.