[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#762243: kde-workspace FTBFS on arm64 dpkg-shlibdeps issues



Package: kde-workspace
Version: $:4.11.11-2
Severity: important
User: debian-arm@lists.debian.org
Usertags: arm64

kde-workspace seems to be failing to build on arm64 with dpkg-shlibdeps issues related to libkwinglesutils.so.

https://buildd.debian.org/status/fetch.php?pkg=kde-workspace&arch=arm64&ver=4%3A4.11.11-2&stamp=1411113959

-- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkwinglesutils.so.1.0.0
-- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkwinglesutils.so.1
-- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/libkwinglesutils.so
-- Removed runtime path from "/«PKGBUILDDIR»/debian/tmp/usr/lib/libkwinglesutils.so.1.0.0"
<--snip-->
dpkg-shlibdeps: warning: can't extract name and version from library name 'libkdeinit4_kwin_rules_dialog.so'
dpkg-shlibdeps: error: couldn't find library libkwinglesutils.so.1 needed by debian/kde-window-manager/usr/lib/kde4/libkdeinit/libkdeinit4_kwin_gles.so (ELF format: 'elf64-littleaarch64'; RPATH: '')
dpkg-shlibdeps: error: couldn't find library libkwinglesutils.so.1 needed by debian/kde-window-manager/usr/lib/kde4/kwin4_effect_gles_builtins.so (ELF format: 'elf64-littleaarch64'; RPATH: '')
dpkg-shlibdeps: warning: can't extract name and version from library name 'libkdeinit4_kwin.so'
<--snip-->
dpkg-shlibdeps: error: cannot continue due to the errors listed above
Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
To help dpkg-shlibdeps find private libraries, you might need to use -l.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/kde-window-manager.substvars debian/kde-window-manager/usr/lib/kde4/kcm_kwin4_effect_builtins.so debian/kde-window-manager/usr/lib/kde4/kcm_kwin4_genericscripted.so debian/kde-window-manager/usr/lib/kde4/kcm_kwin_scripts.so debian/kde-window-manager/usr/lib/kde4/kcm_kwincompositing.so debian/kde-window-manager/usr/lib/kde4/kcm_kwindecoration.so debian/kde-window-manager/usr/lib/kde4/kcm_kwindesktop.so debian/kde-window-manager/usr/lib/kde4/kcm_kwinoptions.so debian/kde-window-manager/usr/lib/kde4/kcm_kwinrules.so debian/kde-window-manager/usr/lib/kde4/kcm_kwinscreenedges.so debian/kde-window-manager/usr/lib/kde4/kcm_kwintabbox.so debian/kde-window-manager/usr/lib/kde4/kwin3_aurorae.so debian/kde-window-manager/usr/lib/kde4/kwin3_b2.so debian/kde-window-manager/usr/lib/kde4/kwin3_laptop.so debian/kde-window-manager/usr/lib/kde4/kwin3_oxygen.so debian/kde-window-manager/usr/lib/kde4/kwin4_effect_builtins.so debian/kde-window-manager/usr/lib/kde4/kwin4_effect_gles_builtins.so debian/kde-window-manager/usr/lib/kde4/kwin_b2_config.so debian/kde-window-manager/usr/lib/kde4/kwin_oxygen_config.so debian/kde-window-manager/usr/lib/kde4/libkdeinit/libkdeinit4_kwin_rules_dialog.so debian/kde-window-manager/usr/lib/kde4/libkdeinit/libkdeinit4_kwin_gles.so debian/kde-window-manager/usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so debian/kde-window-manager/usr/lib/kde4/libexec/kwin_killer_helper debian/kde-window-manager/usr/lib/kde4/libexec/kwin_opengl_test debian/kde-window-manager/usr/lib/kde4/libexec/kwin_rules_dialog debian/kde-window-manager/usr/lib/kde4/imports/org/kde/kwin/decorations/plastik/libplastikplugin.so debian/kde-window-manager/usr/lib/kde4/imports/org/kde/kwin/decoration/libdecorationplugin.so debian/kde-window-manager/usr/lib/kconf_update_bin/kwin_update_default_rules debian/kde-window-manager/usr/lib/kconf_update_bin/kwin_update_settings_410 debian/kde-window-manager/usr/lib/kconf_update_bin/kwin_update_settings_411 debian/kde-window-manager/usr/lib/kconf_update_bin/kwin_update_settings_49 debian/kde-window-manager/usr/lib/kconf_update_bin/kwin_update_tabbox_qml_settings debian/kde-window-manager/usr/lib/kconf_update_bin/kwin_update_tabbox_settings debian/kde-window-manager/usr/bin/kwin debian/kde-window-manager/usr/bin/kwin_gles returned exit code 2


It appears the file is being installed so i'm not sure why dpkg-shlibdeps is not finding it. I have not tried to reproduce or debug this issue locally.


Reply to: