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
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
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) availabl
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
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 s
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-f
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 octave
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-combinator
On Fri, Jun 19, 2009 at 09:49:34PM +0200, Rafael Laboissiere wrote:
> The failure on caballero is due to the infamous alternatives problem [2] but
> nobody seem to care. I wish I could ask for this:
> 2: http://lists.debian.org/debian-wb-team/2009/06/msg00058.html
I'll go fix caballero tonight -
* Kurt Roeckx [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].
> >
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 inf
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 fo
12 matches
Mail list logo
