Skip to content
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

conda channel order in galaxy and planemo #3389

Closed
2 of 3 tasks
mvdbeek opened this issue Jan 6, 2017 · 4 comments
Closed
2 of 3 tasks

conda channel order in galaxy and planemo #3389

mvdbeek opened this issue Jan 6, 2017 · 4 comments

Comments

@mvdbeek
Copy link
Member

mvdbeek commented Jan 6, 2017

The channel order mechanism has changed between conda 3.19.3 (what we've been shipping galaxy with initially) and >= 4. The changes are documented here. This led us to notice that there are problems with the current order.

  • currently planemo conda_install writes out a channel order that is wrong (i.e. different from bioconda). The current order is [defaults, conda-forge, r, bioconda, iuc] while it should be iuc, bioconda, r, defaults, conda-forge].

  • need to verify that galaxy's channel order is correct

  • looking up galaxy's channel order should be easy. log in galaxy log? log in tool run information ?

@bgruening
Copy link
Member

Adding to the last point, the complete environment of a tool + channel order should be dumped as part of the metadata.

@nsoranzo
Copy link
Member

nsoranzo commented Jan 9, 2017

while it should be [iuc, bioconda, defaults, r, conda-forge]

According to https://github.com/bioconda/bioconda-recipes/blob/master/config.yml , this should be:

[iuc, bioconda, r, defaults, conda-forge]

which is also what we already use in config/galaxy.ini.sample .

@mvdbeek
Copy link
Member Author

mvdbeek commented Jan 11, 2017

updated the above -- I think that was a mistake when we we're working through some problems in gitter

@jmchilton
Copy link
Member

Moved these logging issues to a new issue and closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants