Closed ulrichmarkus closed 10 months ago
Thanks for reporting! Indeed, running with conda is not as good monitored as singularity (I use that when developing) and docker (github tests), therefore some errors slip through occasionally.
About multiqc: thanks, thats already updated in the dev branch, but didnt know that it made actual problems. I'll plan a release soonish so that this is resolved.
Fixed in the dev banch, so I close that issue now.
Description of the bug
Two small issues when using conda as tool for the pipeline ampliseq:
package biostrings
When I run the standard test command with conda for nf-core/ampliseq the pipeline finishes with an error at the process NFCORE_AMPLISEQ:AMPLISEQ:FILTER_SSU. The error indicated that it couldnt resolve a new conda environment containing the package biostrings. The bioconductor package biostrings is loaded with bioconductor-biostrings instead of bioconductor::biostrings. Therefore you need to change line 5 in the file .nextflow/assets/nf-core/ampliseq/modules/local/filter_ssu.nf from
conda "bioconductor::biostrings=2.58.0"
toconda "bioconductor-biostrings=2.58.0"
.That worked for me at least.
Command used and terminal output
package multiqc
When I run the standard test command with conda for nf-core/ampliseq the pipeline finishes with an error at the process NFCORE_AMPLISEQ:AMPLISEQ:MULTIQC . The error indicated that it couldnt find a module imp. The imp issue came with the update from python to 3.12 (see issue https://github.com/MultiQC/MultiQC/issues/2112) When updating line 4 in the file .nextflow/assets/nf-core/ampliseq/modules/nf-core/multiqc/main.nf from
conda "bioconda::multiqc=1.15"
toconda "bioconda::multiqc=1.17"
it should work again.Command used and terminal output
Relevant files
No response
System information
No response