Bug#1066469: tack: FTBFS: configure: error: No curses header-files found
On Wed, Mar 13, 2024 at 07:03:29PM +0100, Sven Joachim wrote: > On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote: > > > Source: tack > > Version: 1.08-1 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20240313 ftbfs-trixie > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > > > Relevant part (hopefully): > >> configure: WARNING: pkg-config is not installed > >> checking for specific curses-directory... no > >> checking for specified curses library type... curses > >> checking for extra include directories... no > >> checking if we have identified curses headers... none > >> configure: error: No curses header-files found > >>tail -v -n \+0 config.log > > This reminds me that I really should update the tack package to a newer > version. The error is still present in tack 1.09 (the latest stable > release), but fixed as of tack 1.09-20230201 (the latest development > snapshot). > > @Thomas: since tack 1.09 is more than four years old and there has been > no new snapshot for over a year, how about releasing tack 1.10? This > bug will likely hit other distros as they upgrade to GCC 14. I suppose so - though others seem okay with the snapshots (I'll take a look "soon" - am working on Lynx at the moment) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1066469: tack: FTBFS: configure: error: No curses header-files found
On 2024-03-13 13:08 +0100, Lucas Nussbaum wrote: > Source: tack > Version: 1.08-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): >> configure: WARNING: pkg-config is not installed >> checking for specific curses-directory... no >> checking for specified curses library type... curses >> checking for extra include directories... no >> checking if we have identified curses headers... none >> configure: error: No curses header-files found >> tail -v -n \+0 config.log This reminds me that I really should update the tack package to a newer version. The error is still present in tack 1.09 (the latest stable release), but fixed as of tack 1.09-20230201 (the latest development snapshot). @Thomas: since tack 1.09 is more than four years old and there has been no new snapshot for over a year, how about releasing tack 1.10? This bug will likely hit other distros as they upgrade to GCC 14. Cheers, Sven
Bug#1066469: tack: FTBFS: configure: error: No curses header-files found
Source: tack Version: 1.08-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > configure: WARNING: pkg-config is not installed > checking for specific curses-directory... no > checking for specified curses library type... curses > checking for extra include directories... no > checking if we have identified curses headers... none > configure: error: No curses header-files found > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2024/03/13/tack_1.08-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results 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! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
