Your message dated Thu, 21 Jun 2012 11:51:13 +0000 with message-id <e1shfur-0003ev...@franck.debian.org> and subject line Bug#666339: fixed in tcptrace 6.6.7-4.1 has caused the Debian Bug report #666339, regarding tcptrace: FTBFS: cp: cannot stat `debian/tmp/tcptrace': No such file or directory to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 666339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: tcptrace Version: 6.6.7-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: > fakeroot debian/rules binary-arch > dh_testdir > CFLAGS=-D_BSD_SOURCE ./configure --prefix=/usr --sysconfdir=/etc > --mandir=/usr/share/man > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking target system type... x86_64-unknown-linux-gnu > checking for gcc... gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for executable suffix... > checking for object suffix... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking gcc version... 4 > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking whether make sets ${MAKE}... yes > checking for flex... no > checking for lex... no > checking for yywrap in -lfl... no > checking for yywrap in -ll... no > checking for bison... no > checking for byacc... no > checking for main in -lm... yes > checking how to run the C preprocessor... gcc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for unsigned long long int... yes > checking size of unsigned long long int... 8 > checking for unsigned long int... yes > checking size of unsigned long int... 8 > checking for unsigned int... yes > checking size of unsigned int... 4 > checking for unsigned short... yes > checking size of unsigned short... 2 > checking for gethostbyname... yes > checking for socket... yes > checking for putmsg in -lstr... no > checking for fpurge... no > checking for mkstemp... yes > checking for valloc... yes > checking for memalign... yes > checking for inet_pton... yes > checking how to print unsigned long long... %llu > configure: creating ./config.status > config.status: creating Makefile > touch config-stamp > touch build-indep-stamp > touch build-stamp > dh_testdir > dh_testroot > dh_installdirs > dh_install > cp: cannot stat `debian/tmp/tcptrace': No such file or directory > dh_install: cp -a debian/tmp/tcptrace debian/tcptrace/usr/bin/ returned exit > code 1 > make: *** [binary-arch] Error 2 The full build log is available from: http://people.debian.org/~lucas/logs/2012/03/30/tcptrace_6.6.7-4_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 about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems.
--- End Message ---
--- Begin Message ---Source: tcptrace Source-Version: 6.6.7-4.1 We believe that the bug you reported is fixed in the latest version of tcptrace, which is due to be installed in the Debian FTP archive: tcptrace_6.6.7-4.1.diff.gz to main/t/tcptrace/tcptrace_6.6.7-4.1.diff.gz tcptrace_6.6.7-4.1.dsc to main/t/tcptrace/tcptrace_6.6.7-4.1.dsc tcptrace_6.6.7-4.1_amd64.deb to main/t/tcptrace/tcptrace_6.6.7-4.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 666...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso <car...@debian.org> (supplier of updated tcptrace package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 16 Jun 2012 09:03:38 +0200 Source: tcptrace Binary: tcptrace Architecture: source amd64 Version: 6.6.7-4.1 Distribution: unstable Urgency: low Maintainer: Noah Meyerhans <no...@debian.org> Changed-By: Salvatore Bonaccorso <car...@debian.org> Description: tcptrace - Tool for analyzing tcpdump output Closes: 666339 Changes: tcptrace (6.6.7-4.1) unstable; urgency=low . * Non-maintainer upload. * Correct debian/rules's build-arch target use. Fix FTBFS: "cp: cannot stat `debian/tmp/tcptrace': No such file or directory". (Closes: #666339) * Use autotools-dev dh helper scripts to handle config.{sub,guess} Use dh_autotools-dev_updateconfig in config-stamp target, and dh_autotools-dev_restoreconfig in clean target in debian/rules. Checksums-Sha1: c2a8a02747c8f4847b2b6e16210ae95bc871216a 1711 tcptrace_6.6.7-4.1.dsc 0f876699fb42234fe65a7d2b1a7b3421f440ce2e 29161 tcptrace_6.6.7-4.1.diff.gz f1a0cded5affa790a3156632486dd4255e553778 172936 tcptrace_6.6.7-4.1_amd64.deb Checksums-Sha256: 0ae1a4b4952606992a9d3e4a8e04d6424a29a284a1bc721fcfd8ffb5b6fb67b5 1711 tcptrace_6.6.7-4.1.dsc 8d146edf2763badd92813404240c996613e256f1300c801f0dad02b842bf3ed4 29161 tcptrace_6.6.7-4.1.diff.gz ee176b4c1d64f04b36585af35207d3536372bb104a15424e39b23ddfb5557c54 172936 tcptrace_6.6.7-4.1_amd64.deb Files: 6d50004d5ee920851eb4ab0850d729f1 1711 net optional tcptrace_6.6.7-4.1.dsc d073fb808e942f75399d035ba80c78cf 29161 net optional tcptrace_6.6.7-4.1.diff.gz 64b0bc35d12f367c0525ea4f48638671 172936 net optional tcptrace_6.6.7-4.1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP3DEOAAoJEHidbwV/2GP+oTwP/0dv8exc1B4NnsGujFQ16tcB /zI+YrtzL9JPhETPcjycAT8uJswb7tsxj8w+DLKU9TJ1QPs+HSCPg/3sYpD9Mpsx M//NZN++lMZBpj9DWOOgkrnVUvzTaQegKebe3BxPfTbqypS730aGYikbCA8LCOMK GZleZNZR1Y7+z/yQdF2cAx04vPrEfKYkUntKY/56ou73A+nqbme1E+xE8fltLBmn I6faeGJ6dFvO2VHgAXhy+FoNYgcevHu0jahsqgQ22+6AWegmUI4v8apOVCqLadXo ZblENt+Z/ppE2Tfe3RT1+vQbPJm5YS39eAbDt10FXMQVac41uuU6ynSEFHLzaneg YEYuyeIHvrlT8U6wGEylM7e8g0H9RAkQnz/PfUfzMNOY9hjI8e56GyYVyLaDQoF5 Tz3WdhWxWAkp6cbrRpt1RSCBSpNfideTBGU0pUSxz1dFxYz5x5gxu+Z0ZpDv1hvG fwJMM51fbRQQ27ARx7tl6I0WWFO6Zk0C7npxgHcWky0o0ZqV8xglyW77oCfMJhOT FbM/4Foy2HnEgquMO7DM+kN0SrrZBqcGP6BQMcdlZJ0zB/EvB/9VtkMtZ3qjPxvi /IObp60tkrzDQxJ/fgplv6YxkyzB1Xp/pWujN+vG+F0VBLS+eLXxoMLZQ4j5r5JG B3EjVJGv6uado3SEUJji =kSy8 -----END PGP SIGNATURE-----
--- End Message ---
