Package: posixtestsuite
Severity: normal
Version: 1.4.3-1

I get problems trying to build posixtestsuite using pbuilder (in an
i386 chroot):

...
dpkg-genchanges: binary-only upload - not including any source code
dpkg-buildpackage: binary only upload (no source included)
W: no hooks of type B found -- ignoring
 -> unmounting dev/pts filesystem
umount: /var/cache/pbuildd/chroot/dev/pts: device is busy
umount: /var/cache/pbuildd/chroot/dev/pts: device is busy
W: Retrying to unmount dev/pts
umount: /var/cache/pbuildd/chroot/dev/pts: device is busy
umount: /var/cache/pbuildd/chroot/dev/pts: device is busy

  Could not unmount dev/pts, there might be some program 
  still using files in /proc (klogd?).
  Please check and kill the process manually so that I can unmount dev/pts

  This error is only happens with chroot; try using user-mode-linux to 
  avoid this message.

...

And this message repeats indefinitely.  It turns out there's a process
left over from conformance/interfaces/sigpause/4-1.test which causes
this, and won't die for anything short of a kill -9.  The test log
shows:

...
spawn 
/tmp/buildd/posixtestsuite-1.4.3/build-tree/posixtestsuite-1.4.3/./conformance/interfaces/sigpause/3-1.test^M
signal was called^M
Test PASSED: sigpause returned -1 and set errno to EINTR^M
Test PASSED^M
spawn 
/tmp/buildd/posixtestsuite-1.4.3/build-tree/posixtestsuite-1.4.3/./conformance/interfaces/sigpause/4-1.test^M
spawn 
/tmp/buildd/posixtestsuite-1.4.3/build-tree/posixtestsuite-1.4.3/./conformance/interfaces/sigpending/1-1.test^M
All pending signals found^M
Unsent signals not found.^M
Test PASSED^M
...

-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.11-9-amd64-k8
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)

-- 
Daniel Schepler              "Please don't disillusion me.  I
[EMAIL PROTECTED]    haven't had breakfast yet."
                                 -- Orson Scott Card


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to