Hi Thibaut,
On 2016-11-02 09:04, Thibaut Paumard wrote:
The "long" type is 64-bit on 64-bit arches. My quick hack works only
on these. The proper fix is more involving: I have to create a custom,
opaque data type that will hold the actual hid_t.
However, overloading the comparison operator for this custom type is
not easy, so I would have to provide an API to check for the validity
of an id, and use that in the interpreted part of the code instead of
"id>=0".
I guess you are targeting the transition freeze on Friday? I don't
think I can make it. I could upload the quick hack to get this fixed
for the 64-bit arches and disable the tests on the other arches (or
get yorick-hdf5 removed from them, but that would also require an
upload of Yorick, which has a meta package that depends on
yorick-hdf5). Then I would have more time to fix yorick-hdf5 before
the hard freeze.
Yes, this plan (quick hack + temporarily disabling tests on other archs)
sounds sensible.
Thanks,
_g.
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
