-
Notifications
You must be signed in to change notification settings - Fork 97
Description
Hi,
I have an issue with the version of conda needed by Galaxy 3.19.3. (in a first place with my travis test and in a second place with Galaxy itself).
One of my dependency bioconductor-camera take ages to Solving package specifications: ............................................... to finally reach the TravisCI time out. I think it's a problem with conflict between R versions.
- To investiguate, I choose a really easy package
r-batch
./miniconda2-conda3.19.3/bin/conda create --name __r-batch@1.1_4 r-batch=1.1_4 --override-channels --channel bioconda --channel r --channel defaults --channel conda-forgeInstallation the r3.2.2 version
r-batch: 1.1_4-r3.2.2_0
- I have to remove the conda-forge channel
./miniconda2-conda3.19.3/bin/conda create --name __r-batch@1.1_4 r-batch=1.1_4 --override-channels --channel bioconda --channel r --channel defaultsInstallation
r-batch: 1.1_4-r3.3.1_0
- No problemo with the last 4.2.12
./miniconda2-conda4.2.12/bin/conda create --name __r-batch@1.1_4 r-batch=1.1_4 --override-channels --channel bioconda --channel r --channel defaults --channel conda-forgeInstallation
r-batch: 1.1_4-r3.3.1_0 bioconda
I know that there is an issue with the offline option needed by Galaxy or something like that.
My question is: is it possible to use the last version of conda now with planemo, or is it still mandatory? According to galaxyproject/galaxy#3227 ?
My last possibility is to alter this file : .planemo/condarc and maybe the galaxy.ini conda_ensure_channelsof my docker image