Your message dated Fri, 25 Sep 2009 16:58:26 +0200
with message-id <20090925145826.ga16...@mithrandir>
and subject line Re: Bug#543871: Netcdf3 vs Netcdf4
has caused the Debian Bug report #543871,
regarding libnetcdf-dev: installs older header files instead of version 4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
543871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnetcdf-dev
Version: 1:3.6.2-3.1
Severity: grave
Justification: renders package unusable


I'm trying to compile/install the python netcdf4 package,
from http://code.google.com/p/netcdf4-python/.  building it
requires the -dev packages for hdf5 and netcdf4.  I have
installed libnetcdf4 1:3.6.2-3.1 and libnetcdf-dev 1:3.6.2-3.1

the script complains about not being able to find the netcdf4 development
files.

so I compare the /usr/include/netcdf.h
installed by the libnetcdf-dev, with the two from
http://www.unidata.ucar.edu/downloads/netcdf/ftp/netcdf-4.0.1.tar.gz,
and this is what I see:

ma...@croese:~/Local$ diff -U3 /usr/include/netcdf.h netcdf-4.0.1/libsrc/ | 
grep "^[\+\-]" | wc
     57     230    1584
ma...@croese:~/Local$ diff -U3 /usr/include/netcdf.h netcdf-4.0.1/libsrc4/ | 
grep "^[\+\-]" | wc
   1120    6152   41895

did I misunderstand the meaning of the package?
how do I get the correct headers (short of installing them by hand)?

thanks,
Mario

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.30-1-powerpc
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libnetcdf-dev depends on:
ii  libc6-dev [libc-dev]         2.9-24      GNU C Library: Development Librari
ii  libnetcdf4                   1:3.6.2-3.1 An interface for scientific data a

Versions of packages libnetcdf-dev recommends:
ii  netcdf-doc                   1:3.6.2-3.1 Documentation for NetCDF

Versions of packages libnetcdf-dev suggests:
ii  gfortran                      4:4.3.3-9  The GNU Fortran 95 compiler
pn  netcdf-bin                    <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Package: libnetcdf-dev
Version: 4.0.1-1

This wishlist is actually fixed in _experimental_, where a new netcdf package
is now available for 4.0.1. Of course you have to use a versioned 
build-dependency
on libnetcdf-dev (>= 4.0.1) to build python-netcdf4. It is due for unstable
in a few weeks, if all tests will proceed sane.

Cheers.

On Tue, Sep 22, 2009 at 04:19:23PM +0200, Francesco P. Lovergine wrote:
> On Tue, Sep 22, 2009 at 03:27:48PM +0200, Mario Frasca wrote:
> > Francesco P. Lovergine wrote:
> > >'4' refers to the current SONAME and C API version which is 4.0.0, it has 
> > >nothing to share
> > >with the library version. The 4.0.1 version for instance uses 1.0.0 for 
> > >the so-called '4' interface,
> > >5.0.0 for C++/Fortran and 6.0.0 for C libraries respectively.
> > too many apparently random numbers in this explaination...
> > 
> > you are saying that libnetcdf4 is based on upstream NetCDF 3.6.2 and
> > it is not the library providing NetCDF 4 and that libnetcdf-dev is
> > in fact the development version of libnetcdf4, aren't you?
> > 
> > but then...
> > 
> > - libnetcdf-dev drops the last character of its base library before
> > appending '-dev'!
> 
> Yes, it is the default -dev library for the current default netcdf library,
> which is currently libnetcdf4. This is by policy to allow library migrations,
> we do not distribute multiple versions of the library if it can be avoided.
> Please, read Debian Policy and docs about library packaging.
> 
> > - how will we call the library implementing NetCDF 4(.0.1)?
> > 
> 
> libnetcdf6 using the C library soname for the whole set. Keep in mind that
> APIs can change fastly then releases and that's perfectly sensed.
> 

-- 
Francesco P. Lovergine


--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

Reply via email to