Re: netcdf Transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 13/07/2015 12:50, sebastic wrote:
> On 2015-07-13 13:40, Alastair McKinstry wrote:
>> So, whats the current status of the netCDF transition?
>
> We still need to verify all reverse dependencies before we can request
a transition slot.
>
> Ross was working on this, but he's on vacation now. No one else is
actively testing the reverse dependencies AFAIK. I'm not going to start
with that before getting the gdal & spatialite transition done. If you
want to help with the netcdf transition verify all reverse dependencies
with the new netcdf, netcdf-cxx, netcdf-cxx-legacy & netcdf-fortran
packages.
>
>> All the netcdf-* packages appear to build, are there outstanding bugs or
>> should we just kick off the transition?
>
So, to start with I've tested and built my packages, either in unstable
or experimental:
adios
cdftools
cmor
exodusii
ferret-vis
grads
magics++
oasis3
cdo
# metview
ncl
metview still has an RC bug that should be fixed today.
Of these, cdo and metview are in the auto-grib-api transition. This
hopefully will transition 5 days
after metview hits unstable.
regards
Alastair
> Kind Regards,
>
> Bas
- --
Alastair McKinstry, <alastair@sceal.ie>, <mckinstry@debian.org>,
https://diaspora.sceal.ie/u/amckinstry
Software is like Poetry - most of it shouldn't have been written.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVsKdLAAoJEMvmu05dmtOlMssP/3DR2EI29p6g1wBjzjUqnyqC
hyBsbOQObTTkouFY4HgVqX2imtvbWdQbDBk7fBjVT6sKnmTjBq+ZvEiU24NnMWTc
8IsVqvbRHUwJdOH94deS5XuzlcTwhilf43SJjcn1KrTQG3HzhDwspTOAa9NNrdzQ
Ej6F73LUv4AfsuhHLhLB9zPXRPNEvMnIPoQVXfN8Cg2AcyDqDHw/0M0xQT3XeaLH
sx9m4cn4lpcJoxI2dRP51h1KOi5xxcRQ2hSMh8iK74eGpF2Tlh5g/C0VsPEtnsjt
PteJwGdELO/wLXUA9I1Edudozhg5M9N3WgK+zYBFD4pzoUj+3t67PAmI78wvZlZi
DeeWImLCORt7K26pcrxAw4Ceb/2hlwNjgVfYhyEsDGU2boYWQJj3LLMGulr7ffeV
VZByE1y+F9T/JV3bmcgzi39cQNf8JNOlK2Fjwznx2BJ0vbX9wyiSeWAUOi1GqvC1
n2txe+fxdbQsiK645SZRjYNaQl6wOezuEbMcyL73XRlAICdgAjDxo7ViM/ge+9j6
Outlkol6OzljDKiZsiKW+VScetxTNIIGQ82JlLZr/cN6dVzcYI+EqX0tFIjgXMJ5
+ruWL4doqH6vasQTs0NYG0Kl83LZU+C4w/TiXr72g9PjMQTz1QuShZaOqTMvs5JJ
Cibfs4GRXRqXTdC5Y0qq
=5tcU
-----END PGP SIGNATURE-----
Reply to: