[Pkg-octave-devel] BTS status for the DOG

[Rafael Laboissiere]

The bug hunting season is over for now.  In the last days, I have closed
8 bug reports regarding the DOG packages.

Here is the current situation (according to
http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=pkg-octave-devel@lists.alioth.debian.org):

Severity: grave
    * #319618: octaviz: vtk_init undefined

Severity: serious
    * #302688: octaviz: FTBFS (amd64/gcc-4.0): cast from
          'vtkObjectBase* 'to 'unsigned int'loses precision
    * #310226: octave2.9: FTBFS: linking a shared lib to a static lib fails.

Severity: important
    * #300576: octaviz: FTBFS on 64 bit arches: reinterpret_cast from
           `vtkObjectBase*' to `nsigned int' loses precision

Severity: normal
    * #302034: octave-forge: command 'legend' fails on first call and works afterward
    * #304162: vtk_init does not work because liboctaviz is in a wrong place
    * #304368: octave2.9 depends on obsolete version of atlas

Severity: normal
    * #293235: octave2.1-emacsen: hangs Emacs
    * #295395: octave-forge: Replacing a submatrix of a sparse matrix results in a full matrix

Severity: minor
    * #324471: octave2.1-emacsen: problems if octave startup file contains cd()

Severity: wishlist
    * #253188: octave2.1: Keyword end confuses octave-mode.el


We are out of hope as regards the octaviz bugs (#319618, #302688,
#300576, and #304162), because this package fails to compile with g++
4.0.  This is getting fixed upstream and we will probably have to wait
until libvtk5 is released.

Five bugs reports regard octave2.9 and/or will be fixed when this version
will become octave3.0: #310226, #304368, #295395, #324471, and #253188.

The two other bugs left (#293235 and #302034) are tagged upstream, but it
does not seem to exist trivial fixes for them.  These bug reports may
stay open for a while.  We can simply ignore them or even tag them
"wontfix".

Help on fixing these remaining bugs is welcome.

-- 
Rafael