Source: libssh2 Version: 1.5.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past)
libssh2 FTBFS on all architectures with: --- debian/libssh2-1.symbols (libssh2-1_1.5.0-1_m68k) +++ dpkg-gensymbolssAyNcA 2015-03-30 08:09:06.562181072 +0000 @@ -56,8 +56,8 @@ libssh2_knownhost_readline@Base 1.2 libssh2_knownhost_writefile@Base 1.2 libssh2_knownhost_writeline@Base 1.2 - libssh2_md5@Base 1.5.0 - libssh2_md5_init@Base 1.5.0 +#MISSING: 1.5.0-1# libssh2_md5@Base 1.5.0 +#MISSING: 1.5.0-1# libssh2_md5_init@Base 1.5.0 libssh2_poll@Base 1.0 libssh2_poll_channel_read@Base 1.0 libssh2_publickey_add_ex@Base 1.0 @@ -114,8 +114,8 @@ libssh2_sftp_tell@Base 1.0 libssh2_sftp_unlink_ex@Base 1.0 libssh2_sftp_write@Base 1.0 - libssh2_sha1@Base 1.5.0 - libssh2_sha1_init@Base 1.5.0 +#MISSING: 1.5.0-1# libssh2_sha1@Base 1.5.0 +#MISSING: 1.5.0-1# libssh2_sha1_init@Base 1.5.0 libssh2_trace@Base 1.0 libssh2_trace_sethandler@Base 1.2.3 libssh2_userauth_authenticated@Base 1.0 I question how you could possibly have built and uploaded the i386 binaries of it, except in an unclean (maybe not minimal or not up-to-date) chroot, or not even in a chroot. The effect of this is that you broke ABI on i386, even. -- System Information: Debian Release: 8.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: m68k Kernel: Linux 3.16.0-4-m68k Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
