[Pkg-octave-devel] octave2.1-forge ready?

[Thomas Weber]

Am Mittwoch, 18. Juli 2007 12:13:12 schrieb Cyril Brulebois:
> Rafael Laboissiere <rafael at debian.org> (17/07/2007):
> > Actually, the best way for us to evaluate your changes is by having
> > them in SVN.  Do not be afraid of doing broken commits, we can always
> > revert them.
>
> Alright, I think I'm done with octave2.1-forge, which builds fine in
> pbuilder. Some remarks:
>  + I: octave2.1-forge: arch-dep-package-has-big-usr-share 4516kB 44%
>  + I: octave2.1-forge: hyphen-used-as-minus-sign
> usr/share/man/man1/mex2.1.1.gz:33 + I: octave2.1-forge:
> hyphen-used-as-minus-sign usr/share/man/man1/mex2.1.1.gz:34
>
> I won't do any split until I'm more confident with DOG packages, but it
> might be worth to think about it.

Generally, you are right. In this specific case, it's unimportant. Octave2.1 
is going to die pretty soon (as soon as we have switched all dependending 
packages to 2.9).

Sorry for your time, I thought you'd know that[1]

So, as a warning: don't spend time with octave2.9-forge. We hope to get rid of 
it soon (and even if not, due to upstream changes, it will be split into 
several packages). 

> The end of the build logs contains many occurrences of:
> > dpkg-shlibdeps: warning: format of 'NEEDED liboctinterp.so' not
> > recognized

That's okay, the Octave interpreter knows where to find its own libraries. 


> which was due to:
> > checking for mkoctfile... mkoctfile2.1
> > collect2: ld terminated with signal 11 [Segmentation fault]

Huh, a segfault when running a bash script?

[1] Then again, who knows how long other packages in Debian will want to 
continue using 2.1.

Thanks
	Thomas