Installation of Orthofinder with conda fails - package

I tried installing orthofinder like this:
conda install -c bioconda orthofinder
But it returns the following:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: /
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
What is going on?
I am using conda 4.9.2 installed using Homebrew.
I also tried with a newer version of conda and it gives the same error.

Got solved using the zsh shell. I have no idea why but it worked. If someone knows please let me know.

Related

Glitches installing wxpython?

Im relatively new to python world.
Im trying to install wxpython on several computers and it keeps failing.
I use anaconda version 4.9.2 and use the prompt command:
conda install -c anaconda wxpython
I get the following error message:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
I try updating python to latest version. I try a number of things. and still I get this pesky problem. What am I doing wrong?
Thanks!
Nothing wrong per se. Those messages are indicating that Conda can't install that package without changing the currently installed packages. Because the Anaconda distribution (!= Conda) has lots of packages this happens very frequently. Also, this particular package is not updated frequently and the anaconda channel doesn't even seem to keep pace with that.
In general, it is better practice is to create new environments for each project/task you have to work on, and only install the packages you require. Also, the conda-forge channel tends to be a more consistent provider for packages, but undergoes less interoperability testing and tuning than the Anaconda channel packages. That is, consider trying something like
conda create -n myenv -c conda-forge python=3.9 wxpython ...
where myenv is whatever you would like to refer to the environment as, and ... should be whatever other packages you know you would like to use.

opam init fails - unable to create temp file

I have installed opam 2.1.0 on a Linux Virtualbox VM. When I try opam init, I get the following error:
<><> Fetching repository information ><><><><><><><><><><><><><><><><><><><><><>
[ERROR] Could not update repository "default": OpamDownload.Download_fail(_, "Curl
failed: \"/snap/bin/curl --write-out %{http_code}\\\\n --retry 3
--retry-delay 2 --user-agent opam/2.1.0 -L -o
/tmp/opam-32196-d33843/index.tar.gz.part --
https://opam.ocaml.org/index.tar.gz\" exited with code 23")
[ERROR] Initial download of repository failed.
Running with --disable-sandboxing doesn't help. I know that its a problem creating/writing to /tmp/opam-... directory because if I replace that with my current directory or home directory the command by itself runs fine. It also runs fine with /tmp/opam-... if I use the --create-dirs option in curl but I don't have any way of getting opam init to use that option. Any ideas?
thanks
Update
The reason opam init failed for me was because curl was installed with snap on my system. This exactly what is going on with your VM.
Try to run opam init -verbose and that could reveal more about why you ran into an error.
In my case I needed to install other things with opam and it kept failing every time. So snap uninstall curl and then sudo apt install curl fixed things. (Was only able to figure this out with help from my professor)
Workaround
I ran into the same issue and I found a workaround on the OCaml forum: here. (Credits to UnixJunkie)
You can run:
opam init github git+https://github.com/ocaml/opam-repository.git
This should avoid the certificate issues. This worked for me.
I tried to fix the certificate issues using this answer as well. You could try doing that, but it seems complicated when the workaround is to simply point it to the github repo directly.
This question is similar to this one.

"Unsatisfiable requirements detected for the package" in Julia

I am getting an error while adding packages to the julia:
Error
DataFrame
(#v1.5) pkg> add DataFrames
Updating registry at `C:\Users\.julia\registries\JuliaComputingRegistry`
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package DataFramesMeta [1313f7d8]:
DataFramesMeta [1313f7d8] log:
├─DataFramesMeta [1313f7d8] has no known versions!
└─restricted to versions * by an explicit requirement — no versions left
CUDA
(#v1.5) pkg> add CUDA
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package CUDA [052768ef]:
CUDA [052768ef] log:
├─CUDA [052768ef] has no known versions!
└─restricted to versions * by an explicit requirement — no versions left
This happens every time I try to add any package to julia. I have tried reinstalling the julia but the issue still persist.
Please suggest a solution to this issue. I have also posted this issue on julia-discourse.
Thanks in advance.
Update
The issue is related to cloning of registry during update. Apparently, it is some kind of a bug.
To resolve this issue, you may delete the registry/General folder and then restart Julia. This will make Julia to rebuild all the packages and then everything should run smoothly.
To delete the folder, one may either go to console and perform following operations:
(#v1.5) pkg> registry rm General
Removing registry `General` from ~/.julia/registries/General
or
Look for the folder .julia/registries/General (tested in windows) and delete it manually. (Path will look something like this: C:\Users\User\.julia\registries\General
Thanks!!

Failure in installing Octave in conda

When trying to install octave in conda, I used this command provided in conda's website:
conda install -c conda-forge octave
But during the installation, this error occured:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: |
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versionsThe following specifications were found to be incompatible with your CUDA driver:
- feature:/linux-64::__cuda==11.0=0
Your installed CUDA driver is: 11.0
If my understanding of the message is correct, it says that octave requires cuda driver of version 11.0, however I do have the version 11.0. What went wrong during the process?

Installing mongodb-enterprise-server error

Hello guys. Can someone help me about this one? I cant install mongodb because of dependency problem. I already tried updating my linux mint terminal.
dpkg: dependency problems prevent configuration of mongodb-enterprise-server:
mongodb-enterprise-server depends on libcurl3 (>= 7.16.2); however:
Package libcurl3 is not installed.
mongodb-enterprise-server depends on snmp; however:
Package snmp is not installed.
Installing via dpkg -i mongodb.deb will not include additional package dependencies. You should be able to fix your installation by following up with sudo apt --fix-broken install.
Unless you have strong reasons to avoid the standard process I would recommend following the tutorial to Install MongoDB Enterprise by adding the appropriate repo definitions. Adding the normal package repo will also make it easier for you to update to newer minor releases of MongoDB 4.0.x.

Resources