[Pkg-octave-devel] backporting octave 3.2 to lenny

Thomas Weber tweber at debian.org
Wed Jan 12 20:07:35 UTC 2011

On Wed, Jan 12, 2011 at 03:55:15PM +0100, Carsten Aulbert wrote:
> Hi all
> I'm one of the admins of a largish 7000 core Debian cluster running Lenny for 
> at least the foreseeable future. However, we have users who need to have 
> octave 3.2 on several machines, thus I'm tempted to backport at least the core 
> package.
> However, I'm a bit confused about the raised build-deps as I can compile 
> octave manually on lenny, but not the squeeze source package.
> Is there a specific reason why these dependencies were raised when compared to 
> lenny?

For BLAS/ATLAS libraries: their handling changed in Debian, so a version
jump was needed to get the new behaviour. Expected influence on end
users: none.

HDF5: version jump, see

Suitesparse: there was a small patch necessary for Octave 3.0 to work
with Suitesparse 3.2, so the patch was introduced and the version
requirement encreased (otherwise the patch wouldn't work).
I'm not sure that the version requirement is necessary, actually.

libarpack: Probably due to some changes in libarpack itself, see the
changelog for the -2 upload


More information about the Pkg-octave-devel mailing list