Closed ezherman closed 1 year ago
@ezherman Thanks for your suggestion
We found there are two version of homopolish 0.4.1 on bioconda and just one can build the env successfully.
If set the channel_priority strict, it would get wrong dependencies version.
We have sent the request for removing the wrong version from bioconda.
The temparary solution is to set the certain build number when conda install.
conda create -n homopolish_py1 -c conda-forge -c bioconda homopolish=0.4.1=pyhdfd78af_1
Hi @SeaneryChang, thank you for looking into this! Great that you've found the source of the problem. I will close this issue, as it looks to have a solution now.
Hi @SeaneryChang, unfortunately I am still getting the dependencies issue with the conda command that you provided. Would you be able to look into this again? And is there any way in which I can help?
Hi @ezherman, do you remember you run the command under the strict mode or the flexible mode?
Hi @Pohuii-Tzeng, thanks for getting back to me! I ran the command under strict mode. This is a requirement for the workflow manager that I am using (Snakemake).
Hi @Pohuii-Tzeng, I was wondering whether there has been any progress on resolving this issue with bioconda. Thank you!
Hello @ezherman. In order to make it downloadable in strict mode, I tried to deal with the dependency conflicts in homopolish these days. But still doesn't find a solution. We decide to suggest users install homopolish in flexible mode like what you suggested to us. But we will do it by adding the parameter in the install command which will only make the install command run in flexible. The command will look like this:
conda create -n homopolish --no-channel-priority -c conda-forge -c bioconda homopolish=0.4.1=pyhdfd78af_1
And we will also upload a newer build to bioconda.
Thanks for your reply @Pohuii-Tzeng! That's fair, I can see that a flexible install is a workable solution. It's not a perfect fix for my use case, where the Snakemake workflow manager requires all environments in the workflow to be installed with the same level of channel priority. But I have found a temporary workaround. I'll close this issue now, thanks again for getting back to me!
I have found that the suggested mamba installation command fails for homopolish v0.4.1 under strict channel priority. Below I outline the steps that I took. I suggest adding the anaconda channel to the mamba command and adding that users should use flexible channel priority in order to install this version of homopolish, so long as the conflicting package (libedit) is not updated on conda-forge.
The default mamba command
The command suggested in the README by default installs homopolish v0.3.3.
The above command returns:
Specifying the latest homopolish version in the mamba command
Specifying the latest version results in a package incompatibility:
This returns:
Including the anaconda channel for the libedit package
It seems that the libedit version that is required is not yet available on conda-forge. Instead, it's available on anaconda. However, specifying the anaconda channel does not resolve the issue, due to strict repo priority:
This returns:
Suggested solution
I suggest that users are asked to set channel priority to flexible prior to installing homopolish, as shown below. Note that the
mamba create
command takes a while due to the flexible solve.