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
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
