missing location search and geotools

Bug #1505187 reported by Peter Gervai on 2015-10-12
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Undecided
Unassigned
Wily
Undecided
Unassigned

Bug Description

Version: 4:4.12.0-0ubuntu5

Although it's true that I use digikam/wily under debian/sid (pulling up the required ubuntu libs) I still cannot see the package dependency on marble libs, which may result all kinds of geotools missing: location search, map display, location editing etc.

Is it me (then please show me towards the missing(?) libs) or it's really missing from the current build?

Peter Gervai (grin) on 2015-10-12
description: updated
Pedro Neves (nevesdiver) wrote :

Hi Peter:

I'm having the same problem. It seems that there's one library missing (libkgeomap...), but I'm not sure what the exact problem is.
I'm using Kubuntu just because there's no installable Digikam on Debian, but I'd love to go back to Debian Sid.

Can you explain what packages (and from which repositories) you use?

Cheers:

Pedro

Download full text (3.6 KiB)

Hola Pedro,

On Mon, Oct 12, 2015 at 2:53 PM, Pedro Neves <email address hidden> wrote:

> I'm having the same problem. It seems that there's one library missing (libkgeomap...), but I'm not sure what the exact problem is.

My guess is that compile-time deps missing libmarble* (widget, lib,
...) and libkgeomap* so it's not even compiled in.

> I'm using Kubuntu just because there's no installable Digikam on Debian, but I'd love to go back to Debian Sid.
>
> Can you explain what packages (and from which repositories) you use?

It is theoretically not that hard: put this into
/etc/apt/sources.list.d/digicam:

# digikam
deb http://hu.archive.ubuntu.com/ubuntu wily main universe

(And possibly pin it against automatic upgrades to ubuntu; I comment
out after digikam upgrade to make it sure not messing up the system.)

But it's not that simple: you have to select ubuntu digikam, then
check every library it requires whether you need the ubuntu one
(either due to strict dependency or different packaging from debian,
even if the latter should not matter if everything's okay) or the
debian one.

Then you will meet the problem that it's well possible that your
system have packages installed which require conflicting libraries;
either you remove these, or try to carefully up/downgrade to make the
libs not to conflict or you replace them by ubuntu counterparts
temporarily.

For me it was rather simple, I have pulled minimal ubuntu libs but had
to resolve the debian KDE update of all the libs manually, it's been a
fun 30 minutes. ;-)

But as far as I see it's not that simple anymore since kipi-plugins
-0ubuntu5 try to pull up lots of conflicting libraries; I am satisfied
with non-conflicting -0ubuntu3 (or I'm lazy to re-resolve them again),
so I didn't try.

ii digikam-data 4:4.12.0-0ubuntu5
ii kde-runtime 4:15.08.1-1
ii libbaloofiles4 4:4.14.2-2
ii libc6 2.19-18
ii libgcc1 1:5.2.1-15ubuntu1
ii libgphoto2-6 2.5.4-1.1+b2
ii libgphoto2-port12 2.5.7-5
ii libjasper1 1.900.1-debian1-2.4
ii libjpeg8 8d1-2
ii libkdcraw23 4:15.04.2-0ubuntu1
ii libkdecore5 4:4.14.12-2
ii libkdeui5 4:4.14.12-2
ii libkexiv2-11v5 4:15.04.2-0ubuntu4
ii libkface3 4:15.07.90-0ubuntu1
ii libkfile4 4:4.14.12-2
ii libkhtml5 4:4.14.12-2
ii libkio5 4:4.14.12-2
ii libkipi11 4:4.13.3-1
ii libknotifyconfig4 4:4.14.12-2
ii libkparts4 4:4.14.12-2
ii liblcms2-2 2.6-3+b3
ii liblensfun0 0.2.8-2
ii liblqr-1-0 0.4.2-2
ii libopencv-core2.4v5 2.4.9+dfsg-1ubuntu6
ii libopencv-imgproc2.4v5 2.4.9+dfsg-1ubuntu6
ii libpgf6 6.14.12-3
ii libphonon4 4:4.8.0-5
ii libpng12-0 1.2.50-2+b2
ii libqt4-dbus 4:4.8.7+dfsg-1
ii libqt4-sql 4:4.8.7+dfsg-1
ii libqt4-sql-sqlite 4:4.8.7+dfsg-1
ii libqt4-xml 4:4.8.7+dfsg-1
ii libqtcore4 4:4.8.7+dfsg-1
ii libqtgui4 4:4.8.7+dfsg-1
ii libsolid4 ...

Read more...

Pedro Neves (nevesdiver) wrote :

Hi Peter:

Thanks for the info.
I wonder... How hard would it be to compile it from source for Debian?

Any ideas?

Pedro

Achim Bohnet (allee) wrote :

Marble/kgeomap uses in wily qt5/kf5
digikam 4.* is qt4/KDE4

you can mix qt4 with qt5 (plugins), therefore no kgeomap support in digikam 4.* anymore.
As qt4/kde version of marble is no longer maintained it can't be included into a new release.

As soon as digikam 5.* finds it's way into a kubuntu release kgeomap support will return.

I suggest to set the bug to 'won't fix'.

Achim

 #kubuntu-devel:

[23:52:22] <yofel> clivejo: what's the actual problem?
[23:52:51] <clivejo> libkgeomap is looking for marble-config.cmake
[23:53:06] <ahoneybun> I'll be working but g2g for now
[23:53:19] <yofel> oops
[23:53:30] <yofel> I guess nobody removed that. libkgeomap is unbuildable in wily
[23:53:50] <clivejo> nice to know
[23:53:52] <yofel> looks for qt4 marble, and we only ship qt5 marble
...
[02:21:22] <claydoh> what happened to libkgeomap for digikam/kipi in wily?
[02:25:25] <sgclark> no clue
[02:52:54] <claydoh> https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1459443
[02:52:55] <ubottu> Launchpad bug 1459443 in digikam (Ubuntu) "Reenable gpssync plugin in digikam" [High,Triaged]
[02:53:16] <claydoh> but I can't find why it is gone or if it is coming back
[02:54:53] <sgclark> umm well http://osdir.com/ml/ubuntu-bugs/2015-08/msg16295.html
[02:55:14] <sgclark> seems odd
[02:56:15] <sgclark> ahh indeed it is qt4 only
[02:56:26] <sgclark> won't work in wily
...

Peter Gervai (grin) wrote :

Would be neat to reflec in either changelog or readme or wherever. Apart from that yeah, I can relate to it, this is probably a cantfix ;)

Philip Muškovac (yofel) wrote :

As Achim explained, there's nothing we can do about this for wily. Once everything is ported to Qt5 it will come back.

Changed in digikam (Ubuntu Wily):
status: New → Won't Fix
Changed in digikam (Ubuntu):
status: New → Triaged
Peter Gervai (grin) wrote :

PLEASE include it in the changelog or readme. Please use 'marble' or 'location' somewhere in the sentence so grep our best friend could find it. Thanks.

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

Other bug subscribers