Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

2018-05-20 Thread Sven Joachim
Control: reassign -1 acr 1.6.1-1

On 2018-05-15 14:42 +0200, meskio wrote:

> Quoting Sven Joachim (2018-05-06 21:50:57)
>> It seems to me this is a bug in acr 1.6.1-1.  The configure script
>> generated by it is clearly broken, and the same tudu version built
>> successfully with acr 1.2-1 back in June 2017.  Maybe the acr
>> maintainer can find out what went wrong here.
>
> I submited the bug upstream:
> https://github.com/radare/acr/issues/15
>
> I'll try to fix it myself.

Thanks, I can confirm that tudu builds with acr 1.6.2-1.  Reassigning
the bug to your package, will close it in a minute.

Cheers,
   Sven



Processed: Re: Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

2018-05-20 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 acr 1.6.1-1
Bug #897537 [src:tudu] tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: 
not found
Bug reassigned from package 'src:tudu' to 'acr'.
No longer marked as found in versions tudu/0.10.2-1.
Ignoring request to alter fixed versions of bug #897537 to the same values 
previously set
Bug #897537 [acr] tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not 
found
Marked as found in versions acr/1.6.1-1.

-- 
897537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

2018-05-15 Thread meskio
Quoting Sven Joachim (2018-05-06 21:50:57)
> It seems to me this is a bug in acr 1.6.1-1.  The configure script
> generated by it is clearly broken, and the same tudu version built
> successfully with acr 1.2-1 back in June 2017.  Maybe the acr
> maintainer can find out what went wrong here.

I submited the bug upstream:
https://github.com/radare/acr/issues/15

I'll try to fix it myself.

-- 
meskio | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.


signature.asc
Description: signature


Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

2018-05-06 Thread Sven Joachim
On 2018-05-02 22:54 +0200, Lucas Nussbaum wrote:

> Source: tudu
> Version: 0.10.2-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20180502 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):
>> make[1]: Entering directory '/<>'
>> rm -f configure Makefile */Makefile
>> acr
>> acr: ./configure script created successfully.
>> acr: all done.
>> dh_auto_configure
>>  ./configure --build=x86_64-linux-gnu --prefix=/usr
>> --includedir=\${prefix}/include --mandir=\${prefix}/share/man
>> --infodir=\${prefix}/share/info --sysconfdir=/etc
>> --localstatedir=/var --disable-silent-rules
>> --libdir=\${prefix}/lib/x86_64-linux-gnu
>> --libexecdir=\${prefix}/lib/x86_64-linux-gnu
>> --disable-maintainer-mode --disable-dependency-tracking
>> checking for cpp... ERROR:  cannot parse sources

It seems to me this is a bug in acr 1.6.1-1.  The configure script
generated by it is clearly broken, and the same tudu version built
successfully with acr 1.2-1 back in June 2017.  Maybe the acr
maintainer can find out what went wrong here.

>> WARNING: Unknown flag '--disable-silent-rules'.
>> 
>> 
>> WARNING: Unknown flag '--disable-maintainer-mode'.
>> 
>> 
>> WARNING: Unknown flag '--disable-dependency-tracking'.
>> 
>> checking build system type... x86_64-linux-gnu
>> checking host system type... x86_64-unknown-linux-gnu
>> checking target system type... x86_64-unknown-linux-gnu
>> checking for working directories... current
>> using prefix '/usr'
>> checking for c++ compiler... g++
>> checking for xcurses.h... no
>> checking for ncursesw/curses.h... yes
>> checking for ncurses/curses.h... no
>> checking for ncurses.h... yes
>> checking for curses.h... yes
>> checking for libncursesw ... yes
>> checking for libncurses ... yes
>> checking for libcurses ... yes
>> checking for WIDEC_CURSES... ./configure: 394: ./configure: 
>> echo#define_XOPEN_SOURCE_EXTENDED: not found
>> ./configure: 394: ./configure: echo#include: not found
>> ./configure: 394: ./configure: echointmain(){addwstr(L"");}: not found
>> ./configure: 394: ./configure: cannot create /dev/null2: Permission denied
>> ./configure: 394: ./configure: eval$CXX-g: not found
>> ./configure: 394: ./configure: rmtest.c: not found
>> no
>> 
>> ERROR: There is no wide character support on curses!
>> 
>> dh_auto_configure: ./configure --build=x86_64-linux-gnu
>> --prefix=/usr --includedir=\${prefix}/include
>> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
>> --sysconfdir=/etc --localstatedir=/var --disable-silent-rules
>> --libdir=\${prefix}/lib/x86_64-linux-gnu
>> --libexecdir=\${prefix}/lib/x86_64-linux-gnu
>> --disable-maintainer-mode --disable-dependency-tracking returned
>> exit code 1
>> make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 2

Cheers,
   Sven



Bug#897537: tudu: FTBFS: ./configure: 394: ./configure: rmtest.c: not found

2018-05-02 Thread Lucas Nussbaum
Source: tudu
Version: 0.10.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 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):
> make[1]: Entering directory '/<>'
> rm -f configure Makefile */Makefile
> acr
> acr: ./configure script created successfully.
> acr: all done.
> dh_auto_configure
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking
> checking for cpp... ERROR:  cannot parse sources
> 
> WARNING: Unknown flag '--disable-silent-rules'.
> 
> 
> WARNING: Unknown flag '--disable-maintainer-mode'.
> 
> 
> WARNING: Unknown flag '--disable-dependency-tracking'.
> 
> checking build system type... x86_64-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> checking for working directories... current
> using prefix '/usr'
> checking for c++ compiler... g++
> checking for xcurses.h... no
> checking for ncursesw/curses.h... yes
> checking for ncurses/curses.h... no
> checking for ncurses.h... yes
> checking for curses.h... yes
> checking for libncursesw ... yes
> checking for libncurses ... yes
> checking for libcurses ... yes
> checking for WIDEC_CURSES... ./configure: 394: ./configure: 
> echo#define_XOPEN_SOURCE_EXTENDED: not found
> ./configure: 394: ./configure: echo#include: not found
> ./configure: 394: ./configure: echointmain(){addwstr(L"");}: not found
> ./configure: 394: ./configure: cannot create /dev/null2: Permission denied
> ./configure: 394: ./configure: eval$CXX-g: not found
> ./configure: 394: ./configure: rmtest.c: not found
> no
> 
> ERROR: There is no wide character support on curses!
> 
> dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
> --disable-dependency-tracking returned exit code 1
> make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/tudu_0.10.2-1_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.