* Rafael Laboissiere raf...@debian.org [2009-05-05 11:25]:
That would be great. One question: is the bug deterministic or does it
happen randomly?
I'm not sure. I created an account for you yesterday and tried it
again and now I cannot reproduce the problem anymore. I don't know if
this is
On Tue, Apr 28, 2009 at 06:31:32PM +0200, Martin Michlmayr wrote:
Just for the record, I see the same problem on an amd64 system (Intel
EM64T chip).
Is this a normal installation or as part of a build process?
Thomas
--
To UNSUBSCRIBE, email to
* Thomas Weber thomas.weber.m...@gmail.com [2009-05-05 11:10]:
On Tue, Apr 28, 2009 at 06:31:32PM +0200, Martin Michlmayr wrote:
Just for the record, I see the same problem on an amd64 system (Intel
EM64T chip).
Is this a normal installation or as part of a build process?
build process.
* Martin Michlmayr t...@cyrius.com [2009-05-05 11:19]:
* Thomas Weber thomas.weber.m...@gmail.com [2009-05-05 11:10]:
On Tue, Apr 28, 2009 at 06:31:32PM +0200, Martin Michlmayr wrote:
Just for the record, I see the same problem on an amd64 system (Intel
EM64T chip).
Is this a normal
* Rafael Laboissiere raf...@debian.org [2009-05-02 17:42]:
* Luk Claes l...@debian.org [2009-05-02 14:19]:
There is only one of them really stalled on the buildd, the others just
did not get retried. It being stalled is to debug the problem and it's
kind of waiting on your input how
I am revisiting this buildd problem conerning the postinst script of the
octave3.0. I see in the buildd status page for mipsel [1], the following:
State: Building (16)
tbb (26d 00:44, 3/7, mayer) octave-communications (18d 00:24, 10/10, rem)
octave-financial (18d 00:24, 11/11, rem)
Rafael Laboissiere wrote:
I am revisiting this buildd problem conerning the postinst script of the
octave3.0. I see in the buildd status page for mipsel [1], the following:
State: Building (16)
tbb (26d 00:44, 3/7, mayer) octave-communications (18d 00:24, 10/10, rem)
* Luk Claes l...@debian.org [2009-05-02 14:19]:
There is only one of them really stalled on the buildd, the others just
did not get retried. It being stalled is to debug the problem and it's
kind of waiting on your input how to debug it AFAIK.
I am afraid, I have no idea on how to debug
Just for the record, I see the same problem on an amd64 system (Intel
EM64T chip).
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
* Martin Michlmayr t...@cyrius.com [2009-04-28 18:31]:
Just for the record, I see the same problem on an amd64 system (Intel
EM64T chip).
Thanks for your report.
This bug is driving me crazy. It seems to be a random problem and I have
no clue on how to debug this. Out of desperation, I just
This one time, at band camp, Rafael Laboissiere said:
* Martin Zobel-Helas zo...@ftbfs.de [2009-04-23 13:17]:
On Thu Apr 23, 2009 at 12:07:58 +0200, Rafael Laboissiere wrote:
I am simply lost here and have no idea on how I can debug this random
bug.
As soon as i have that bug
* Stephen Gran sg...@debian.org [2009-04-26 18:50]:
We currently have another process wedged on mayer.debian.org:
ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
ioctl(0, TIOCNXCL, {0x1000 /*
This one time, at band camp, Rafael Laboissiere said:
lsof -p 31649
COMMAND PID USER FD TYPE DEVICE SIZENODE NAME
octave-3. 31649 root cwdDIR3,3 4096 7192581
/home/buildd/build/chroot-unstable
octave-3. 31649 root rtdDIR3,3 4096 7192581
Hi,
I am contacting you guys who gave me feedback on Bug#524745. I asked
debian-admin to install octave3.0 on the sid chroot of some architectures
where the bug happened. They did it on merulo (ia64) and pescetti
(powerpc).
I can perfcetly launch octave on those machines and successfully run
Hi,
On Thu Apr 23, 2009 at 12:07:58 +0200, Rafael Laboissiere wrote:
Hi,
I am contacting you guys who gave me feedback on Bug#524745. I asked
debian-admin to install octave3.0 on the sid chroot of some architectures
where the bug happened. They did it on merulo (ia64) and pescetti
* Martin Zobel-Helas zo...@ftbfs.de [2009-04-23 13:17]:
On Thu Apr 23, 2009 at 12:07:58 +0200, Rafael Laboissiere wrote:
I am simply lost here and have no idea on how I can debug this random
bug.
As soon as i have that bug again on the buildd, i will inform you, so
wen can debug
Hi,
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 \_
On Tue, Apr 21, 2009 at 09:17:55PM +0200, Martin Zobel-Helas wrote:
Hi,
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
On Tue, Apr 21, 2009 at 11:37:35PM +0200, Philipp Kern wrote:
Maybe we guessed wrong with the kernel bug:
23:35 sgran 21:35:08.474724 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0
-opost -isig -icanon -echo ...}) = 0
23:35 sgran 21:35:08.474887 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0
* Martin Zobel-Helas zo...@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
This one time, at band camp, Rafael Laboissiere said:
* Martin Zobel-Helas zo...@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
* Stephen Gran sg...@debian.org [2009-04-21 23:55]:
This one time, at band camp, Rafael Laboissiere said:
* Martin Zobel-Helas zo...@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
* Thomas Weber thomas.weber.m...@gmail.com [2009-04-20 00:11]:
On Sun, Apr 19, 2009 at 05:47:11PM +0200, Luk Claes wrote:
Package: octave3.0
Version: 1:3.0.5-2
Severity: grave
Hi
The postinst of octave3.0 seems to hang on at least the mipsel buildds (for
unstable) [1].
Rafael Laboissiere wrote:
* Thomas Weber thomas.weber.m...@gmail.com [2009-04-20 00:11]:
On Sun, Apr 19, 2009 at 05:47:11PM +0200, Luk Claes wrote:
Package: octave3.0
Version: 1:3.0.5-2
Severity: grave
Hi
The postinst of octave3.0 seems to hang on at least the mipsel buildds (for
Package: octave3.0
Version: 1:3.0.5-2
Severity: grave
Hi
The postinst of octave3.0 seems to hang on at least the mipsel buildds (for
unstable) [1].
This issue blocks the buildds from building any other package till the
octave3.0 process (mentioned in the build log) is killed manually. This
On Sun, Apr 19, 2009 at 05:47:11PM +0200, Luk Claes wrote:
Package: octave3.0
Version: 1:3.0.5-2
Severity: grave
Hi
The postinst of octave3.0 seems to hang on at least the mipsel buildds (for
unstable) [1].
This issue blocks the buildds from building any other package till the
26 matches
Mail list logo
