Package: spdam
Version: 7.3.7+dfsg-1
Severity: important
The current version of sdpa/sdpam in sid build-depends/depends on the
octave3.2* packages. These packages will be removed from unstable once
the transition to the new version of octave (currently 3.6.1) will be
completed (see the wiki page of the DOG [1]).
Just changing the relationships:
Source: spda
Build-Depends: octave3.2, octave3.2-common, octave3.2-headers
Package: sdpam
Depends: octave3.2, octave3.2-common, octave3.2-headers
to:
Source: sdpa
Build-Depends: liboctave-dev
Package: sdpam
Depends: octave
would be enoguh. Notice that, since the sdpam package includes binary
*.mex files, it will depend on liboctave1 (and hence the latest version
of octave), through ${shlib:Depends}.
A final note, unrelated to the issue in this bug report: you might
install the *.m and *.mex in the Octave's path, such that the package
will work out of the box in Octave. For doing that, you can get the
paths for the *.m and *.mex files as below, and use it in debian/rules:
octave-config --print LOCALFCNFILEDIR
octave-config --print LOCALOCTFILEDIR
Rafael
[1] http://wiki.debian.org/Teams/DebianOctaveGroup
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (700, 'testing'), (650, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
