[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
tags 893515 +patch thanks I am currently doing a final build with the changes, assuming it suceeds I will upload it to Raspbian and post a debdiff to this bug. debdiff can be found at http://debdiffs.raspbian.org/main/d/digikam/digikam_5.7.0-2+rpi1.debdiff ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
This was blocking stuff up in Raspbian buster so I decided to take a look. I decided to base my work on the version currently in Debian experimental. First of all I reduced the exiv2 dependency in both the Debian packaging and the upstream cmake to 0.25. I then turned my attention to the kdepim problem. After some time messing around with upstreams broken git history I was able to locate the relevent patches, merge them together and fix-up the filepaths. They then applied cleanly. I then ran into another build failure. In file included from /usr/include/c++/7/cmath:45:0, from /usr/include/c++/7/math.h:36, from /digikam-5.7.0/core/libs/rawengine/libraw/internal/dcraw_common.cpp:22: /usr/include/arm-linux-gnueabihf/bits/mathcalls.h:140:1: note: candidate: _Float64 powf64(_Float64, _Float64) __MATHCALL_VEC (pow,, (_Mdouble_ __x, _Mdouble_ __y)); ^ /digikam-5.7.0/core/libs/rawengine/libraw/internal/dcraw_common.cpp:5752:14: note: candidate: float powf64(float, float) static float powf64(float a, float b) it looks like there is a conflict between a function called "powf64" in the dcraw code in digikam and a "powf64" function in the kernel headers upstream fixed this by renaming powf64 to libraw_powf64, I did the same. In this case since it was a simple rename I did not bother going digging for the original upstream patch. I am currently doing a final build with the changes, assuming it suceeds I will upload it to Raspbian and post a debdiff to this bug. No intent to NMU in Debian. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
On Sunday, April 8, 2018 1:25:42 PM CDT Simon Frei wrote: > I totally understand that, I am just trying to get infos to you as > debian maintainer from my (at the moment admittedly almost non-existing) > involvement upstream. Exiv2 0.26 will likely not get into testing. > Upstream does backport a lot of security fixes to 0.26, but negated > creating a dot release on request, and is focussing on 0.27. It was > planned to release an rc in early 2018, but from what I read in the > issue tracker, that's not going to happen asap. Yes, fair enough. I'm not entirely opposed to patching digikam to accept the older exiv2. That was going to be my Plan B in any case, but you make a good case to do it immediately and work on updating exiv2 in parallel. -S signature.asc Description: This is a digitally signed message part. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
I totally understand that, I am just trying to get infos to you as debian maintainer from my (at the moment admittedly almost non-existing) involvement upstream. Exiv2 0.26 will likely not get into testing. Upstream does backport a lot of security fixes to 0.26, but negated creating a dot release on request, and is focussing on 0.27. It was planned to release an rc in early 2018, but from what I read in the issue tracker, that's not going to happen asap. signature.asc Description: OpenPGP digital signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
Digikam still works with exiv2 0.25. It's just that a lot of fixes have gone into 0.26 that prevent crashs in digikam, that's why its cmake file has a >=0.26 dependency. signature.asc Description: OpenPGP digital signature ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
On Monday, March 19, 2018 10:48:38 AM CDT you wrote: > digikam 5.6.0-4 can't be compiled with KDE Pim 17.12.2, it failes > because kcalcore was been refactored to use QDateTime instead of > KDateTime. I have DigiKam 5.9.0 compiled locally and it works. Unfortunately, it depends on exiv2 0.26 that only exists in experimental. So the digikam upload will also be to experimental. -Steve signature.asc Description: This is a digitally signed message part. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
Control: notfound -1 5.6.0-4 Control: found -1 4:5.7.0-2 Control: found -1 4:5.6.0-4 Control: blocks 894342 by -1 Control: severity -1 serious As the kdepim transition has now started raise the severity to serious. The transition bug is #894342. hefee -- On Montag, 19. März 2018 16:48:38 CEST Sandro Knauß wrote: > Source: digikam > Version: 5.6.0-4 > Severity: important > > Hey, > > digikam 5.6.0-4 can't be compiled with KDE Pim 17.12.2, it failes > because kcalcore was been refactored to use QDateTime instead of > KDateTime. Additionally, it does not find KDocTools, please add > libkf5doctools-dev to Build-Deps to resolve this. > > See attached buildlog against KDE Pim 17.12.2 and KF 5.43, both currently > exisitng in experimental. We are currently preparing atransiton for KDE Pim > 17.12.2 in the next days. From the upstream bugreport #387960 it looks > like this issue is fixed with 5.8.0. > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled signature.asc Description: This is a digitally signed message part. ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
[Pkg-kde-extras] Bug#893515: digikam: FTBFS with kdepim 17.12.2
Source: digikam Version: 5.6.0-4 Severity: important Hey, digikam 5.6.0-4 can't be compiled with KDE Pim 17.12.2, it failes because kcalcore was been refactored to use QDateTime instead of KDateTime. Additionally, it does not find KDocTools, please add libkf5doctools-dev to Build-Deps to resolve this. See attached buildlog against KDE Pim 17.12.2 and KF 5.43, both currently exisitng in experimental. We are currently preparing atransiton for KDE Pim 17.12.2 in the next days. From the upstream bugreport #387960 it looks like this issue is fixed with 5.8.0. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ___ pkg-kde-extras mailing list pkg-kde-extras@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
