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

[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.

Hyphens are not that important at the moment, let's solve FTBFS's first.

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

but it looks quite similar to the build logs available on
buildd.debian.org, so I guess it's OK.

And at last, I'll try to keep an eye on:
> 2006.03.17+dfsg1-4 (mips) (latest build at May 9 19:37: maybe-failed)

which was due to:
> checking for mkoctfile... mkoctfile2.1
> collect2: ld terminated with signal 11 [Segmentation fault]
> configure: error: Could not run mkoctfile2.1
> make: *** [config.status] Error 1

Cheers,

-- 
Cyril Brulebois
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20070718/007f01f9/attachment.pgp