. side note, I found this interesting:
##===========================
dbb=# select * from dsc_bdepends where bdepends ~ 'hdf5' order by
bdepends, dsc_name, ppa_name;
ppa_name | dsc_name |
bdepends | bd_constr
-------------- --------------------------------------
---------------------------------------------- -------------
stable_dsc | gdal_1.11.2 dfsg-1~exp2~trusty | libhdf5-dev
| (>= 1.8.8)
unstable_dsc | gdal_1.11.2 dfsg-1~exp2~trusty | libhdf5-dev
| (>= 1.8.8)
testing_dsc | gdal_2.0.2 dfsg-5~trusty0 |
libhdf5-dev | (>= 1.8.8)
testing_dsc | gdal_2.1.0 dfsg-1~trusty0 |
libhdf5-dev | (>= 1.8.8)
testing_dsc | gdal_2.1.0 dfsg-1~trusty1 |
libhdf5-dev | (>= 1.8.8)
testing_dsc | gdal_2.1.0 dfsg-1~xenial0 |
libhdf5-dev | (>= 1.8.8)
unstable_dsc | insighttoolkit4_4.5.2-1otb3~trusty2 | libhdf5-dev
| ()
stable_dsc | cartopy_0.11.0-0~trusty1 |
libhdf5-serial-dev | ()
stable_dsc | gdal_1.10.0-1~precise1 |
libhdf5-serial-dev | (>= 1.6.6)
testing_dsc | gdal_1.10.0-1~precise1 |
libhdf5-serial-dev | (>= 1.6.6)
unstable_dsc | gdal_1.10.0-1~precise2 |
libhdf5-serial-dev | (>= 1.6.6)
unstable_dsc | gdal_1.6.1-1~intrepid1 |
libhdf5-serial-dev | ()
stable_dsc | gdal_1.9.2-2~precise4 |
libhdf5-serial-dev | (>= 1.6.6)
unstable_dsc | insighttoolkit4_4.6.0-3otb2~precise1 |
libhdf5-serial-dev | ()
unstable_dsc | insighttoolkit4_4.6.0-3otb2~trusty1 |
libhdf5-serial-dev | ()
unstable_dsc | insighttoolkit4_4.7.1-1otb1~precise1 |
libhdf5-serial-dev | ()
stable_dsc | insighttoolkit4_4.7.1-1otb1~trusty1 |
libhdf5-serial-dev | ()
unstable_dsc | insighttoolkit4_4.7.1-1otb1~trusty1 |
libhdf5-serial-dev | ()
stable_dsc | iris_1.6.1-0~trusty2 |
libhdf5-serial-dev | ()
stable_dsc | python-netcdf4_1.1.0-0~trusty1 |
libhdf5-serial-dev | (>= 1.8.4~)
(20 rows)
On Wed, 11 May 2016 07:52:50 0200, Sebastiaan Couwenberg
<[email protected]> wrote:
On 05/11/2016 05:50 AM, Brian M Hamlin wrote:
How can I check the versions of the netCDF stack as things progress ?
That depends. The latest versions available in Debian and upstream are
included in the Debian GIS DDPO:
https://qa.debian.org/[email protected]&comaint=yes&version=oldoldstable
Where can I make a pull-request for a trivial change to a package .dsc ?
Package dsc files are generated so changing them makes no sense. You can
discuss changes to the netcdf source packages on the debian-gis list [0]
and/or file a bugreport for the package in question [1].
[0] https://lists.debian.org/debian-gis/
[1] https://www.debian.org/Bugs/Reporting
What is a good way to trace UbuntuGIS - testing PPA versions for
python-netcdf4 -> netcdf-c -> lib hdf5
(there are several, how would *you* do it ) for our next dev-cycle..
Define "trace".
If you're looking for the interdependencies I would parse the Packages
files from the PPA and analyse the Depends fields of the packages in
question.
Because I have coordinated the recent netcdf transitions, I have a
pretty good idea of the dependency chain.
netcdf-c (netcdf source package) is at the bottom, everything else
depends on that. netcdf-cxx-legacy, netcdf-cxx, netcdf-fortran &
netcdf4-python all require the netcdf package to build. netcdf in turn
requires hdf5 to build.
To help prepare transitions, I run a transition tracker [2] using the
ben package [3] also used for Debian [4] & Ubuntu [5]. ben visualizes
the reverse dependencies for packages and marks them as good or bad
based on the regular expressions applied to the fields in the Packages
files (usually just Depends).
[2] http://linuxminded.nl/tmp/pkg-grass-transitions/html/netcdf-c.html
[3] https://tracker.debian.org/pkg/ben
[4] https://release.debian.org/transitions/
[5] https://people.canonical.com/~ubuntu-archive/transitions/
Where is a convenient place to file an update ticket : "netCDF4
project home page has moved from code.google.com to
github.com/Unidata; update source description"
Convenient != Appropriate
You should file bugreports in the tracker for the repository in
question, in this case UbuntuGIS/OSGeo-Live.
If you verify that the issue is also present in the packaging maintained
by the Debian GIS team, you can contact the Debian GIS team via the
mailinglist or file a bugreport for the package in question.
dsc content:
stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Homepage |
http://code.google.com/p/netcdf4-python/
make sense ? thanks
That looks like the python-netcdf4 source package from OSGeo-Live 9.5,
it is maintained by The Mer <[email protected]> according to its
control file.
It is not maintained by the Debian GIS team, the netcdf4-python package
is maintained by the Debian GIS team and included in Debian & Ubuntu. It
does not have these issues.
Regarding NetCDF & Python, only the python{,3}-netcdf4 packages built
from the netcdf4-python source package are actively maintained. The
python-netcdf package built from the python-scientific package as used
by bin/install_jupyter.sh is very problematic. It does not support newer
NumPy versions and has been broken in Debian for quite a while and has
recently been removed from Debian because it was keeping the old NetCDF
4.1.3 packages in Debian unstable (due to being unable to build with the
newer versions). [6]
These issues with python-scientific also caused it to be removed from
Ubuntu xenial, so bin/install_jupyter.sh needs to be updated to not
require python-netcdf any more.
[6] https://lists.debian.org/debian-gis/2016/05/msg00009.html
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
--
Brian M Hamlin
OSGeo California Chapter
blog.light42.com
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
