Fix conda for upcoming release 2.16.0#940
Conversation
This PR is against the
|
|
So got a few more problems: (B) 6: (C) 7: Edit: after a re-run of the failed tests (B) turns to (A) and (C) to to a problem with the new DADA2 env |
| conda-solver: libmamba | ||
| channels: conda-forge | ||
| channel-priority: strict | ||
| channel-priority: flexible # 'strict' would be preferable but 'flexible' is required for QIIME2 2024.10 conda yml file |
There was a problem hiding this comment.
I think this can be set to strict if the QIIME2 environment definition includes the channel for each package (e.g., bioconda::blast==2.17.0)
There was a problem hiding this comment.
Thanks! But the QIIME2 conda yml file contains 756 lines, and none of the packages are defined with channels, it comes from the QIIME2 developers with that flaw. I would like to keep it as is for now.
|
Thanks! |
This is fixing conda CI tests.
At first this was intentionally to master branch to run conda CI tests.
Changes include minimum nextflow version 25.04.0 to 25.04.8, an additional package for the DADA2 1.34.0 conda env, change from
channel-priority: stricttoflexiblefor CI tests. The latter possibly could be avoided by adding channels to the QIIME2 conda yml file (but that are >700 entries and subject to be update soon anyway, so postponed for now).PR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).