Package: src:h5utils
Version: 1.12.1-1
Severity: important

The current version of h5utils build-depends on octave3.2-headers.  This
later package 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]).

Simply changing the build-dependency from octave3.2-headers to
liboctave-dev fixes the issue.

Two additional comments, that are not really related to the bug reported
here but are worth mentioning (tell me if you prefer that I file
separated bug reports for the points below):

1) You might add "Suggests: octave" to h5utils.  This would give an
indication to the users that there is an Octave plugin included in the

2) On my i386 system, the h5read.oct file is installed in:


Notice that this is a versioned path.  This means that the script will
not be in the Octave path if the octave package is upgraded upstream
(unless the user explicitly include it via addpath).  Actually, the
directory above is reserved for the pristine Octave files, not really
appropriate for plugins.

This path is obtained by the following code in

    OCT_INSTALL_DIR=`octave-config --oct-site-dir
Plugins should be installed in one of the following paths (the example
below is shown is for the i386 architeture):

    $ octave-config --print LOCALOCTFILEDIR
    $ octave-config --print LOCALAPIOCTFILEDIR
Note that the last one has the API number, which may be (or not) a good



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


Pkg-grass-devel mailing list

Reply via email to