Package: libc6 Version: 2.17-1 Severity: serious Justification: ABI breakage
__secure_getenv is being used by util-linux in libblkid.a. Any program linked against libblkid.a will have a dependency upon this symbol. This includes e2fsprogs, which currently FTBFSes. There may be additional users; this is just the one I'm aware of. The new glibc has secure_getenv to replace __secure_getenv but the old symbol is not retained. I've NMUed util-linux to force it to be rebuilt. This should fix the immediate issues. But the wider question is how widespread was usage of this symbol, and do we need to rebuild everything or could the symbol be restored for backward compatibility? Regards, Roger -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (550, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii debconf [debconf-2.0] 1.5.50 ii libgcc1 1:4.8.0-6 libc6 recommends no packages. Versions of packages libc6 suggests: ii glibc-doc 2.17-1 ii locales 2.17-1 ii locales-all [locales] 2.17-1 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
