Hi, Gilles Filippini a écrit , Le 25/11/2013 18:40: > Sylvestre Ledru a écrit , Le 25/11/2013 18:17: >> If someone wants to step in to help on HDF5, he/she is more than welcome. >> >> I am planning to maintain it but help is welcome. >> For example, some tasks which should be done: >> * fix the git repository (git import-orig ../hdf5_1.8.12.orig.tar.gz fails >> with conflicts) >> * package the new upstream release (1.8.12) /!\ in the release 11, the >> SONAME was wrongly changed >> to 8 for no real reason. We should check if the 8 is deserved or not. >> * backport the arm64 ubuntu changes > > I step in. I'll start with the git stuff.
I've successfully imported and merged the new upstream release. There were no conflicts at all. I've also refreshed the patch set and achieved a first successful build. At this stage I'd like to push my changes to alioth. I applied yesterday for pkg-grass membership for this purpose. I'm now in the process of updating the symbol files, and I'm a bit puzzled by the many '#MISSING: 1.8.x# flags present in libhdf5-mpich2-7.symbols and libhdf5-openmpi-7.symbols. Shouldn't removed symbols bump the SONAME? There are also a lot of '(optional)' and '(arch xxx)' tags. What are the rationals for setting them? Thanks in advance, _g.
signature.asc
Description: OpenPGP digital signature
