-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Bioconda has two (redundant) T-COFFEE packages #10614
Comments
t_coffee was introduced in:
t-coffee was introduced in:
Given |
Let's ask @pditommaso - what do you think? |
Interesting, I was not aware of it. The problem of that formula is that it uses the binary installer. I agree that the twos can be merged using the latest one. |
In this case, what should be done to the other recipes that depend on t_cofee? Should we update them all? |
Good point. Do you have any idea how many |
@pditommaso for the bioconda channel, |
I see. Anyhow I would just to keep as it is for now. The new formulate does not include all required deps and should be considered experimental. |
Hi @pditommaso , @apcamargo and others, WORKING
t_coffee /tmp/rba_fw55wzu1_39 -mode rcoffee
# Command Line: t_coffee /tmp/rba_fw55wzu1_39 -mode rcoffee [PROGRAM:T-COFFEE]
# T-COFFEE Memory Usage: Current= 48.796 Mb, Max= 1071.462 Mb
# Results Produced with T-COFFEE Version_11.00.8cbe486 (2014-08-12 22:05:29 - Revision 8cbe486 - Build 477)
# T-COFFEE is available from http://www.tcoffee.org
# Register on: https://groups.google.com/group/tcoffee/
conda list
...
t-coffee 11.00.8cbe486 h26a2512_0 bioconda
... NOT WORKING
t_coffee /tmp/rba_fw55wzu1_39 -mode rcoffee
********************************************************************************
Command line arguments: ['/home/uc/miniconda3/bin/t_coffee', '/tmp/rba_fw55wzu1_39', '-mode', 'rcoffee']
Install folder: /home/uc/miniconda3/lib/t_coffee-11.0.8
********************************************************************************
#*****************************************************************
--ERROR: # [FATAL:T-COFFEE]
# The Program /home/uc/miniconda3/lib/t_coffee-11.0.8/bin/t_coffee Needed by T-COFFEE Could not be found
# If /home/uc/miniconda3/lib/t_coffee-11.0.8/bin/t_coffee is installed on your system:
# -Make sure /home/uc/miniconda3/lib/t_coffee-11.0.8/bin/t_coffee is in your $path:
# If /home/uc/miniconda3/lib/t_coffee-11.0.8/bin/t_coffee is NOT installed obtain a copy from:
# (null)
#
#
# and install it manualy
******************************************************************
*************************************************************************************************
* FULL TRACE BACK PID: 6590
6590 -- ERROR: # [FATAL:T-COFFEE]
6590 -- COM: /home/uc/miniconda3/lib/t_coffee-11.0.8/bin/t_coffee /tmp/rba_fw55wzu1_39 -mode rcoffee
6590 -- STACK: 6589 -> 6590
*************************************************************************************************
# TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 6590 ppid 6589
#CL: /home/uc/miniconda3/lib/t_coffee-11.0.8/bin/t_coffee /tmp/rba_fw55wzu1_39 -mode rcoffee
********************************************************************************
Result: None
Error message: None
********************************************************************************
conda list
...
t_coffee 11.0.8 py36_2 bioconda
... If you plan to remove one of the packages, please ensure that the remaining one works completely. Best regards |
Pinging @bioconda/core |
I don't think we need to (or should) remove any old packages - they are not broken, but removing them might break things. Removing either of the two recipes from the repo and updating all recipes requiring t-coffee to match the name makes sense though, so we don't have the duplicate in the future. |
W.r.t. distributing mafft etc within the t-coffee package: I vote against that. The practice makes sense outside of a package manager. It might even make limited sense with other package managers, to be able to ensure compatible versions of the incorporated tools are available. With conda, they can be pinned as needed though, so there is no need for that. It would be important to have a test case in the recipe testing t-coffee in a mode calling all the aligners. CLIs are APIs, but people tend to forget that and so a change in command line interface by one of the tools might break t-coffee. It might be prudent to pin strongly. |
@SchwarzMarek - Any chance you could add your tests to the |
This was exactly the reason why I've create the However it turned out that T-Coffee uses an insane number of external packages for most of which do not exist a Bioconda package. I've posted the list here. |
Hi @epruesse - It would certainly be nice to have run-tests for every aligner. The test would be more complicated. printf ">a\nACGTCGATGCTA\n>b\nCAGTGTCAGCTG\n" | t_coffee -in=stdin -mode rcoffee and check the exit code. |
@SchwarzMarek That looks good! If it gets too complicated to have individual lines, you can write a |
Hi again, I've dug-up the -mode options from https://github.com/cbcrg/tcoffee/blob/master/lib/t_coffee_lib/t_coffee.c (line 814 onwards) and tested them for sample DNA, RNA and protein see the table below. I'm inclined to make changes to Table
|
Folks, as author of the |
I would prefer to keep the |
Yes, but without the required deps is basically broken. It's better the
other version.
If anybody want to step in contributing the missing deps is welcome.
…On Tue, Dec 11, 2018, 13:13 SchwarzMarek ***@***.*** wrote:
I would prefer to keep the t-coffee. The installation of required tools
is easier with this recipe.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10614 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAx3SD3iU_CoJiOkrslav88_-FE3ltB1ks5u36F1gaJpZM4WIBtz>
.
|
Well, as it was argued in the linked post (here), having the dependencies are important, however, not all are easily accessible. For example Also not all mods are not frequently used (some are not even in docs (I've looked here)) Maybe we could focus on dependencies for basic modes covered in tcoffee docs. That is As of now, I can add |
Is there a way to print a warning message when installing a conda package? it could used to warn the user that some modes are not available. |
@pditommaso perhaps a post-link script? https://conda.io/docs/user-guide/tasks/build-packages/link-scripts.html |
You could use |
OK, great. I will add a disclaimer to warn users that this is a recipe under development and does not support all t-coffee modes. |
FYI #12594 |
It turns out that a discrete number of deps are already on bioconda. I've updated the recipe adding them however the build is failing with this message:
Any suggestion how to solve it? |
@pditommaso this can happen if both packages were compiled against different sub-dependencies. Let's say zlib 1 and zlib 2. Rebuild/rerender both and it should fix it. |
I think the issue is that paste incorrectly is limited to only py27 while dca is only py3. However pasta should work for py3 according to their documentation: |
Hopefully fixed the conflict in #12648 |
T-coffee also installs blast and blast-legacy, which clobber each other's files. See #14331 |
hello, I was searching for t coffee in anaconda cloud and encountered this discussion, which one shall I install in my production server? Thanks in advance |
@edgano what's the status of the |
@glichtenstein |
@dpryan79 I agree, will go with t-coffee then, thank you very much. |
Is anyone still able to help with this issue? It's preventing packages from upgrading beyond python 3.7 and it's also been documented in a newer issue here: #32576 (comment) |
I rebuild t-coffee about 2 weeks ago, so packages should switch to that, as it doesn't pin a python version. |
@dpryan79 I see that the recipe for perl-bio-tools-run-alignment-tcoffee still points to the old problematic package Should that be changed? This comment suggests so and I've submitted a PR implementing it here. |
@amizeranschi I don't see a PR -- your link is to a commit on your fork of bioconda-recipes. Did you miss the last step of creating the PR on the official bioconda repository or am I just not finding it? |
Awesome! I'm excited to finally not be stuck on old python 3 versions. |
https://bioconda.github.io/recipes/t_coffee/README.html
https://bioconda.github.io/recipes/t-coffee/README.html
The first one ("t_coffee") is older, but doesn't compile on macOS and doesn't have some dependencies that a member of the T-COFFEE team said are important to the software.
The text was updated successfully, but these errors were encountered: