-
Notifications
You must be signed in to change notification settings - Fork 441
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
busco: add tar requirement #2715
busco: add tar requirement #2715
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[makeblastdb] /usr/local/bin/makeblastdb: error while loading shared libraries: libbz2.so.1
busco pins blast to < 2.4, which doesn't seem to ship bzip2 as a dependency --- but bzip2 is listed in https://github.com/bioconda/bioconda-recipes/blob/master/recipes/blast/2.2.21/meta.yaml, which is pretty weird.
tools/busco/busco.xml
Outdated
@@ -1,12 +1,13 @@ | |||
<tool id="busco" name="Busco" version="@TOOL_VERSION@+galaxy1"> | |||
<tool id="busco" name="Busco" version="@TOOL_VERSION@+galaxy2"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add a profile="18.01"
... the tool doesn't set detect_errors="exit_code"
and we'd get this plus isolated home etc., for free.
<tool id="busco" name="Busco" version="@TOOL_VERSION@+galaxy2"> | |
<tool id="busco" name="Busco" version="@TOOL_VERSION@+galaxy2" profile="18.01"> |
seems that the build number was not bumped after the bzip2 requirement was added. |
I think it's actually 2.2.31 that gets installed, whose last known build looked like this: https://github.com/bioconda/bioconda-recipes/blob/de1a2caef2b4fa26f37e96ddbd404156a5ae2e60/recipes/blast/meta.yaml |
This seems related: bioconda/bioconda-recipes#15459 |
…matthias/tools-iuc into topic/busco-container-fix
now that bioconda/bioconda-recipes#19016 is merged we could try this one again. seems stuck anyway |
It passed here, the status just didn't update
|
From the logs there remains the error:
FOR CONTRIBUTOR: