Dear RMs it is now time to start with a transition of HDF5 library in unstable, after months of permanence in experimental. The 1.8.3 is built in 1.6 compatible mode, so it should not require changes to sources.
Dependent maintainers for libhdf5-serial-1.6.6-0: Gürkan Sengün <[email protected]> (gnudatalanguage) Helen Faulkner <[email protected]> (labplot) Gerber van der Graaf <[email protected]> (libgpiv pygpiv) Debian PhotoTools Maintainers <[email protected]> (pfstools) Bradley Smith <[email protected]> (mathgl) Alastair McKinstry <[email protected]> (cdo) Debian GIS Project <[email protected]> (gdal h5utils mapserver) Debian Science Team <[email protected]> (ecs libcgns) Thorsten Alteholz <[email protected]> (meep) Josselin Mouette <[email protected]> (tessa) Aurelien Jarno <[email protected]> (med-fichier) Debian Octave Group <[email protected]> (dynare octave3.0 octave3.1 octave3.2 octave-ad octave-ann octave-audio octave-combinatorics octave-communications octave-econometrics octave-fixed octave-ftp octave-general octave-graceplot octave-gsl octave-image octave-io octave-linear-algebra octave-miscellaneous octave-multicore octave-nan octave-nlwing2 octave-nurbs octave-octcdf octave-octgpr octave-odepkg octave-optim octave-optiminterp octave-parallel octave-pdb octave-secs1d octave-secs2d octave-signal octave-sockets octave-specfun octave-symband octave-symbolic octave-triangular octave-xraylib semidef-oct) Dirk Eddelbuettel <[email protected]> (r-cran-hdf5) Debian Scientific Computing Team <[email protected]> (paraview) Debian QA Group <[email protected]> (mpb) Thibaut Paumard <[email protected]> (yorick-hdf5) Francesc Altet <[email protected]> (pytables) Andrew Ross <[email protected]> (plplot) They already depend on libhdf5-serial-dev, so a simple rebuild should suffice for a smooth transition. If you had not concerns about, I would upload in sid the hdf5 1.8.3 ASAP. Note that upstream moved to a proper SONAME support, so distributed new libraries will drop debian-specific versioning in their names, still used in 1.6 series. All that should be transparent to other packages. ----- Forwarded message from "Francesco P. Lovergine" <[email protected]> ----- Date: Fri, 13 Mar 2009 22:56:57 +0100 From: "Francesco P. Lovergine" <[email protected]> To: [email protected], Debian-Med Packaging Team <[email protected]>, Debian Octave Group <[email protected]> Subject: Re: [DebianGIS] HDF5 changes User-Agent: Mutt/1.5.18 (2008-05-17) On Fri, Mar 13, 2009 at 10:16:37PM +0100, Francesco P. Lovergine wrote: > In the incoming weeks HDF5 libraries should also be updated. As you > could already known HDF Group is supporting both 1.6 (legacy) and > the new 1.8 series, which are not full compatible each other. > Applications that currently supports HDF5 1.6 > could need a source update as detailed in > http://www.hdfgroup.org/HDF5/faq/bkfwd-compat.html for both some > structures and API functions. > > My own idea is migrating hdf5 source package to 1.8.2 and simply > drop 1.6 support. The new package will be available for a while > in the experimental staging area, before uploading to unstable. > Of course, you should check in the meantime if your source > package needs updating and possibly provide a patch. > > If you had problems with this updating plan, please give > a feedback as soon as possibile. > > Note that HDF5 1.8.1+ is a pre-requisite for NetCDF-4, so a > new transition will need to be considered on that side > in a not so far future. > Some clarifications: I mean that the 1.6 legacy libraries will be dropped, but the 1.8 will be used in compatibility mode anyway. http://www.hdfgroup.uiuc.edu/HDF5/doc_1.8pre/doc/RM/APICompatMacros.html The _default_ profile will be choosen at compile time, which will provide 1.6 as default API, with 1.8 available by explicit call. Cheers. -- Francesco P. Lovergine _______________________________________________ Pkg-grass-general mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general ----- End forwarded message ----- -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
