New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test updates for NCBI BLAST DB v5 #2863
Comments
With NCBI BLAST+ v2.10.0 the v5 DB became the default, and it has slightly different file extensions to their v4 DB format. See GitHub issue biopython#2863
With NCBI BLAST+ v2.10.0 the v5 DB became the default, and it has slightly different file extensions to their v4 DB format. See GitHub issue #2863
@tillea reported by email that even with the patch it fails on 32bit systems:
P.S. We're looking into the possibility that |
@chebizarro @peterjc Is this still a blocking issue for release 1.77? |
Possibly - I suspect it is a Debian/Blast issue though. |
Then does it make sense to wait for this? Especially since we are considering to drop |
It works on the major CPUs anyway - seems low risk to proceed with our release. |
On Sat, May 23, 2020 at 08:09:56AM -0700, Peter Cock wrote:
It works on the major CPUs anyway - seems low risk to proceed with our release.
I'd recommend to proceed which also saves some patches on Debian side. I did not found the time to follow your hints yet but I can perfectly try to hunt this down on the next version.
|
I built a Docker container based on the i386/ubuntu 18.04 image and can't seem to replicate the problem using the i386 build of |
Thanks Chris, that is reassuring - less likely one of our main target demographic will hit this. |
This would be solved by #3344 |
Clarification: The warning about the BLAST+ wrappers being out of sync would be fixed by dropping them. The error about V5 databases was already fixed, as as the Closing. |
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959587
@tillea wrote:
Related to this, there are new switches to add to the command line wrappers (shown as warnings from the tests above)
The text was updated successfully, but these errors were encountered: