[Pkg-octave-devel] Bugs in octave2.1

Thomas Weber thomas.weber.mail at gmail.com
Fri Jan 2 18:59:21 UTC 2009


On Fri, Jan 02, 2009 at 06:02:50PM +0100, Rafael Laboissiere wrote:
> New year comes and it is time for some cleanup.  I started doing some triage
> on the bug reports filed against the DOG packages.  For octave2.1, we have
> the following open bug reports:
> 
>       #505373 FTBFS with GCC 4.4: missing #include
>       #477348 octave2.1: documentation of randn lacking detail
>       #367165 octave2.1: please put runtime libraries in /usr/lib, not /usr/lib/octave-VERSION
>       #348480 polyfit breaks down over "large" x values
> 
> The first two bugs are tagged wontfix and we should just ignore them.
> On the other hand, bugs #367165 and #348480 also apply to octave3.0 and
> should not disappear when octave2.1 will be dropped from Debian after the
> release of lenny.  Should we reassign those bug reports to octave3.0?

Yes. #348480 is fixed in the development branch (3.1), but won't make it
into the 3.0 branch (change of algorithm). Hmm, that makes me wonder
whether we shouldn't close it and point people to the 3.1 branch.

I'm reluctant about #367165. Putting the libraries into /usr/lib means
we need a SONAME. Octave doesn't version the SONAME currently. I've
looked into this quite some time ago, but we would need to introduce
both automake and libtool into Octave. That would be a huge patch,
touching about every Makefile.

	Thomas



More information about the Pkg-octave-devel mailing list