When using `ENSEMBLVEP_VEP` has anyone encountered...
# modules
a
When using
ENSEMBLVEP_VEP
has anyone encountered the following error:
Copy code
Can't locate List/MoreUtils.pm in @INC (you may need to install the List::MoreUtils module) (@INC contains: /opt/conda/share/ensembl-vep-112.0-0/modules /opt/conda/share/ensembl-vep-112.0-0 /opt/conda/lib/perl5/5.32/site_perl /opt/conda/lib/perl5/site_perl /opt/conda/lib/perl5/5.32/vendor_perl /opt/conda/lib/perl5/vendor_perl /opt/conda/lib/perl5/5.32/core_perl /opt/conda/lib/perl5/core_perl .) at /opt/conda/share/ensembl-vep-112.0-0/Bio/EnsEMBL/Variation/DBSQL/VariationFeatureAdaptor.pm line 102.
I am running using an older version of VEP in a singularity container, but following the way the
nf-core
container was built except for a change in VEP version.
I don’t know how
conda
works, but if the packages are not re-built with the latest recipe when you install them then it seems that the dependency was only added a couple of months back (well after 112 was released) https://github.com/bioconda/bioconda-recipes/commit/f7a4dd360b88cf28c826586415ca4c42cc3a4eaf
m
Could it be due to sourcing files that set environment variables? e.g. similar issue: https://community.seqera.io/t/confusion-over-why-a-tool-works-in-docker-but-fails-in-s[…]fer-i-e-using-wave-micromamba/1244/2
a
No AFAICT it is down to the bad recipe, missing
perl-list-moreutils
as above. I manually created a seqera container with that as an explicit dependency for now, but I am not clear on how bioconda works in terms of installing an old version of a package (here 112) when the recipe has been updated? I do suspect it may not always be an issue because I think perhaps the parts that use
moreutils
are only used if you use particular extensions (e.g. AlphaMissense)
👍🏽 1
m
VEP shakefist