Hi, I've uploaded since the Python3 issue is solved.
For upstream please note: There are some remaining Python2 files in the test suite. Please consider the patch https://salsa.debian.org/med-team/kissplice/-/blob/master/debian/patches/tests-2to3.patch There are build time errors described below which might require your attention. Kind regards Andreas. On Fri, May 29, 2020 at 04:19:35AM +0530, Nilesh Patra wrote: > Hi, > > On Fri, 29 May 2020, 01:08 Andreas Tille, <andr...@an3as.eu> wrote: > > > Hi Moritz, > > > > On Thu, May 28, 2020 at 08:48:41PM +0200, Moritz Mühlenhoff wrote: > > > > > > JFTR, this is now fixed upstream in 2.5.0 and later: > > > http://kissplice.prabi.fr/download/: > > > > > > -------------------------------------- > > > Kissplice Version 2.5.0 (2020-04-06) > > > > > > New features: > > > Now compatible with python3 > > > -------------------------------------- > > > > Thanks for the hint. Unfortunately there are remaining issues > > in build time test and autopkgtest. even of version 2.5.1 .:-( > > > > I've Fixed the autopkgtest > > For the failing build tests: this is what I observe - this try matching > strings containing a few values with kissplice result. > > For instance, this is one of the failures: > > Expected: > 0a: Single SNPs, Inexact Repeats or sequencing substitution errors, 69 found > > Actual: > 0a: Single SNPs, Inexact Repeats or sequencing substitution errors, 22 found > > There's definitely a difference between the outputs of previous kissplice > version and current kissplice version, I tried this manually as well. > > Just _maybe_, the upstream data has been changed, and the correct data > hasn't been injected; or the implementation has changed in version, > 2.5.1and this should output 22, but the tests haven't been changed > accordingly ; or maybe this is a bug with kissplice itself. > > In either case, I'm not really about this. Maybe we should ask upstream > about it. > > Thanks and regards > Nilesh -- http://fam-tille.de