Bug#791067: hdf5: library transition may be needed when GCC 5 is the default
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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.
Kind Regards,
Bas
- --
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJV5vBGAAoJEGdQ8QrojUrxulwQALkLgANyJbCHpR3HSI3Ciobv
qeQINp7NutMZHUi5uQvkgG7415QD6Ql1Xhboh/UHeBGVBGMgKT7oeu5k8pnwBVEu
e5oyVmCZqmAu3lA9b8pR0vU1VWLLBnyPpRl9hhw+T7xqF4Xv/jeDrIwontoexq98
rdTwSlp3L6+EOoCTSFyL6ZGn0acwWwtLUJfxBktu4HOO3lGBv2y+t/sPxObTxYam
h3AXxQt6JP7QSgjyGYj2kgS7BeKZFAQO9/+OhTmWA8kmiDaveiT3PV7JgBeqEern
MYRmvpuYAv2n0XEKdy7srq+MY3C+Z2WQqQL5AXo4rRQjPGTm/Et8Kq/9uI3CT8cb
Zr6JM1Bun8gKewj9EVXevQP6Ix0BrAX2uif7I8FxdWDpNmBarm4cR91VvBfTfRrX
JuRR7z2aaV85UkBr+8dw+QVwvfEIJteRBf/WrwqjZcn8vslEzovwYTaHrWurhjm6
+VArrqJWpi8JDqBVmn6Eb9ABtow06nrbiwzaa0oyZ7ukXLU0Aw0Rw6Zh9j3hSOUr
kJ2lnUV7jiBoEReE8Hekf6TI9nmztiMF7ONhIzuVPD9dcXK83VMiR6rau4cwYr4m
ohMyWUHf4V0WYClre1ChBtw4Ml0CRLaLNJNpMx2yByhC4FSLSEmq1loKxOzSakIU
alfeXrlopLQeCxd7FUUw
=LACr
-----END PGP SIGNATURE-----
Reply to: