digiKam Software Collection 3.0.0 beta1 is out...

[Gilles Caulier-4]

Dear all digiKam fans and users!

The digiKam development team is happy to release new digiKam Software
Collection 3.0.0 beta1.

For more details, see announcement on digikam.org:

http://www.digikam.org/node/665

This version is only for testing purpose. Do not use yet in production.

Thanks in advance for your reports.

Gilles Caulier
digiKam project
http://www.digikam.org
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[alekcejk]

Hi,

Building Digikam SC 3.0.0 beta1 for testing in
Fedora Rawhide problematic because of required
libkipi version 2.0.0.

libkipi 2.0.0 will be released with KDE 4.10?

In Fedora libkipi built from separate tarballs
released with KDE SC but libkipi in current KDE
(4.9.1) release is 1.6.0.

There are more than two months before KDE 4.10 beta1
release, so how libkipi 2.0.0 can be built now?

The possible way is to built libkipi package from
digikam-3.0.0-beta1 sources but there are two questions:

1. Is there any incompatible changes in libkipi 2.0.0
with applications from KDE SC 4.9.x?

2. What package version should be used should be used?
Assume that with KDE 4.10 beta1 will be released
libkipi-4.9.50 tarball, so for now can we use version
for example libkipi-4.9.40 version?. It would be nice
to have such separate libkipi-4.9.40 tarball in
directory with digikam-3.0.0-beta1 release.


Gilles Caulier wrote:

> Dear all digiKam fans and users!
>
> The digiKam development team is happy to release new digiKam Software
> Collection 3.0.0 beta1.
>
> For more details, see announcement on digikam.org:
>
> http://www.digikam.org/node/665
>
> This version is only for testing purpose. Do not use yet in production.
>
> Thanks in advance for your reports.
>
> Gilles Caulier
> digiKam project
> http://www.digikam.org

--
Alexey Kurov <[hidden email]>

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

[Gilles Caulier-4]

libkipi 2.0 is include with digiKam SC. You just need to use right
cmake flag to use local source code.

https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/entry/README#L83

At install, libkipi 2.0 header are not installed. Only binary files.
There is no conflict possible with your distro version. More than on
version of shared can be installed on the system

Gilles Caulier

2012/9/19  <[hidden email]>:

> Hi,
>
> Building Digikam SC 3.0.0 beta1 for testing in
> Fedora Rawhide problematic because of required
> libkipi version 2.0.0.
>
> libkipi 2.0.0 will be released with KDE 4.10?
>
> In Fedora libkipi built from separate tarballs
> released with KDE SC but libkipi in current KDE
> (4.9.1) release is 1.6.0.
>
> There are more than two months before KDE 4.10 beta1
> release, so how libkipi 2.0.0 can be built now?
>
> The possible way is to built libkipi package from
> digikam-3.0.0-beta1 sources but there are two questions:
>
> 1. Is there any incompatible changes in libkipi 2.0.0
> with applications from KDE SC 4.9.x?
>
> 2. What package version should be used should be used?
> Assume that with KDE 4.10 beta1 will be released
> libkipi-4.9.50 tarball, so for now can we use version
> for example libkipi-4.9.40 version?. It would be nice
> to have such separate libkipi-4.9.40 tarball in
> directory with digikam-3.0.0-beta1 release.
>
>
> Gilles Caulier wrote:
>
>> Dear all digiKam fans and users!
>>
>> The digiKam development team is happy to release new digiKam Software
>> Collection 3.0.0 beta1.
>>
>> For more details, see announcement on digikam.org:
>>
>> http://www.digikam.org/node/665
>>
>> This version is only for testing purpose. Do not use yet in production.
>>
>> Thanks in advance for your reports.
>>
>> Gilles Caulier
>> digiKam project
>> http://www.digikam.org
> --
> Alexey Kurov <[hidden email]>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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

[Gilles Caulier-4]

2012/9/19  <[hidden email]>:
> Hi,
>
> Building Digikam SC 3.0.0 beta1 for testing in
> Fedora Rawhide problematic because of required
> libkipi version 2.0.0.
>
> libkipi 2.0.0 will be released with KDE 4.10?

yes.

>
> In Fedora libkipi built from separate tarballs
> released with KDE SC but libkipi in current KDE
> (4.9.1) release is 1.6.0.
>
> There are more than two months before KDE 4.10 beta1
> release, so how libkipi 2.0.0 can be built now?
>
> The possible way is to built libkipi package from
> digikam-3.0.0-beta1 sources but there are two questions:
>
> 1. Is there any incompatible changes in libkipi 2.0.0
> with applications from KDE SC 4.9.x?

yes, completly.

>
> 2. What package version should be used should be used?
> Assume that with KDE 4.10 beta1 will be released
> libkipi-4.9.50 tarball, so for now can we use version
> for example libkipi-4.9.40 version?. It would be nice
> to have such separate libkipi-4.9.40 tarball in
> directory with digikam-3.0.0-beta1 release.

it is, in extra sub-dir.

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

[alekcejk]

Gilles Caulier wrote:

> libkipi 2.0 is include with digiKam SC. You just need to use right
> cmake flag to use local source code.
>
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/entry/README#L83
>
> At install, libkipi 2.0 header are not installed. Only binary files.
> There is no conflict possible with your distro version. More than on
> version of shared can be installed on the system
>
> Gilles Caulier

This way of building using bundled code is not allowed in Fedora, so
we have problem with building separate libkipi package.

>> 2. What package version should be used should be used?
>> Assume that with KDE 4.10 beta1 will be released
>> libkipi-4.9.50 tarball, so for now can we use version
>> for example libkipi-4.9.40 version?. It would be nice
>> to have such separate libkipi-4.9.40 tarball in
>> directory with digikam-3.0.0-beta1 release.
>
> it is, in extra sub-dir.

You mean extra sub-dir in digikam-3.0.0-beta tarball?
Sources from this tarball can be used for libkipi package
but question with package versioning (and its upgrading
to libkipi released with KDE 4.10 beta) is not solved.
Putting separate tarball (libkipi-4.9.40 for example) in
ftp://ftp.kde.org/pub/kde/unstable/digikam/
will make packaging much simpler.


--
Alexey Kurov <[hidden email]>

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

[S. Burmeister]

Am Mittwoch, 19. September 2012, 23:10:23 schrieb Gilles Caulier:
> libkipi 2.0 is include with digiKam SC. You just need to use right
> cmake flag to use local source code.
>
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-softwar
> e-compilation/repository/revisions/master/entry/README#L83
>
> At install, libkipi 2.0 header are not installed. Only binary files.
> There is no conflict possible with your distro version. More than on
> version of shared can be installed on the system

Installing libkipi10 crashes ksnapshot if one uses the "send to" feature, i.e.
if it tries to list the 2.0 kipi-plugins.

https://bugs.kde.org/show_bug.cgi?id=307114

This is reproducible for me. You need KDE 4.9.1 libkipi10 from the digikam
collection and libkipi9 from KDE 4.9.1 as well as kipi-plugins 2.0 installed
from the digikam collection. Ksnapshot starts fine but as soon as you click on
"send to" it crashes.

Application: KSnapshot (ksnapshot), signal: Segmentation fault
[KCrash Handler]
#6  QString::operator= (this=0x61636f7c, other=...) at tools/qstring.cpp:1411
#7  0xb38deea1 in KIPI::Plugin::setUiBaseName (this=0x82aa898, name=0xb3991e94
"kipiplugin_ipodexportui.rc") at /usr/src/debug/digikam-software-
compilation/extra/libkipi/libkipi/plugin.cpp:311
#8  0xb398a37b in KIPIIpodExportPlugin::Plugin_iPodExport::Plugin_iPodExport
(this=0x82aa898, parent=0x819c3c8) at /usr/src/debug/digikam-software-
compilation/extra/kipi-plugins/ipodexport/plugin_ipodexport.cpp:66
#9  0xb398a9ba in
KPluginFactory::createInstance<KIPIIpodExportPlugin::Plugin_iPodExport,
QObject> (parentWidget=0x0, parent=0x819c3c8, args=...) at
/usr/include/kpluginfactory.h:477
#10 0xb6e31286 in KPluginFactory::create (this=0x82a93b0, iface=0xb7358580
"KIPI::Plugin", parentWidget=0x0, parent=0x819c3c8, args=..., keyword=...) at
/usr/src/debug/kdelibs-4.9.1/kdecore/util/kpluginfactory.cpp:203
#11 0xb734a389 in create<KIPI::Plugin> (parent=0x819c3c8, this=<optimized
out>, args=..., keyword=..., parentWidget=0x0) at
/usr/include/kpluginfactory.h:531
#12 createInstance<KIPI::Plugin> (error=0xbfb3fe88, args=...,
parent=0x819c3c8, parentWidget=0x0, this=0x81783a8) at
/usr/include/kservice.h:565
#13 createInstance<KIPI::Plugin> (error=0xbfb3fe88, args=...,
parent=0x819c3c8, this=0x81783a8) at /usr/include/kservice.h:542
#14 KIPI::PluginLoader::Info::plugin (this=0x8178398) at
/usr/src/debug/libkipi-4.9.1/libkipi/pluginloader.cpp:133
#15 0x0805dda8 in _start ()

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

[alekcejk]

Hi,

I found that libkipi translations are not in
extra/libkipi sub-dir.
Are those translations would be added in
libkipi tarball released with KDE 4.10 or maybe
better place for them os kde-l10n?

Gilles Caulier wrote:

>> 2. What package version should be used should be used?
>> Assume that with KDE 4.10 beta1 will be released
>> libkipi-4.9.50 tarball, so for now can we use version
>> for example libkipi-4.9.40 version?. It would be nice
>> to have such separate libkipi-4.9.40 tarball in
>> directory with digikam-3.0.0-beta1 release.
>
> it is, in extra sub-dir.
>
> Gilles Caulier

--
Alexey Kurov <[hidden email]>

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

[Gilles Caulier-4]

i just forget to open translation with i18n team, just before release date.

This will change for beta2.

Gilles Caulier

2012/9/21  <[hidden email]>:

> Hi,
>
> I found that libkipi translations are not in
> extra/libkipi sub-dir.
> Are those translations would be added in
> libkipi tarball released with KDE 4.10 or maybe
> better place for them os kde-l10n?
>
> Gilles Caulier wrote:
>
>>> 2. What package version should be used should be used?
>>> Assume that with KDE 4.10 beta1 will be released
>>> libkipi-4.9.50 tarball, so for now can we use version
>>> for example libkipi-4.9.40 version?. It would be nice
>>> to have such separate libkipi-4.9.40 tarball in
>>> directory with digikam-3.0.0-beta1 release.
>>
>> it is, in extra sub-dir.
>>
>> Gilles Caulier
> --
> Alexey Kurov <[hidden email]>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel

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