Hi Rafael,
Thanks for the patch! I would need to adjust it though so I could
easily build backports of the package across debian/ubuntu releases:
http://neuro.debian.net/pkgs/libgdf-dev.html
probably in a way similar to what I have done for ptb-3:
https://github.com/neurodebian/psychtoolbox-3/blob/debian/debian/rules#L99
override_dh_makeshlibs:
dh_makeshlibs
: # Provide Octave:Depends
[ -e /usr/bin/octave-depends ] \
&& octave-depends \
|| echo 'octave:Depends=octave (>= 3.4.3-1~)' >>
debian/octave-psychtoolbox-3.substvars
do you foresee any complications from such a solution?
On Mon, 02 Apr 2012, Rafael Laboissiere wrote:
> Package: octave-gdf
> Version: 0.1.2-1
> Severity: important
> Tags: patch
> The current version of libgdf in sid 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]).
> The libgdf package needs octave3.2-headers for including the makefile
> fragment defs.make and for calling the octave-depends script that makes
> the substitution of ${octave:Depends}. These files have been dropped in
> the Debian packaging of Octave 3.6.1.
> I am attaching below a patch for fixing the issues in this bug report.
> The patch was obtained through debdiff. I added the corresponding entries
> to debian/changelog. The octave-gdf package should now simply depend on
> octave. Note that the octave-gdf package will, in fine, depend on
> liboctave1, which will pull the appropriate version of octave (3.6.1-4,
> currently).
> I also added the files octave-gdf.docs and octave-gdf.examples to the
> debian/ directory for installing the functions documentation and the
> provided examples. I think that these are useful additions.
> Rafael
> [1] http://wiki.debian.org/Teams/DebianOctaveGroup
--
=------------------------------------------------------------------=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
