-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correctly clean package / libsolv cache from time to time #61
Comments
maybe it's because there is a cache: if you clear the cache beforehand with |
also, obviously, you might need to add I got this solutoin right now:
|
This is just an observation: To answer your post: Also, the repositories are configured properly: $ cat ~/.condarc
channels:
- conda-forge
- bioconda
- defaults
channel_priority: flexible
report_errors: true using When i try a new environment $conda create -n goatest goatools=0.9.9
.............
.............
xorg-xproto conda-forge/linux-64::xorg-xproto-7.0.31-h14c3975_1007
xz conda-forge/linux-64::xz-5.2.4-h14c3975_1001
zlib conda-forge/linux-64::zlib-1.2.11-h516909a_1006
zstd conda-forge/linux-64::zstd-1.4.3-h3b9ef0a_0
Proceed ([y]/n)? But mamba create -n goatest goatools=0.9.9
.............
.............
Looking for: ['goatools 0.9.9.*']
16934 packages in https://conda.anaconda.org/conda-forge/noarch
8315 packages in https://conda.anaconda.org/bioconda/noarch
27093 packages in https://conda.anaconda.org/bioconda/linux-64
74021 packages in https://conda.anaconda.org/conda-forge/linux-64
832 packages in https://repo.anaconda.com/pkgs/main/noarch
3536 packages in https://repo.anaconda.com/pkgs/r/noarch
5893 packages in https://repo.anaconda.com/pkgs/r/linux-64
14211 packages in https://repo.anaconda.com/pkgs/main/linux-64
Encountered problems while solving.
Problem: nothing provides requested goatools 0.9.9.* This isn't specific for this package, this has happened to me at least for 5-10 different packages in the last months. I'm using Also, look: $mamba install mamba=0.0.10
Encountered problems while solving.
Problem: nothing provides requested mamba 0.0.10.* |
Did you try to clean the folder I mentioned though? |
ah, regarding the x.x.x.* specification, it's just a way to express "any build number" for installing mamba 0.0.10 it works for me:
Are you on OS X or Linux? (Or Win?) |
$ uname -a
Linux mibu-manjaro 4.19.81-1-MANJARO #1 SMP PREEMPT Tue Oct 29 12:49:04 UTC 2019 x86_64 GNU/Linux (based on In my home directory, i don't have any cache: ls -la ~/.conda/pkgs/
total 8
drwxr-xr-x 2 mibu mibu 4096 abr 2 2018 .
drwxr-xr-x 3 mibu mibu 4096 abr 2 2018 ..
-rw-rw-r-- 1 mibu mibu 0 abr 2 2018 urls
-rw-rw-r-- 1 mibu mibu 0 abr 2 2018 urls.txt In my environment directory, I had the ls -la /storage/miniconda3/envs/bif/pkgs/cache/
total 44
drwxrwsr-x 2 mibu mibu 4096 nov 7 18:52 .
drwxr-xr-x 315 mibu mibu 36864 sep 23 19:21 .. |
I just erased the cache from the base env and fixed the issue, previously I erased the cache from the env I was working in. Thanks for your help |
I renamed the bug and reopened it! We'll have to take care of this soon. |
The latest release (0.1.0) of mamba should fix this issue. |
Hello,
first, thank for this package, it's way faster than conda and has saved me a lot of time.
The problem that I've found is that, when you want to install a specific version of a package, let's say
mamba install goatools=0.9.9
, it fails to find it so isn't able to install it:Notice that I'm not using globs in my search. I've found this with multiple packages and most of the time, maybe all of them, is when i want to install the latest version of a package. Of course the package is available in the conda repositories and when I try to do a
mamba install package-name
, without specifying the version, sometimes it doesn't install the latest one, so I specify the version, that's the reason I've had this specific problem multiple times. I understand that a package cannot be installed because of the requirements, but in these cases,mamba
is saying that the package isn't available.The text was updated successfully, but these errors were encountered: