See
https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/381//console
or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt5/381/
for more information.
See
https://jenkins.debian.net/job/chroot-installation_sid_install_kde-full/968//console
or just
https://jenkins.debian.net/job/chroot-installation_sid_install_kde-full/968/
for more information.
See
https://jenkins.debian.net/job/chroot-installation_sid_install_kde/1066//console
or just
https://jenkins.debian.net/job/chroot-installation_sid_install_kde/1066/ for
more information.
See
https://jenkins.debian.net/job/chroot-installation_sid_install_qt4/374//console
or just https://jenkins.debian.net/job/chroot-installation_sid_install_qt4/374/
for more information.
Your message dated Wed, 16 Dec 2015 22:26:28 +0100
with message-id <5671d704.20...@free.fr>
and subject line The bug is in dikikam/core/CMakeList.txt
has caused the Debian Bug report #807363,
regarding libkf5akonadicontact-dev: KF5AkonadiContactConfigVersion.cmake
reports bad version
to be marked
Your message dated Wed, 16 Dec 2015 22:25:09 +0100
with message-id <5671d6b5.7080...@free.fr>
and subject line The bug is rather in kipi-plugin CMakeList.txt
has caused the Debian Bug report #807361,
regarding libkf5calendarcore-dev: bad version number in
KF5CalendarCoreConfigVersion.cmake
to be m
Hey,
ah now i see the problem:
>extra/kipi-plugins/CMakeLists.txt:116 (find_package)
find_package(KF5 ${KF5_MIN_VERSION}
OPTIONAL_COMPONENTS
Archive # for FlashExport
ThreadWeaver # for Panorama
CalendarCore # for Calendar
)
^^ here it
I haven't yet found the line that generates that.
find_package(KF5 ${KF5_MIN_VERSION}
OPTIONAL_COMPONENTS
Archive # for FlashExport
ThreadWeaver # for Panorama
CalendarCore # for Calendar <==
)
--eric
On 16/12/2015 20:15, Sandro Knauß wrote:
But digikam can't relay on a version for libkcalcore > 5 because the ci
build.kde.org would show red for that.
It should not but it does.
I checked the source code (kipi plugins) and see the following CMakeLists.txt:
PRINT_OPTIONAL_LIBRARY_STATUS("l
Hi,
> I'm quite surprised because digikam expects 15.08.2 which is the package
> version name. 4:15.08.2-1 => 15.08.2 no?
Debian take the versionnumer from the bundles in where the libs exist - in our
case it is KDE Applications and this is release every four months (15.08,
15.12,...)
But every
Will discuss with digikam author..
--eric
On 16/12/2015 17:58, Adrien Grellier wrote:
Hi,
It seems that the lib version is 4.82, as we can see in the filename or in the
CmakeLists.txt :
https://sources.debian.net/src/kcalcore/4:15.08.2-1/CMakeLists.txt/
In order to build digikam, I am afraid we will have to wait for a newer
version of
Hi,
It seems that the lib version is 4.82, as we can see in the filename or in the
CmakeLists.txt :
https://sources.debian.net/src/kcalcore/4:15.08.2-1/CMakeLists.txt/
In order to build digikam, I am afraid we will have to wait for a newer
version of libkf5calendarcore.
Regards,
Adrien
signa
Hey,
no it is not a bad version number, because it is planned to push kcalcore to
Frameworks, but because it isn't ready for frameworks it is shipped with KDE
Applications alongside with kdepim. Thats why the version number isn't synced
with KDE Applications.
Regards,
sandro
Got another stacktrace:
Application: konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6 0x7f8f6a6a11b3 in QString::~QString() (_q_value=@0x7f8f56584560: ) at
../../include/QtCore/../../src/corelib/threa
15 matches
Mail list logo
