[Pkg-octave-devel] Bug#524745: Bug#524745: Bug#524745: Postinst seems to run forever on mipsel

[Rafael Laboissiere]

* Stephen Gran <sgran at debian.org> [2009-04-21 23:55]:

> This one time, at band camp, Rafael Laboissiere said:
> > * Martin Zobel-Helas <zobel at ftbfs.de> [2009-04-21 21:17]:
> > 
> > > here some more infos:
> > > 
> > > 21029 ?        S      0:00      \_ sh -c /usr/bin/sudo /usr/bin/apt-get --purge -o Dir::State::status=/home/buildd/build/chroot-unstable/var/lib/dpkg/status -o DPkg::Options::=--root=/home/buildd/build/chroot-unstable -o DPkg::R
> > > 21030 ?        S      0:03          \_ /usr/bin/apt-get --purge -o Dir::State::status=/home/buildd/build/chroot-unstable/var/lib/dpkg/status -o DPkg::Options::=--root=/home/buildd/build/chroot-unstable -o DPkg::Run-Directory=/ho
> > > 22519 pts/0    Ss+    0:00              \_ /usr/bin/dpkg --root=/home/buildd/build/chroot-unstable --force-confold --status-fd 14 --configure libmagic1 file gettext-base libkeyutils1 libkrb5support0 libk5crypto3 libkrb5-3 libgss
> > > 23967 pts/0    S+     0:00                  \_ /bin/sh -e /var/lib/dpkg/info/octave3.0.postinst configure 
> > > 23976 pts/0    R+   1987:42                      \_ octave-3.0.5 --silent --no-history --no-init-file --eval pkg ('rebuild');
> > > 
> > > strace -p 23976
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> > > [...] runs infitive
> > 
> > Thanks for the info.  Is the hanging due to some file Octave is trying to
> > open/read/close?  Could you please run lsof on the octave-3.0.5 process
> > and post the results?  In the case above, it would be:
> > 
> >     lsof -p 23976
> 
> The process has been killed, so we no longer have that information for
> you.

Yes, I know, but could you try to launch the offending command:

    octave-3.0.5 --silent --no-history --no-init-file --eval "pkg ('rebuild');"
    
in one of the machines where it fails and see what happens?

-- 
Rafael