On Wed, Sep 2, 2015 at 14:49:18 +0200, Sebastiaan Couwenberg wrote: > On 02-09-15 14:37, Gilles Filippini wrote: > > Gilles Filippini a écrit le 28/08/2015 00:12 : > >> Sebastiaan Couwenberg a écrit le 27/08/2015 10:17 : > >>> I suggest to reassign the hdf5 transition issue back to > >>> release.debian.org, because I would also like to see a single > >>> hdf5 transition instead of two (I made the same decisions for > >>> netcdf & geos). > >> > >> Yes, I'll do that *after* having the rdeps checked to avoid > >> useless ping pong game. I've started tracking progress on > >> titanpad[1] in case anybody wants to help. > >> > >> [1] <https://titanpad.com/gpirV5ouad> > > > > I've tested a rebuild of all 68 rdepends reported on the auto-hdf5 > > transition page [1]. Only 5 of them aren't binnmu OK: > > > > [...] > > > > To me, HDF5 1.8.15 is now transition ready. > > Thanks for your work preparing the hdf5 transition, I'd say upload to > unstable as soon as possible. We should have done hdf5 before netcdf. > > The libvigraimpex transition (#794736) can then start triggered by the > hdf5 transition. > Hrm. Do I see correctly that hdf5 1.8.15 bumps SONAME of the C library? If so, that MUST NOT be uploaded to unstable before the C++ fun is over. If a transition is needed for the C++ lib, that must be done separately and ahead of the switch to 1.8.15. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature