Error installing qiime 2.12

[Jerson_Garita]

Hello! I was just trying to update from qiime 2.11 to qiime 2.12 using miniconda, but I received this error message

“ERROR conda.core.link:_execute_actions(337): An error occurred while installing package ‘::bioconductor-genomeinfodbdata-1.0.0-r3.4.1_1’.
LinkError: post-link script failed for package ::bioconductor-genomeinf odbdata-1.0.0-r3.4.1_1”

I tried to get this file again from other repository in order to check if the one downloaded from the “qiime´s file” has an error…but despite of this change I receive the same error message.

does anybody know how to solve it?

Thank you so much.

[thermokarst]

Hi @Jerson_Garita - I suspect this is a transient network error. How about you clean up:

$ source deactivate
$ conda clean --all

and then try to install again.

Keep us posted!

[Jerson_Garita]

Thank you so much for your advice…unfortunately, I am having the same error message.

“ERROR conda.core.link:_execute_actions(337): An error occurred while installing package ‘::bioconductor-genomeinfodbdata-1.0.0-r3.4.1_1’.
LinkError: post-link script failed for package ::bioconductor-genomeinfodbdata-1.0.0-r3.4.1_1”

I will appreciate any other idea…

thanks so much

[thermokarst]

Hmm, this one is a bit tricky --- if clearing your cache didn't help, you might be the victim of overzealous network hardware. Please see this post for some more details:

2017.12 Installation Issues (download stalls)

Wow, that is a tricky one! I chatted with @ebolyen a bit about this today - we both think that there is some piece of network infrastructure sitting between your computer and the bioconductor servers that is terminating the connection prematurely (maybe an institutional firewall?). This is a bummer, because there probably isn’t much that can be done in that department. We don’t develop conda, so we probably don’t the complete picture of how this could be accomplished, but a quick Google search…

I'm sorry I don't have a better answer for you - this gets into the realm of conda, which is something we don't develop. If your workstation is mobile (e.g. a laptop), maybe try from a new network? Sorry, and good luck - keep us posted!