Hi, It seems the htslib ecosystem upgrade to version 1.21 stalled.
Andreas, I hope you don't mind I follow up by email to your question on #debian-med:matrix.org? I felt more comfortable analysing the issue closely than throwing a quick answer in the chat: > The [pysam issue] was closed but there is no new release. Do > we want to fetch the according patch or rather pinging for the > promised new upstream release? > > [pysam issue]: https://github.com/pysam-developers/pysam/issues/1317 I begun to dig into changes necessary to get pysam support for htslib 1.21 and friends, and they seem to involve several upstream commits. I noted at least: * 6147f5da869065c141aa8235ecbeb251d6e09bbe * 923aad9a9477bca02bd6838d63e59e7f0101dc8d (possibly) * b1e87ef6f22d0b9177d513891e0f4a4b84457200 * d3d2733e77e8db3ece4cd44ff5f9fee23e1342d2 * f4319112d89654ec862b832488315bb3657514a1 Waiting for a newer upstream sounds more prudent in my opinion. Keeping these commits at hand may be helpful in case we were to run into Trixie release freeze; synchronizing to the current state of the master branch may be a fine option too, at least better than cherry picking upstream commits. In the meantime, it may be useful to follow up with other components upgrades into Debian experimental, this would facilitate further testing from various parties. Have a nice day, :) -- .''`. Étienne Mollier <emoll...@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `-
signature.asc
Description: PGP signature
