Bug#844901: openssh: FTBFS: configure: error: libedit not found
reassign 844901 libedit-dev 3.1-20160903-1 affects 844901 src:openssh reassign 844573 libedit-dev 3.1-20160903-1 severity 844705 serious merge 844573 844705 844901 thanks On Sat, Nov 19, 2016 at 07:55:07AM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > checking for /proc/pid/fd directory... yes > > checking for libwrap... yes > > checking for pkg-config... /usr/bin/pkg-config > > checking if /usr/bin/pkg-config knows about libedit... yes > > checking for el_init in -ledit... no > > configure: error: libedit not found > > "tail -v -n +0 config.log" config.log says: /usr/bin/ld: cannot find -lncurses So this is the same as #844573 and #844705: either libedit-dev should depend on libncurses5-dev, or (perhaps preferably?) the fix from #644421 should be restored and libedit should once again link against libtinfo rather than libncurses. -- Colin Watson [cjwat...@debian.org]
Bug#844901: openssh: FTBFS: configure: error: libedit not found
Source: openssh Version: 1:7.3p1-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for /proc/pid/fd directory... yes > checking for libwrap... yes > checking for pkg-config... /usr/bin/pkg-config > checking if /usr/bin/pkg-config knows about libedit... yes > checking for el_init in -ledit... no > configure: error: libedit not found > "tail -v -n +0 config.log" The full build log is available from: http://aws-logs.debian.net/2016/11/18/openssh_7.3p1-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.