Your message dated Tue, 29 Jan 2013 22:49:43 +1100 with message-id <[email protected]> and subject line Re: Bug#699218: procps: FTBFS with test suite error: testsuite/lib.test/fileutils_badfd.sh missing has caused the Debian Bug report #699218, regarding procps: FTBFS with test suite error: testsuite/lib.test/fileutils_badfd.sh missing 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 [email protected] immediately.) -- 699218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699218 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: procps Version: 1:3.3.3-2 Severity: serious Justification: FTBFS Dear Maintainer, in order to help diagnosing #699205, I need to rebuild procps with debugging options as there's no pre-built -dbg package (hint, hint). Unfortunately that fails with a test suite error, despite "nocheck" being set in DEB_BUILD_OPTIONS: === Begin === sascha.silbe@twin:~/src/deb$ apt-get source procps/wheezy sascha.silbe@twin:~/src/deb$ cd procps-3.3.3 sascha.silbe@twin:~/src/deb/procps-3.3.3$ DEB_BUILD_OPTIONS="nostrip noopt" dpkg-buildpackage [...] === lib tests === Schedule of variations: unix Running target unix Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using ./config/unix.exp as tool-and-target-specific interface file. Running ./lib.test/fileutils.exp ... ERROR: tcl error sourcing ./lib.test/fileutils.exp. ERROR: couldn't execute "/home/sascha.silbe/src/deb/procps-3.3.3/testsuite/lib.test/fileutils_badfd.sh": no such file or directory while executing "spawn $badfd" (file "./lib.test/fileutils.exp" line 13) invoked from within "source ./lib.test/fileutils.exp" ("uplevel" body line 1) invoked from within "uplevel #0 source ./lib.test/fileutils.exp" invoked from within "catch "uplevel #0 source $test_file_name"" Running ./lib.test/strutils.exp ... [...] === End === -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages procps depends on: ii initscripts 2.88dsf-34 ii libc6 2.13-37 ii libncurses5 5.9-10 ii libncursesw5 5.9-10 ii libprocps0 1:3.3.3-2 ii libtinfo5 5.9-10 ii lsb-base 4.1+Debian8 Versions of packages procps recommends: ii psmisc 22.19-1 procps suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Package: procps Version: 1.3.3.6-1 On Tue, Jan 29, 2013 at 09:22:59AM +0100, Sascha Silbe wrote: > ERROR: couldn't execute > "/home/sascha.silbe/src/deb/procps-3.3.3/testsuite/lib.test/fileutils_badfd.sh": > no such file or directory This file now appears in procps 3.3.6 I'm not sure why you triggered that and i didn't as make check is run each time. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
--- End Message ---
