Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Hi Simon, Le mardi 25 octobre 2016 18:55:39 EDT, vous avez écrit : > So while this seems to have migrated into unstable, when building in the > Zesty proposed pocket, it failed to build. > > This FTBFS is only on ppc64el and seems to be caused by symbols > problems. You can take a look for yourself here: > - https://launchpad.net/ubuntu/+source/taglib/1.11.1-0.1 > - > https://launchpadlibrarian.net/290827635/buildlog_ubuntu-zesty-ppc64el.tagli > b_1.11.1-0.1_BUILDING.txt.gz > > Is this something Ubuntu-specific (in which case I'll fix this) or is it > something you guys missed? This is unrelated to the ncmpcpp problem; in this case it seems to be architecture-dependent symbols not existing on this architecture. The fix would be to tag the symbols in question (e.g. arch=!ppc64el). The odd thing is, taglib 1.11.1-0.1 has been built successfully on ppc64el on Debian [1], so I'm not sure what is happening here. I don't think it would be right to disable the symbols in Debian, because it would likely break the package on that architecture for us. Please keep me posted on your findings (by private email or on a new bug report, since #839767 is not concerned). Cheers, Matteo [1] https://buildd.debian.org/status/fetch.php? pkg=taglib=ppc64el=1.11.1-0.1=1477391033 signature.asc Description: This is a digitally signed message part.
Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
So while this seems to have migrated into unstable, when building in the Zesty proposed pocket, it failed to build. This FTBFS is only on ppc64el and seems to be caused by symbols problems. You can take a look for yourself here: - https://launchpad.net/ubuntu/+source/taglib/1.11.1-0.1 - https://launchpadlibrarian.net/290827635/buildlog_ubuntu-zesty-ppc64el.taglib_1.11.1-0.1_BUILDING.txt.gz Is this something Ubuntu-specific (in which case I'll fix this) or is it something you guys missed? -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4
Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Control: severity -1 important Control: tag -1 + upstream Control: forwarded -1 https://github.com/taglib/taglib/issues/757 Le mercredi 12 octobre 2016, 14:33:36 EDT Christoph Egger a écrit : > Control: reopen -1 > Control: reassign -1 libtag1v5 > Control: found -1 1.11+dfsg.1-0.1 > > Christoph Eggerwrites: > > Which is exactly what happened in unstable ~1 day ago as part of the > > transition. So this seems to be a totally normal unstable disturbance > > and not a bug. > > Actually missing symbol seems to indicate libtag missed a soname bump? > (And the problem was hidden by an unrelated binnmu later). Indeed, WCharByteOrder was removed between taglib 1.9 and 1.11, as well as several other symbols, but the so version was changed only from 1.14.0 to 1.16.0. I reported the problem upstream, but this is not an easy matter, as we can't just decide to bump the soname in Debian without a green light from upstream. Matteo signature.asc Description: This is a digitally signed message part.
Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Control: reopen -1 Control: reassign -1 libtag1v5 Control: found -1 1.11+dfsg.1-0.1 Christoph Eggerwrites: > Which is exactly what happened in unstable ~1 day ago as part of the > transition. So this seems to be a totally normal unstable disturbance > and not a bug. Actually missing symbol seems to indicate libtag missed a soname bump? (And the problem was hidden by an unrelated binnmu later). Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer
Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Hi! Nick Blackwrites: > I rebuilt the source package against current libtag, and it works once > more. Which is exactly what happened in unstable ~1 day ago as part of the transition. So this seems to be a totally normal unstable disturbance and not a bug. Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer
Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Package: ncmpcpp Version: 0.7.4-1 Followup-For: Bug #839767 I rebuilt the source package against current libtag, and it works once more. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ncmpcpp depends on: ii libboost-filesystem1.61.0 1.61.0+dfsg-2.1+b1 ii libboost-locale1.61.0 1.61.0+dfsg-2.1+b1 ii libboost-program-options1.61.0 1.61.0+dfsg-2.1+b1 ii libboost-regex1.61.01.61.0+dfsg-2.1+b1 ii libboost-system1.61.0 1.61.0+dfsg-2.1+b1 ii libboost-thread1.61.0 1.61.0+dfsg-2.1+b1 ii libc6 2.24-3 ii libcurl3-gnutls 7.50.1-1 ii libfftw3-double33.3.5-1 ii libgcc1 1:6.2.0-5 ii libicu5757.1-4 ii libmpdclient2 2.9-1 ii libncursesw56.0+20160917-1 ii libreadline77.0-1 ii libstdc++6 6.2.0-5 ii libtag1v5 1.11+dfsg.1-0.2 ii libtinfo5 6.0+20160917-1 ncmpcpp recommends no packages. Versions of packages ncmpcpp suggests: ii desktop-file-utils 0.23-1 ii mpd 0.19.19-1 -- no debconf information
Bug#839767: ncmpcpp fails to start due to undefined symbol in binary
Package: ncmpcpp Version: 0.7.4-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, ncmpcpp is not able to start at all. any attempt to start results into this: bash$ ncmpcpp ncmpcpp: symbol lookup error: ncmpcpp: undefined symbol: _ZN6TagLib6String14WCharByteOrderE I tried to check what is missing: bash$ echo _ZN6TagLib6String14WCharByteOrderE|c++filt TagLib::String::WCharByteOrder though it looks like taglib is available in my system: bash$ dpkg -l | grep libtag ii libtag-extras1 1.0.1-3+b1 amd64TagLib extras library - support for more file formats ii libtag1v5:amd641.11+dfsg.1-0.1amd64audio meta-data library ii libtag1v5-vanilla:amd641.11+dfsg.1-0.1amd64audio meta-data library - vanilla flavour ii libtaglib-ocaml0.3.1-1+b3 amd64OCaml bindings for the TagLib Audio Meta-Data Library ldd also shows, that all dependencies are in place: bash$ ldd /usr/bin/ncmpcpp linux-vdso.so.1 (0x7ffdcdfc5000) libboost_filesystem.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.61.0 (0x7f44a026) libboost_system.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.61.0 (0x7f44a005c000) libboost_locale.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_locale.so.1.61.0 (0x7f449fd71000) libboost_program_options.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.61.0 (0x7f449faf2000) libboost_regex.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.61.0 (0x7f449f7da000) libicuuc.so.57 => /usr/lib/x86_64-linux-gnu/libicuuc.so.57 (0x7f449f43) libicudata.so.57 => /usr/lib/x86_64-linux-gnu/libicudata.so.57 (0x7f449d9b3000) libboost_thread.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.61.0 (0x7f449d78b000) libmpdclient.so.2 => /usr/lib/libmpdclient.so.2 (0x7f449d574000) libreadline.so.6 => /lib/x86_64-linux-gnu/libreadline.so.6 (0x7f449d32a000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f449d10d000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f449cedb000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f449ccb1000) libfftw3.so.3 => /usr/lib/x86_64-linux-gnu/libfftw3.so.3 (0x7f449c8b4000) libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x7f449c63a000) libtag.so.1 => /usr/lib/x86_64-linux-gnu/libtag.so.1 (0x7f449c357000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f449bfd6000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f449bcd) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f449bab9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f449b71b000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f449b513000) libboost_chrono.so.1.61.0 => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.61.0 (0x7f449b30c000) libicui18n.so.57 => /usr/lib/x86_64-linux-gnu/libicui18n.so.57 (0x7f449ae92000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f449ac8c000) /lib64/ld-linux-x86-64.so.2 (0x55964ec77000) libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 (0x7f449aa66000) libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x7f449a832000) librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 (0x7f449a615000) libssh2.so.1 => /usr/lib/x86_64-linux-gnu/libssh2.so.1 (0x7f449a3e9000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7f449a1b) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7f4499e4e000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7f4499c03000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7f449992b000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7f44996fb000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7f44994f7000) liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x7f44992e6000) libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x7f4499095000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4498e7a000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7f4498c45000) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7f44989c2000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f44986b1000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7f449844c000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7f4498239000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7f449802d000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7f4497e29000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f4497c12000) libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2