Hello ! 
This week was my first ever +1 Maintenance week.
I mainly focused on the almost finished hdf5 transition.
hdf5 transition - Ubuntu uploads
- LP: #2167933: openms: FTBFS in stonking-proposed with hdf5 2.2
openmspackage failed to build with hdf5 new version. Just a linking error, with cmake script needing a small update. Added a patch (still waiting for sponsoring) and forwarded to Debian #1148933. - LP: #2167945: uncalled: FTBFS in stonking-proposed with hdf5 2.2
uncalledFTBFS as well with the new hdf5 version. Another linking error, easily fixed. Uploaded the patch - LP: #2168474: sync uncalled from Debian unstable
Before I was able to send the previous patch to Debian, they also fixed the issue. On top of that, uncalled autpkgtests were failing, because of an hdf5 regression, that the Debian maintainer chose to patch directly in the uncalled test suite. Syncing was the right move to unblock and get rid of the delta. - LP: #2168435: hdf5 2.2.0 fails to read legacy fast5 files
This is the hdf5 regression that affected uncalled autopkgtests. We don’t know wether this was an explicit upstream choice to stop supporting those legacy files, but it does not seem so. I prepared a patch and forwarded it upstream. We will wait for their answer to see if we upload or drop the patch. - LP: #2168438: h5py: FTBFS on armhf in stonking -proposed
This seems like a regression in h5py from an ancient error. I have adapted a patch (still waiting for sponsoring) from the old issue. In the meantime, @doko uploaded a workaround to allow the build to pass, so not a blocker for the transition anymore. - LP: #2167946: ufo-filters: FTBFS on stonking-proposed
Another FTBFS with linking and library finding error. Added two patches that are uploaded. Forwarded to Debian.
Misc Ubuntu uploads
- LP: #2167827: jest/schemas fails to load with typebox 0.34
Provided a small patch to unblock autopkgtests on some node package that failed with newtypebox 0.34in proposed. Already fixed in Debian, patch backported from there (a sync was not possible, as they have already moved to a newer version ofnode-babel). - LP: #2167851: gromacs: FTBFS in stonking-proposed
gromacspackage was FTBFS as well in proposed. This is an issue already solved in upstream/main, but it is a large refactor. Instead I used a workaround patch to fix the issue. Unfortunately, there was another issue with the build due to what I think is a compiler regression currently in-proposed. I will retry the build in PPA and ask for sponsorship once everything is green.
Conclusion
That was a dense week! I hope I was able to help with this transition and it will finally be done. I thought this would be the case, but as I write this message it seems another package has a failing autopkgtest on armhf… We will see. There is always more work 
Many thanks to @ginggs, @lvoytek for review and sponsoring, and @doko for helping with the transition!