Exiv2 library missing???

[Daniel Bauer-2]

On Tuesday 05 December 2006 19:27, Thorsten Schnebeck wrote:

> > > Is it right that
> > > /home/digi/digikamSVN//bin/exiv2-config
> > > is the correct version?
> >
> > I guess, at least the executable file exiv2 is there...
> >
> > > /home/digi/digikamSVN//bin/exiv2-config --version
> > > tells you what?
> >
> > 0.11 !!! (without the !!!)
> > how comes?
>
> So, I took you script and used that to update my own exiv2-package.
> That works without problems. So you _must_ have an old version?
> I checked the SVN trunk - there is no error in versioning.
>
> Did you miss a "make install"?
> try a
> cd exiv2-svn
> make uninstall
> cd ..
> rm -r exiv2-svn
>
> and start your exiv2 build script again
>
> HTH
>
>   Thorsten

hm, yes I *do* have exiv2 0.11 installed, but in /opt/kde3, and the export
commands Fabien gave me should point to the exiv2 in my special svn
directory, as much as I understand. I think the "install in home directory"
should be "secure" in a meaning that it can be installed there independent of
other installs (could be other programs depend on an older version, no?).

When I first type those export commands (sorry, I didn't think about that
before), then --version gives 0.12:

digi@venus:~/digikamSVN/bin> export DIGIKAMDEST=/home/digi/digikamSVN
digi@venus:~/digikamSVN/bin> export KDEDIRS=$DIGIKAMDEST:/usr ; export
LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ; export
LDPATH=$DIGIKAMDEST/lib:$LDPATH
digi@venus:~/digikamSVN/bin> export UNSERMAKE=no
digi@venus:~/digikamSVN/bin> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig
digi@venus:~/digikamSVN/bin> export PATH=$DIGIKAMDEST/bin:$PATH
digi@venus:~/digikamSVN/bin> exiv2-config --version
0.12

So the script worked correctly here, too, so far, and it's just that the
second compile somehow doesn't look where it should.

Well, I'll see tomorrow, if there are news from Fabien, too.

Of course I can de-install my exiv2 from /opt/kde and then install the 0.12
version there, but even if this work-around works it wouldn't solve the
underlaying problem (in my opinion), because then all the exif2 svn up stuff
in the test directory would be useless, because it would always use
the /opt/kde3 install instead of the updated svn version. (I would prefer to
have a "testing environment" without touching installed and running apps, and
I guess quite a lot people would like this = "enjoy testing at no
risk :-)" ).

pfff, my english is getting even worse now, so I'll give the compiler and
myself a break for now...

Thanks, and till tomorrow...

Daniel
--
Daniel Bauer photographer Basel Switzerland
professional photography: http://www.daniel-bauer.com
Madagascar special: http://www.sanic.ch
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

So I've got some good and some bad news:

the good news:

I've uninstalled exiv2 0.11 from /opt/kde3, then again deleted everything in home/digi/... and let the scripts run again - now the compile works fine.

the bad news:

now of course ufraw doesn't work anymore, because it needs exiv2 in /opt/kde3. It's a program I use very often. So I reinstalled exiv2 0.11 in /opt/kde3 again...

Digikam svn still starts (I havn't made further tests yet). But (I guess) with the next compile after svn up of digikam the same problems will occour again.

the question:

How can we make it possible that there are two exiv2 installed at the same time without disturbing each other?

I thought of installing stable exiv2 0.12 in /opt/kde3 and recompile ufraw if necessary, but then for what reason have the exiv2 svn version in the home-directory if it uses the one in /opt/kde3 anyway?

Daniel

--

Daniel Bauer photographer Basel Switzerland

professional photography: http://www.daniel-bauer.com

Madagascar special: http://www.sanic.ch

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Wednesday 06 December 2006 12:18,  Fabien wrote:

> Hello,
>
> I saw that it works if you remove the exiv2-0.11 in /opt
> Now that you reinstalled it, we can continue
> I hope you didn't remove the files used for compilation.
>
> So, here are the steps :
>
> 1) use my run_configure.sh.txt script to just start the configure
> (instead of compile_digikam).
>
> You should still get the same errors (or it would make no sense if you
> have again the same configuration)

yes, output is here:
http://www.daniel-bauer.com/test/run_configure.out.txt
>
> 2) if you get the errors, try to replace your graphics/configure by
> the configure.txt I sent you.
> This will output some debugs.

i hope I understood correctly:
- renamed graphics/configure to ... .old
- copied your configure.txt into graphics folder, renamed it to configure,
made it executable
- run run_configure.sh again

output is here:
http://www.daniel-bauer.com/test/run_configure_Fab.out.txt
>
> 3) reports all results to the list

is this what you wanted?
>
> We'll find the solution :)
>
> Thanks.
>
> --
> Fabien

thank *you*

Daniel
--
Daniel Bauer photographer Basel Switzerland
professional photography: http://www.daniel-bauer.com
Madagascar special: http://www.sanic.ch
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

> output is here:
> http://www.daniel-bauer.com/test/run_configure_Fab.out.txt

Hi, hi, hi :-)

> Will find package 'exiv2' in file '/opt/kde3/lib/pkgconfig/exiv2.pc'
> Scanning directory '/home/digi/digikamSVN/lib/pkgconfig'
> [..]
> File 'exiv2.pc' ignored, we already know about package 'exiv2'

THAT is your problem. Now, what is the solution?

Bye

  Thorsten




_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabien-5]

Daniel Bauer wrote:

> On Wednesday 06 December 2006 12:18,  Fabien wrote:
>>2) if you get the errors, try to replace your graphics/configure by
>>the configure.txt I sent you.
>>This will output some debugs.
>
>
> i hope I understood correctly:
> - renamed graphics/configure to ... .old
> - copied your configure.txt into graphics folder, renamed it to configure,
> made it executable
> - run run_configure.sh again
>
> output is here:
> http://www.daniel-bauer.com/test/run_configure_Fab.out.txt

Ok, nice.

So, pkg-config scan first /opt/kde3/lib/pkgconfig *before* the directory
we set with PKG_CONFIG_PATH.
But, when you run it manually, it looks for it ($PKG_CONFIG_PATH) first.
Something weird here.

We can see that it tries to scan twice the directory
/home/digi/digikamSVN/lib/pkgconfig

Any idea in this room ?

>>3) reports all results to the list
>
> is this what you wanted?
Yes, exactly !

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Am Mittwoch 06 Dezember 2006 16:41 schrieb Fabien:

> So, pkg-config scan first /opt/kde3/lib/pkgconfig *before* the directory
> we set with PKG_CONFIG_PATH.
> But, when you run it manually, it looks for it ($PKG_CONFIG_PATH) first.
> Something weird here.
>
> We can see that it tries to scan twice the directory
> /home/digi/digikamSVN/lib/pkgconfig
>
> Any idea in this room ?

From pkg-config manual:

"The package name specified on the pkg-config command line is defined to be
the name of the metadata file, minus the .pc extension. If a  library  can
install  multiple  versions simultaneously, it must give each version its own
name"

but also:

"PKG_CONFIG_PATH
A colon-separated (on Windows, semicolon-separated) list of directories to
search for  .pc  files.   The  default  directory  will  always  be
searched  after  searching the path; the default is
libdir/pkgconfig:datadir/pkgconfig where libdir is the libdir where pkg-config
and datadir is the datadir where pkg-config was installed.


Cause we got this in the output:
"Adding virtual 'pkg-config' package to list of known packages
Scanning directory '/opt/kde3/lib/pkgconfig'"

there must be somewhere a redefinition of PKG_CONFIG_PATH

If you test something like
PKG_CONFIG_PATH=/test pkg-config --list-all --debug
you get
"Adding virtual 'pkg-config' package to list of known packages
Scanning directory '/test'"
like Fabian has already said.

I do not understand these lines:
checking for exiv2-config... /home/digi/digikamSVN/bin/exiv2-config
checking for exiv2 >= 0.12... Fab100 >>>Requested 'exiv2 >= 0.12' but version
of exiv2 is 0.11

What is the content of  /home/digi/digikamSVN/bin/exiv2-config?

Bye

  Thorsten

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Wednesday 06 December 2006 18:12, Thorsten Schnebeck wrote:
> [...]
>
> What is the content of  /home/digi/digikamSVN/bin/exiv2-config?

this: http://www.daniel-bauer.com/test/exiv2-config.txt

tschüss

Daniel
>
> Bye
>
>   Thorsten
>


--
Daniel Bauer photographer Basel Switzerland
professional photography: http://www.daniel-bauer.com
Madagascar special: http://www.sanic.ch
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Am Mittwoch 06 Dezember 2006 18:19 schrieb Daniel Bauer:
> On Wednesday 06 December 2006 18:12, Thorsten Schnebeck wrote:
> > [...]
> >
> > What is the content of  /home/digi/digikamSVN/bin/exiv2-config?
>
> this: http://www.daniel-bauer.com/test/exiv2-config.txt

ok, this is 0.12 and what I expected.
So I looked into the check of ./configure

first there is a test for exiv2-config this results to:
"checking for exiv2-config... /home/digi/digikamSVN/bin/exiv2-config"

This is the correct version. To help configure you could also use the
env-variable $EXIV2_CONFIG but its not necessary.

But now ./configure does not make anything useful with exiv2-config (like
checking the version). No, instead it uses now pkg-config to check the
version of exiv2.

That check results to
"checking for exiv2 >= 0.12... no"

Question stays what overwrites your PKG_CONFIG_PATH?

[search mode]
#------------------------------------------------------------------
# KIPI support (KDE Image Plugin Interface)
#------------------------------------------------------------------

if test "$PKGCONFIGFOUND" = "yes" ; then
   # check for libkipi
   have_libkipi=no

   PKG_CONFIG_PATH="$prefix/lib${kdelibsuff}/pkgconfig:$PKG_CONFIG_PATH"
   if test "$prefix" != "$kde_libs_prefix"; then
       PKG_CONFIG_PATH="$kde_libs_prefix/lib${kdelibsuff}/pkgconfig:
$PKG_CONFIG_PATH"
   fi
   export PKG_CONFIG_PATH

ups - thats bitter! kipi check is before exiv2 test. THAT kills your global
enviroment (and I think this is bad style and a BUG)

With current configure checks you can only use ONE global exiv2 lib.

Can you try this hack:
Please change these lines of your digikam build script from

make -f Makefile.cvs
./configure --prefix=$DIGIKAMDEST --with-extra-includes=$DIGIKAMDEST/include --with-extra-libs=$DIGIKAMDEST/lib
make -j 4

into:

make -f Makefile.cvs
PKGCONFIGFOUND="no" ./configure --prefix=$DIGIKAMDEST --with-extra-includes=$DIGIKAMDEST/include --with-extra-libs=$DIGIKAMDEST/lib
make -j 4

and tell us what configure now tells about the exiv2 check.

Bye

  Thorsten

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Wednesday 06 December 2006 23:06, Thorsten Schnebeck wrote:

> Am Mittwoch 06 Dezember 2006 18:19 schrieb Daniel Bauer:
> > On Wednesday 06 December 2006 18:12, Thorsten Schnebeck wrote:
> > > [...]
> > >
> > > What is the content of  /home/digi/digikamSVN/bin/exiv2-config?
> >
> > this: http://www.daniel-bauer.com/test/exiv2-config.txt
>
> ok, this is 0.12 and what I expected.
> So I looked into the check of ./configure
>
> first there is a test for exiv2-config this results to:
> "checking for exiv2-config... /home/digi/digikamSVN/bin/exiv2-config"
>
> This is the correct version. To help configure you could also use the
> env-variable $EXIV2_CONFIG but its not necessary.
>
> But now ./configure does not make anything useful with exiv2-config (like
> checking the version). No, instead it uses now pkg-config to check the
> version of exiv2.
>
> That check results to
> "checking for exiv2 >= 0.12... no"
>
> Question stays what overwrites your PKG_CONFIG_PATH?
>
> [search mode]
> #------------------------------------------------------------------
> # KIPI support (KDE Image Plugin Interface)
> #------------------------------------------------------------------
>
> if test "$PKGCONFIGFOUND" = "yes" ; then
>    # check for libkipi
>    have_libkipi=no
>
>    PKG_CONFIG_PATH="$prefix/lib${kdelibsuff}/pkgconfig:$PKG_CONFIG_PATH"
>    if test "$prefix" != "$kde_libs_prefix"; then
>        PKG_CONFIG_PATH="$kde_libs_prefix/lib${kdelibsuff}/pkgconfig:
> $PKG_CONFIG_PATH"
>    fi
>    export PKG_CONFIG_PATH
>
> ups - thats bitter! kipi check is before exiv2 test. THAT kills your global
> enviroment (and I think this is bad style and a BUG)
>
> With current configure checks you can only use ONE global exiv2 lib.
>
> Can you try this hack:
> Please change these lines of your digikam build script from
>
> make -f Makefile.cvs
> ./configure --prefix=$DIGIKAMDEST
> --with-extra-includes=$DIGIKAMDEST/include
> --with-extra-libs=$DIGIKAMDEST/lib make -j 4
>
> into:
>
> make -f Makefile.cvs
> PKGCONFIGFOUND="no" ./configure --prefix=$DIGIKAMDEST
> --with-extra-includes=$DIGIKAMDEST/include
> --with-extra-libs=$DIGIKAMDEST/lib make -j 4
>
> and tell us what configure now tells about the exiv2 check.
>
> Bye
>
>   Thorsten
>

Hi, good morning :-)

using PKGCONFIGFOUND="no" makes configure complain about other missing parts:

config.status: executing depfiles commands

-- digiKam configure results -------------------
-- sqlite3 found.................. NO

digiKam needs sqlite3. You need to install sqlite3 3.x, e.g. from
http://www.sqlite.org

-- libgphoto2 found............... YES
-- libkipi found.................. NO

digiKam needs libkipi. You need to install libkipi first
libkipi website is at http://extragear.kde.org/apps/kipi

-- libtiff found.................. YES
-- libpng found................... YES
-- lcms found..................... YES
-- Exiv2 library found............ YES
------------------------------------------------

-- digiKamImagePlugins configure results --------
-- digiKam found.................. YES
-------------------------------------------------

Now that it finds Exiv2 it doesn't find sqlite and libkipi anymore...
I guess, the above is the part of the output you're interested in, but the
complete output is here:
http://www.daniel-bauer.com/test/compile_digikam.Thorsten.out.txt

btw.:
just to be sure I havn't lost sqlite/kipi somewhere, I run the script again
after removing PKGCONFIGFOUND="no" again - and then sqlite/kipi is found, but
Exiv2 not. So I guess you are on the right way, Thorsten, but the command
must somehow be refined to affect the Exiv2 stuff only...

regards

Daniel
--
Daniel Bauer photographer Basel Switzerland
professional photography: http://www.daniel-bauer.com
Madagascar special: http://www.sanic.ch
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

On Thursday, December 7, 2006 11:11:23 AM Daniel Bauer wrote:
> On Wednesday 06 December 2006 23:06, Thorsten Schnebeck wrote:

> > make -f Makefile.cvs
> > PKGCONFIGFOUND="no" ./configure --prefix=$DIGIKAMDEST
> > --with-extra-includes=$DIGIKAMDEST/include
> > --with-extra-libs=$DIGIKAMDEST/lib make -j 4
> >
> > and tell us what configure now tells about the exiv2 check.
> >
> > Bye
> >
> >   Thorsten
>
> Hi, good morning :-)

Hi, hmm more about noon ;-)
>
> using PKGCONFIGFOUND="no" makes configure complain about other missing
> parts:

yes, of course

> -- Exiv2 library found............ YES
> Now that it finds Exiv2 it doesn't find sqlite and libkipi anymore...

I want only a simple test if my analyse fits on your system - and this seems
to be true.

You have to options:
1) Try to convince the kipi-devels that the current kipi configure-checks is
bad style
2) Use a global exiv2 in e.g. /usr/lib and exiv2-svn in kde-prefix area

Bye

  Thorsten

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabien-5]

Hi,

Thorsten Schnebeck wrote:
> Am Mittwoch 06 Dezember 2006 18:19 schrieb Daniel Bauer:

 > [...]

> Question stays what overwrites your PKG_CONFIG_PATH?
>
> [search mode]
> #------------------------------------------------------------------
> # KIPI support (KDE Image Plugin Interface)
> #------------------------------------------------------------------
>
> if test "$PKGCONFIGFOUND" = "yes" ; then
>    # check for libkipi
>    have_libkipi=no
>
>    PKG_CONFIG_PATH="$prefix/lib${kdelibsuff}/pkgconfig:$PKG_CONFIG_PATH"
>    if test "$prefix" != "$kde_libs_prefix"; then
>        PKG_CONFIG_PATH="$kde_libs_prefix/lib${kdelibsuff}/pkgconfig:
> $PKG_CONFIG_PATH"
>    fi
>    export PKG_CONFIG_PATH
>
> ups - thats bitter! kipi check is before exiv2 test. THAT kills your global
> enviroment (and I think this is bad style and a BUG)

Well done Thorsten, I missed this part...

This part is added because there's a check for KIPI that uses
KDE_PKG_CHECK_MODULES.

It's defined there :
<http://websvn.kde.org/branches/KDE/3.5/kde-common/admin/acinclude.m4.in?rev=584244&view=markup>

I wonder why they don't put the original $PKG_CONFIG_PATH first, before
adding the $kde... stuff.


If I replace KDE_PKG_CHECK_MODULES by PKG_CHECK_MODULES, it will remove
the PKG_CONFIG_PATH. This is the diff between both configure :

<
<  PKG_CONFIG_PATH="$prefix/lib${kdelibsuff}/pkgconfig:$PKG_CONFIG_PATH"
<  if test "$prefix" != "$kde_libs_prefix"; then
<
PKG_CONFIG_PATH="$kde_libs_prefix/lib${kdelibsuff}/pkgconfig:$PKG_CONFIG_PATH"
<  fi
<  export PKG_CONFIG_PATH
<


so, it would be ok... But I don't know if there can be some side effects
about that.

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabien-5]

Hi,

Thorsten Schnebeck wrote:

> On Thursday, December 7, 2006 11:11:23 AM Daniel Bauer wrote:
>
>>using PKGCONFIGFOUND="no" makes configure complain about other missing
>>parts:
>
>
> yes, of course
>
>>-- Exiv2 library found............ YES
>>Now that it finds Exiv2 it doesn't find sqlite and libkipi anymore...
>
>
> I want only a simple test if my analyse fits on your system - and this seems
> to be true.
>
> You have to options:
> 1) Try to convince the kipi-devels that the current kipi configure-checks is
> bad style

I'm not sure they are wrong :) Maybe KDE_PKG_CHECK_MODULES could be
replaced by PKG_CHECK_MODULES in graphics/digikam/configure.in.in
<http://websvn.kde.org/trunk/extragear/graphics/digikam/configure.in.in?rev=609246&view=markup>

But, it could be better to change the order of the different elements
that compose PKG_CONFIG_PATH (see my previous email).
The problem is that it's not part of digikam, but part of KDE :)

