Control: severity -1 important Control: tags -1 upstream On 2017-01-13 09:35 +0100, Sven Joachim wrote:
> Source: angband > Version: 1:3.5.1-2.2 > User: ncur...@packages.debian.org > Usertags: ncurses5-config > > The ncurses development packages are going to see a change after the > Stretch release, ncursesw5-config will be replaced by ncursesw6-config. > Your package disables the ncurses frontend if ncursesw5-config is not > present on the build system. From my pbuilder log: > > ,---- > | checking for ncursesw5-config... no > | checking for ncurses - wide char support... no > | *** The ncursesw5-config script installed by ncursesw could not be found > | *** If ncursesw was installed in PREFIX, make sure PREFIX/bin is in > | *** your path, or set the NCURSES_CONFIG environment variable to the > | *** full path to ncursesw5-config. > | [...] > | -- Frontends -- > | - Curses No; missing libraries > `---- This is still the case today and can be tested with the ncurses version in experimental. Alas, the broken configure check is still the same in angband 4.1.2. :-( > The archlinux people did[1] > > sed -i 's/ncursesw5-config/ncursesw6-config/g' acinclude.m4 > > which obviously only works if > > a) ncurses actually starts shipping ncursesw6-config, and > b) angband regenerates the configure script, e.g. with dh_autoreconf. > > > 1. > https://git.archlinux.org/svntogit/community.git/commit/angband/trunk/PKGBUILD?id=e57bea45a128bfd527bfc6e6c70f0d5ca1d78f8f To ensure that ncursesw6-config is present, a build-dependency on libncurses-dev (>= 6.1+20180210) could be added. Which at the moment only works in experimental. Cheers, Sven
