[Pkg-octave-devel] Octaviz autobuilder problem

[Thomas Weber]

Hi, 


Am Freitag, den 20.01.2006, 16:23 +0100 schrieb Rafael Laboissiere:
> The questions are: why is the octave-config alternative set to manual and
> why is it pointing to octave-config-2.1.71 instead of
> octave-config-2.1.72?  This must have something to do with a previous
> version of the octave2.1 package that did not cleaned up properly the
> alternative.
I think it was the introduction of octave2.9. 
Reason: the invalid link has a date of Nov, 3 (you might want to look at
the build logs for s390 -- afaik, there's only one buildd for unstable
for that), which corresponds  to that introduction.


> I can imagine two ways of fixing this bug:
> 
> 1) The "ducking approach": patch CMakeLists.txt to use
>    /usr/bin/octave-config-2.1.72 explicitly. 
Not good. There's at least one package using Octave which is not under
DOG's control (h5utils).

> 2) The "brute force" approach: get the autobuilder admins to clean up the
>    octave-config alternative on each machine.
That's probably what's needed. If i understand Debian's build system
correctly, it means cleaning up the chroot, which should not be *that*
difficult.
 
> Should we ask this at debian-devel?
I'd say yes -- maybe someone has a simpler idea.

	Thomas