Le Wed, Aug 12, 2026 at 07:10:46PM +0000, Steffen Möller a écrit : > > Charles mentioned it, the hdf5 transition kicked in. This affects a few > packages and anything downstream is then blocked. > If I have not overlooked something, then all the mostly trivial bits are gone. > @Charles, are you at something at the very moment? Do you want to guide me > (and > others) towards what is left on > https://release.debian.org/transitions/html/r-api-bioc-3.23.html ?
Hi Steffen, thank a lot for pushing the low hanging fruits out of the way. There remain a couple of packages that do not use HDF5 but I can deal with them as a background task. Regarding HDF5: upstream changed the way it vendored it, and I only could deal with it with the help of Claude. It seemed to work, but that was when Debian was shipping the same version as the one vendored. Now that Debian jumped a major version up, some tests fail and some packages fail to build. Frankly speaking, I think that the simplest is to let both transitions complete by undoing the unvendoring. Bioconductor is active and serious on security; if there are major issues they will not let their stable release be vulnerable. Also, if we are lucky, the next Bioconductor release in October might upgrade its HDF5 vendored library and give us an easier upportunity to unvendor it before Debian's next stable release. How about I ask the Release Team for their agreement? Cheers, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