Daniel, there's also a simple local solution :
I guess you don't need to have 2 developpment headers for exiv2 at the
same time. So you could just remove the file
/opt/kde3/lib/pkgconfig/exiv2.pc (if it's not part of a package, or
maybe remove the exiv2-devel package if it exists).

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

On Thursday, December 7, 2006 12:54:47 PM Fabien wrote:

> Hi,
>
> Thorsten Schnebeck wrote:
> > On Thursday, December 7, 2006 11:11:23 AM Daniel Bauer wrote:
> >>using PKGCONFIGFOUND="no" makes configure complain about other missing
> >>parts:
> >
> > yes, of course
> >
> >>-- Exiv2 library found............ YES
> >>Now that it finds Exiv2 it doesn't find sqlite and libkipi anymore...
> >
> > I want only a simple test if my analyse fits on your system - and this
> > seems to be true.
> >
> > You have to options:
> > 1) Try to convince the kipi-devels that the current kipi configure-checks
> > is bad style
>
> I'm not sure they are wrong :) Maybe KDE_PKG_CHECK_MODULES could be
> replaced by PKG_CHECK_MODULES in graphics/digikam/configure.in.in
> <http://websvn.kde.org/trunk/extragear/graphics/digikam/configure.in.in?rev
>=609246&view=markup>

I dont understand why digikam uses pgk-config at all when it first check for
exiv2-config. So digikam could simply use exiv2-config --version for the
version check.

Bye

  Thorsten

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Thursday 07 December 2006 12:54, Fabien wrote:
> [..]
> Daniel, there's also a simple local solution :
> I guess you don't need to have 2 developpment headers for exiv2 at the
> same time. So you could just remove the file
> /opt/kde3/lib/pkgconfig/exiv2.pc (if it's not part of a package, or
> maybe remove the exiv2-devel package if it exists).

Hi Fabien,

this works.

I've just tested compile with installed exiv2 0.11 in /opt and  
renamed /opt/kde3/lib/pkgconfig/exiv2.pc to something else. Compile works,
digikam starts, ufraw still works, too... So everything is fine for me at the
moment. I didn't understand the rest of this thread, but I guess it wasn't
addresse to me anyway :-)

I guess  /opt/kde3/lib/pkgconfig/exiv2.pc will be re-installed if I ever
compile a new stable exiv2 into /opt, or maybe I might need it, when
compiling a new version of ufraw. So, I hope I will think about this then...

Thanks for your help!
If you need me to test something else in this matter, just let me know what
you want me to do.

Daniel
--
Daniel Bauer photographer Basel Switzerland
professional photography: http://www.daniel-bauer.com
Madagascar special: http://www.sanic.ch
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabien-5]

Hi,

Daniel Bauer wrote:
> On Thursday 07 December 2006 12:54, Fabien wrote:
>
>>[..]
>>Daniel, there's also a simple local solution :
>>I guess you don't need to have 2 developpment headers for exiv2 at the
>>same time. So you could just remove the file
>>/opt/kde3/lib/pkgconfig/exiv2.pc (if it's not part of a package, or
>>maybe remove the exiv2-devel package if it exists).

> this works.

Ok, fine !

> I've just tested compile with installed exiv2 0.11 in /opt and  
> renamed /opt/kde3/lib/pkgconfig/exiv2.pc to something else. Compile works,
> digikam starts, ufraw still works, too... So everything is fine for me at the
> moment. I didn't understand the rest of this thread, but I guess it wasn't
> addresse to me anyway :-)
:)

> I guess  /opt/kde3/lib/pkgconfig/exiv2.pc will be re-installed if I ever
> compile a new stable exiv2 into /opt, or maybe I might need it, when
> compiling a new version of ufraw. So, I hope I will think about this then...

I guess ufraw is/will be able to use exiv2 0.12 :)

> Thanks for your help!
> If you need me to test something else in this matter, just let me know what
> you want me to do.
Ok, thanks !

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users