Hi, I unfortunatly cannot reproduce the problem. I would need the sequence that creates the issue, or a fake one reproducing the error. Could be a sequence format that raise an error (bad characters?, even if I tried to do so also).
I tested with a fake sequence and a fake db the same input parameters and it worked. I can test against Swissprot, but I would need the sequence that creates the problem, at least to try to find what is wrong with the sequence and create a fake one doing the same (which I could send to upstream if necessary). If sending the sequence is only an issue with the fact it is logged on public server, maybe you could send me the sequence directly. If it is too private, well, can you consider spending more time analysing your sequence and trying to reproduce the problem with a fake one ? You already did a great job on analysing the impacts (which output format, sub sequences...), thanks for this. Olivier -- gpg key id: 4096R/326D8438 (pgp.mit.edu) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
