Re: octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 08:41:42AM +0300, Riku Voipio wrote: On Fri, Jun 19, 2009 at 09:49:34PM +0200, Rafael Laboissiere wrote: The octave3.2 package failed to autobuild on ia64 and is stuck on powerpc. the armel experimental buildd is again having hangings like #524745 in octave3.2 postinst. Seen so far with: octave-audio octave-ad octave-combinatorics octave-fixed octave-general I guess the individual packages don't matter that much, it hangs in octave3.2's postinst, right? Thomas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 08:03:04AM +0200, Thomas Weber wrote: On Tue, Jul 21, 2009 at 08:41:42AM +0300, Riku Voipio wrote: the armel experimental buildd is again having hangings like #524745 in octave3.2 postinst. Seen so far with: octave-audio octave-ad octave-combinatorics octave-fixed octave-general I guess the individual packages don't matter that much, it hangs in octave3.2's postinst, right? correct. It might have something to do with what packages have been unpacked before octave 3.2 postinst is run. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 09:46:59AM +0300, Riku Voipio wrote: On Tue, Jul 21, 2009 at 08:03:04AM +0200, Thomas Weber wrote: On Tue, Jul 21, 2009 at 08:41:42AM +0300, Riku Voipio wrote: the armel experimental buildd is again having hangings like #524745 in octave3.2 postinst. Seen so far with: octave-audio octave-ad octave-combinatorics octave-fixed octave-general I guess the individual packages don't matter that much, it hangs in octave3.2's postinst, right? correct. It might have something to do with what packages have been unpacked before octave 3.2 postinst is run. Can you make the build log(s) available up until the hang (I assume there is such a thing, but I'm not familiar with buildd's handling of blocking builds). If possible, for octave-audio, but I'll take whatever you have, obviously :) Thanks Thomas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 12:53:19PM +0200, Thomas Weber wrote: correct. It might have something to do with what packages have been unpacked before octave 3.2 postinst is run. Can you make the build log(s) available up until the hang (I assume there is such a thing, but I'm not familiar with buildd's handling of blocking builds). If possible, for octave-audio, but I'll take whatever you have, obviously :) experimental build logs can be found from experimental.debian.net: http://experimental.debian.net/fetch.php?pkg=octave-audiover=1.1.4-1arch=armelstamp=1248003676file=logas=raw Notice the: Build started at 20090718-0247 ... Finished at 20090719-1441 ie hanged for over 24h. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 02:04:24PM +0300, Riku Voipio wrote:
On Tue, Jul 21, 2009 at 12:53:19PM +0200, Thomas Weber wrote:
correct. It might have something to do with what packages have been
unpacked
before octave 3.2 postinst is run.
Can you make the build log(s) available up until the hang (I assume there
is such a thing, but I'm not familiar with buildd's handling of blocking
builds). If possible, for octave-audio, but I'll take whatever you have,
obviously :)
experimental build logs can be found from experimental.debian.net:
http://experimental.debian.net/fetch.php?pkg=octave-audiover=1.1.4-1arch=armelstamp=1248003676file=logas=raw
I can't reproduce this in a chroot. However, I can reproduce it
with the sbuild. both installing octave3.2 and running by hand:
octave-3.2.0-silent --no-history --no-init-file --eval pkg ('rebuild');
work just fine. But during the install of octave3.2 when doing
sbuild -d experimental octave-audio_1.1.4-1
octave hangs on the above command during postinst! notice that experimental
buildd's use a old sbuild patched for experimental:
ii sbuild10:2006.11.27-13.etch Tool for
building Debian binary packagesfro
what a heisenbug...
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [buildd-tools-devel] octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 08:26:43PM +0300, Riku Voipio wrote:
On Tue, Jul 21, 2009 at 02:04:24PM +0300, Riku Voipio wrote:
On Tue, Jul 21, 2009 at 12:53:19PM +0200, Thomas Weber wrote:
correct. It might have something to do with what packages have been
unpacked
before octave 3.2 postinst is run.
Can you make the build log(s) available up until the hang (I assume there
is such a thing, but I'm not familiar with buildd's handling of blocking
builds). If possible, for octave-audio, but I'll take whatever you have,
obviously :)
experimental build logs can be found from experimental.debian.net:
http://experimental.debian.net/fetch.php?pkg=octave-audiover=1.1.4-1arch=armelstamp=1248003676file=logas=raw
I can't reproduce this in a chroot. However, I can reproduce it
with the sbuild. both installing octave3.2 and running by hand:
octave-3.2.0-silent --no-history --no-init-file --eval pkg ('rebuild');
work just fine. But during the install of octave3.2 when doing
sbuild -d experimental octave-audio_1.1.4-1
octave hangs on the above command during postinst! notice that experimental
buildd's use a old sbuild patched for experimental:
Yes. We have included some changes to better support dependency
resolution when building experimental packages. However, we haven't
AFAIK included all the changes yet. I'll be happy to integrate them;
I just need the patches.
Is it known what the postinst is blocking on? What's happening here
that's different between the unstable and experimental sbuilds?
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`-GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
Re: [buildd-tools-devel] octave3.2 autobuild problems
On Tue, Jul 21, 2009 at 07:10:41PM +0100, Roger Leigh wrote:
On Tue, Jul 21, 2009 at 08:26:43PM +0300, Riku Voipio wrote:
On Tue, Jul 21, 2009 at 02:04:24PM +0300, Riku Voipio wrote:
On Tue, Jul 21, 2009 at 12:53:19PM +0200, Thomas Weber wrote:
correct. It might have something to do with what packages have been
unpacked
before octave 3.2 postinst is run.
Can you make the build log(s) available up until the hang (I assume
there
is such a thing, but I'm not familiar with buildd's handling of blocking
builds). If possible, for octave-audio, but I'll take whatever you have,
obviously :)
experimental build logs can be found from experimental.debian.net:
http://experimental.debian.net/fetch.php?pkg=octave-audiover=1.1.4-1arch=armelstamp=1248003676file=logas=raw
I can't reproduce this in a chroot. However, I can reproduce it
with the sbuild. both installing octave3.2 and running by hand:
octave-3.2.0-silent --no-history --no-init-file --eval pkg ('rebuild');
work just fine. But during the install of octave3.2 when doing
sbuild -d experimental octave-audio_1.1.4-1
octave hangs on the above command during postinst! notice that experimental
buildd's use a old sbuild patched for experimental:
Yes. We have included some changes to better support dependency
resolution when building experimental packages. However, we haven't
AFAIK included all the changes yet. I'll be happy to integrate them;
I just need the patches.
Is it known what the postinst is blocking on? What's happening here
that's different between the unstable and experimental sbuilds?
Well, it's not clear what causes the bug. Last time it happened on
different architectures and we have actually never found out what caused
it. It just stopped failing :)
The best guess in #524745 was something with open file descriptors.
Thomas
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: octave3.2 autobuild problems
On Fri, Jun 19, 2009 at 09:49:34PM +0200, Rafael Laboissiere wrote: The octave3.2 package failed to autobuild on ia64 and is stuck on powerpc. the armel experimental buildd is again having hangings like #524745 in octave3.2 postinst. Seen so far with: octave-audio octave-ad octave-combinatorics octave-fixed octave-general -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
octave3.2 autobuild problems
The octave3.2 package failed to autobuild on ia64 and is stuck on powerpc. This is blocking our planned transition of the octave-forge packages from octave3.0 to octave3.2 [1]. The failure on caballero is due to the infamous alternatives problem [2] but nobody seem to care. I wish I could ask for this: gb octave3.2_3.2.0-2 . ia64-but-please-not-on-caballero but I guess that the syntax is wrong. ;-) OTOH, the problem with powerpc seems to be easier to fix. I have asked for a dep-wait in the past [3] but I think it is wrong now, since arpack_2.1+parpack96.dfsg-2 has migrated into testing. Please, could the dep-wait be removed or the following be done: gb octave3.2_3.2.0-2 . powerpc 1: http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2009-June/006308.html 2: http://lists.debian.org/debian-wb-team/2009/06/msg00058.html 3: http://lists.debian.org/debian-wb-team/2009/06/msg00017.html Cheers, -- Rafael -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: octave3.2 autobuild problems
On Fri, Jun 19, 2009 at 09:49:34PM +0200, Rafael Laboissiere wrote: The octave3.2 package failed to autobuild on ia64 and is stuck on powerpc. This is blocking our planned transition of the octave-forge packages from octave3.0 to octave3.2 [1]. The failure on caballero is due to the infamous alternatives problem [2] but nobody seem to care. I wish I could ask for this: gb octave3.2_3.2.0-2 . ia64-but-please-not-on-caballero but I guess that the syntax is wrong. ;-) I've given it back, let's see if we're lucky. OTOH, the problem with powerpc seems to be easier to fix. I have asked for a dep-wait in the past [3] but I think it is wrong now, since arpack_2.1+parpack96.dfsg-2 has migrated into testing. Please, could the dep-wait be removed or the following be done: gb octave3.2_3.2.0-2 . powerpc Done that. Kurt -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [Pkg-octave-devel] octave3.2 autobuild problems
* Kurt Roeckx k...@roeckx.be [2009-06-19 23:48]: On Fri, Jun 19, 2009 at 09:49:34PM +0200, Rafael Laboissiere wrote: The octave3.2 package failed to autobuild on ia64 and is stuck on powerpc. This is blocking our planned transition of the octave-forge packages from octave3.0 to octave3.2 [1]. The failure on caballero is due to the infamous alternatives problem [2] but nobody seem to care. I wish I could ask for this: gb octave3.2_3.2.0-2 . ia64-but-please-not-on-caballero but I guess that the syntax is wrong. ;-) I've given it back, let's see if we're lucky. Yes, mundy picked it! https://buildd.debian.org/~luk/status/package.php?suite=p=octave3.2a=ia64 Boy, developing Debian packages these days has become so thrilling as playing poker in a Casino or buying a lottery ticket. :-) Thanks, -- Rafael -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
