Hi, Mattia and all, على الخميس 26 تشرين الأول 2017 15:44، كتب Mattia Rizzolo: > On Thu, Oct 26, 2017 at 12:12:05PM -0700, Diane Trout wrote: >> libhts2 introduced an ABI change which broke python-pysam, and a new >> version of python-pysam needed to be released to update to the new ABI. > > FTR, this is what changed between the symbols of the version 1.4.1-5 and > 1.5-1: > [...] > >> libhts2 probably needs a proper symbols file to make it easier to see >> when the ABI is changing. https://wiki.debian.org/UsingSymbolsFiles >> >> Mattia Rizzolo, also suggests other methods of dealing with managing ABI >> changes. > > In pysam's case, it is looking for hts_log, if you had properly checked > the symbols of your package before uploading you should have at least > tweaked the dh_shlibdeps invocation to force a version, or introduced a > .symbols file (very recommended for a case like hstlib where the symbols > seems to be simple). > > But then, the ABI is broken, so just nicest symbols handling is not > enough for your case, you need >> Such as bumping soname, changing the package name and use Conflicts, or >> adding versioned Breaks against broken packages > >
Please see #822701; specifically: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822701#26 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822701#41 (and subsequent replies) and https://lists.alioth.debian.org/pipermail/debian-med-packaging/2016-January/038827.html (which is linked from one of the replies to the above) We've been doing this for every htslib suite release and can confirm upstream's explanation. Other packages do not get broken. Upstream has made a soname bump as appropriate for the 1.4 release if I remember correctly. That's all I can say about this; I don't actually work on the htslib packaging myself. regards Afif -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name
