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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
