No commands work after updating to mamba 1.5.3 #3033
Comments
|
Issue with |
|
I can't find the source of where the |
|
You need the Lines 768 to 773 in 34ce523 |
|
Hello, on my side, i have exactly the same error message with conda 23.10.0 and python 3.11.5. If needed, i paste below the result of conda info command : Thanks so much for your help |
|
This is likely triggered by conda/conda#13173 that makes the code in mamba 1.x use a full import path instead of a relative one. |
|
Thank you @jezdez for your message. Do you know how to fix this issue? Should i downgrage/install another/old version of conda ? On another ubuntu computer (with version conda 23.5.2), i did not get this mamba issue. Thank so much. |
|
@image80 Downgrading is the best course of action until we have a proper fix out. |
|
Yeah, I believe conda/conda#13173 changes the CLI parsing so that the Since this is easy to fix in a backward-compatible way, I would err on fixing mamba instead of rolling back the change in conda. Personally, I consider the change in conda to be acceptable and not needing to be covered by the deprecation policy per CEP 9. But obviously, it's unfortunate that this wasn't caught by a CI system ahead of time. We shall improve that by more conservative version pinning of the conda dependency in mamba, or running mamba tests as part of the conda release, as suggested by @SylvainCorlay to me. |
|
I proposed patch for mamba CLI is here: #3036 |
Yes, for packages that have a higher impact on the ecosystem, it would be reasonable to run a (small) selection of tests upstream. |
|
@JohanMabille Since conda 23.11.0 requires conda-libmamba-solver >=23.11.0, which requires libmamba >=1.5.3, only mamba 1.5.3 is affected by this breakage, so we should be able to make a patch release, and a repodata patch forcing 1.5.3 to be installed with conda<3.11... To the more general point of preventing this kind of breakage, mamba and conda are both upstream to each other in a way (since conda depends on libmamba, and mamba depends on the conda CLI). It makes sense to be a bit cautious about all of this. Some CI set up could be a way to go. Note that mamba 2.0 will not depend on conda at all, which will make the situation a bit simpler. |
We already put in a repodata patch on conda-forge for this. |
|
I've just released 1.5.4, working on the feedstock now, it should be available on conda-forge in the next couple of hours. |
Thank you so much!
I can't say I've run the mamba 1.x tests before locally recently, maybe it'd be worth running them (or a subset) in the conda conda-forge feedstock upon release? |
Maybe it's just a matter of a little smoke tests in the conda recipe. Adding |
|
Yes, please, please, please do add a |
|
See also #3029 |
We can add a
To be clear, any release of |
We also set a more restrictive upper bound on conda in the mamba feedstock, so that when a new conda release is cut, we can test whether mamba is broken, fix it if needed, and relax the constraint without breaking the ecosystem. |
To follow up: |
|
If I understand correctly, before you try to update anything you have Can you try the following and let me know if it works?
If that does not work (do not restore the previously removed files yet):
EDIT: my assumption is that your install is using the
The last command successfully upgraded to |
|
Oh, sorry, I have to correct myself: I'm working off of the current
(To be fair: Disagreements between |
|
On Linux, after upgrading mamba from 1.5.3 to 1.5.4, "mamba update --all" worked again, but "mamba clean --yes --all" still had an error similar to what reported in #534. |
Follow-up to mamba-orggh-3036 to fix "mamba clean". ref: - mamba-org#3033 (comment) Signed-off-by: Marcel Bargull <marcel.bargull@udo.edu>
Thanks for the report! |
…3040) Follow-up to gh-3036 to fix "mamba clean". ref: - #3033 (comment) Signed-off-by: Marcel Bargull <marcel.bargull@udo.edu>
I really meant the content of
I wonder if rebuilding |
I can't see why... Nonetheless: [conda@cf26b1d4025e ~]$ mamba install -qy jq
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
[conda@cf26b1d4025e ~]$ jq -r '.["packages.conda"][]|select(.name=="mamba")|select(.version=="1.5.3")|.depends[]|select(.|startswith("conda "))' /opt/conda/pkgs/cache/????????.json
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
conda >=23.9,<23.11.0
[conda@cf26b1d4025e ~]$ jq -r 'select(.name=="mamba")|.depends[]|select(.|startswith("conda "))' /opt/conda/pkgs/mamba-1.*/info/{index,repodata_record}.json /opt/conda/conda-meta/mamba-1.*.json
conda >=23.9,<24
conda >=23.9,<24
conda >=23.9,<24
[conda@cf26b1d4025e ~]$ # ^- shows all (index.json, repodata_record.json, conda-meta/*.json) have the unpatched info.
[conda@cf26b1d4025e ~]$ mamba update -d conda
Looking for: ['conda']
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- conda
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
────────────────────────────────────────────────────────────────
Install:
────────────────────────────────────────────────────────────────
+ menuinst 2.0.0 py310hff52083_1 conda-forge 134kB
+ distro 1.8.0 pyhd8ed1ab_0 conda-forge 41kB
Upgrade:
────────────────────────────────────────────────────────────────
- conda 23.10.0 py310hff52083_1 conda-forge Cached
+ conda 23.11.0 py310hff52083_1 conda-forge 979kB
Summary:
Install: 2 packages
Upgrade: 1 packages
Total download: 1MB
────────────────────────────────────────────────────────────────
Dry run. Exiting.
DryRunExit: Dry run. Exiting.
[conda@cf26b1d4025e ~]$ rm -rf /opt/conda/pkgs/mamba-1.*
[conda@cf26b1d4025e ~]$ mamba update -d conda
Looking for: ['conda']
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- conda
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
────────────────────────────────────────────────────────────────
Install:
────────────────────────────────────────────────────────────────
+ menuinst 2.0.0 py310hff52083_1 conda-forge 134kB
+ distro 1.8.0 pyhd8ed1ab_0 conda-forge 41kB
Upgrade:
────────────────────────────────────────────────────────────────
- conda 23.10.0 py310hff52083_1 conda-forge Cached
+ conda 23.11.0 py310hff52083_1 conda-forge 979kB
Summary:
Install: 2 packages
Upgrade: 1 packages
Total download: 1MB
────────────────────────────────────────────────────────────────
Dry run. Exiting.
DryRunExit: Dry run. Exiting.
[conda@cf26b1d4025e ~]$ mamba install -y mamba=1.5.2
Looking for: ['mamba=1.5.2']
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- mamba=1.5.2
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
─────────────────────────────────────────────────────────────────────────────
Downgrade:
─────────────────────────────────────────────────────────────────────────────
- libmamba 1.5.3 had39da4_2 conda-forge Cached
+ libmamba 1.5.2 had39da4_1 conda-forge 2MB
- ruamel.yaml 0.18.5 py310h2372a71_0 conda-forge Cached
+ ruamel.yaml 0.17.40 py310h2372a71_0 conda-forge 200kB
- libmambapy 1.5.3 py310h39ff949_2 conda-forge Cached
+ libmambapy 1.5.2 py310h39ff949_1 conda-forge 301kB
- conda 23.10.0 py310hff52083_1 conda-forge Cached
+ conda 23.9.0 py310hff52083_2 conda-forge 969kB
- mamba 1.5.3 py310h51d5547_2 conda-forge 51kB
+ mamba 1.5.2 py310h51d5547_1 conda-forge 52kB
- conda-libmamba-solver 23.11.1 pyhd8ed1ab_0 conda-forge Cached
+ conda-libmamba-solver 23.9.3 pyhd8ed1ab_0 conda-forge 47kB
Summary:
Downgrade: 6 packages
Total download: 3MB
─────────────────────────────────────────────────────────────────────────────
mamba 51.6kB @ 387.4kB/s 0.1s
ruamel.yaml 200.2kB @ 1.3MB/s 0.2s
libmambapy 300.5kB @ 1.7MB/s 0.2s
conda-libmamba-solver 46.5kB @ 254.3kB/s 0.1s
conda 968.7kB @ 4.8MB/s 0.2s
libmamba 1.6MB @ 3.1MB/s 0.5s
Downloading and Extracting Packages:
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
[conda@cf26b1d4025e ~]$ mamba update -d conda
Looking for: ['conda']
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- conda
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
─────────────────────────────────────────────────────────────────────────────
Install:
─────────────────────────────────────────────────────────────────────────────
+ menuinst 2.0.0 py310hff52083_1 conda-forge 134kB
+ distro 1.8.0 pyhd8ed1ab_0 conda-forge 41kB
Upgrade:
─────────────────────────────────────────────────────────────────────────────
- libmamba 1.5.2 had39da4_1 conda-forge Cached
+ libmamba 1.5.4 had39da4_0 conda-forge 2MB
- libmambapy 1.5.2 py310h39ff949_1 conda-forge Cached
+ libmambapy 1.5.4 py310h39ff949_0 conda-forge 302kB
- conda 23.9.0 py310hff52083_2 conda-forge Cached
+ conda 23.11.0 py310hff52083_1 conda-forge 979kB
- conda-libmamba-solver 23.9.3 pyhd8ed1ab_0 conda-forge Cached
+ conda-libmamba-solver 23.11.1 pyhd8ed1ab_0 conda-forge Cached
- mamba 1.5.2 py310h51d5547_1 conda-forge Cached
+ mamba 1.5.4 py310h51d5547_0 conda-forge 52kB
Summary:
Install: 2 packages
Upgrade: 5 packages
Total download: 3MB
─────────────────────────────────────────────────────────────────────────────
Dry run. Exiting.
DryRunExit: Dry run. Exiting.
[conda@cf26b1d4025e ~]$ mamba install -y mamba=1.5.3
Looking for: ['mamba=1.5.3']
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- mamba=1.5.3
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
──────────────────────────────────────────────────────────────────
Upgrade:
──────────────────────────────────────────────────────────────────
- libmamba 1.5.2 had39da4_1 conda-forge Cached
+ libmamba 1.5.3 had39da4_2 conda-forge Cached
- libmambapy 1.5.2 py310h39ff949_1 conda-forge Cached
+ libmambapy 1.5.3 py310h39ff949_2 conda-forge Cached
- mamba 1.5.2 py310h51d5547_1 conda-forge Cached
+ mamba 1.5.3 py310h51d5547_2 conda-forge 51kB
Summary:
Upgrade: 3 packages
Total download: 51kB
──────────────────────────────────────────────────────────────────
mamba 50.9kB @ 401.7kB/s 0.1s
Downloading and Extracting Packages:
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
[conda@cf26b1d4025e ~]$ mamba update -d conda
Looking for: ['conda']
conda-forge/linux-64 Using cache
conda-forge/noarch Using cache
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- conda
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
─────────────────────────────────────────────────────────────────────────────
Install:
─────────────────────────────────────────────────────────────────────────────
+ menuinst 2.0.0 py310hff52083_1 conda-forge 134kB
+ distro 1.8.0 pyhd8ed1ab_0 conda-forge 41kB
Upgrade:
─────────────────────────────────────────────────────────────────────────────
- libmamba 1.5.3 had39da4_2 conda-forge Cached
+ libmamba 1.5.4 had39da4_0 conda-forge 2MB
- libmambapy 1.5.3 py310h39ff949_2 conda-forge Cached
+ libmambapy 1.5.4 py310h39ff949_0 conda-forge 302kB
- conda 23.9.0 py310hff52083_2 conda-forge Cached
+ conda 23.11.0 py310hff52083_1 conda-forge 979kB
- conda-libmamba-solver 23.9.3 pyhd8ed1ab_0 conda-forge Cached
+ conda-libmamba-solver 23.11.1 pyhd8ed1ab_0 conda-forge Cached
- mamba 1.5.3 py310h51d5547_2 conda-forge Cached
+ mamba 1.5.4 py310h51d5547_0 conda-forge 52kB
Summary:
Install: 2 packages
Upgrade: 5 packages
Total download: 3MB
─────────────────────────────────────────────────────────────────────────────
Dry run. Exiting.
DryRunExit: Dry run. Exiting.
Which shows that if the entry in [conda@0fc3fa546c5d ~]$ mamba update -d conda
Looking for: ['conda']
conda-forge/noarch 12.8MB @ 14.0MB/s 1.0s
conda-forge/linux-64 31.0MB @ 16.7MB/s 2.0s
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- conda
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
────────────────────────────────────────────────────────────────
Install:
────────────────────────────────────────────────────────────────
+ menuinst 2.0.0 py310hff52083_1 conda-forge 134kB
+ distro 1.8.0 pyhd8ed1ab_0 conda-forge 41kB
Upgrade:
────────────────────────────────────────────────────────────────
- conda 23.10.0 py310hff52083_1 conda-forge Cached
+ conda 23.11.0 py310hff52083_1 conda-forge 979kB
Summary:
Install: 2 packages
Upgrade: 1 packages
Total download: 1MB
────────────────────────────────────────────────────────────────
Dry run. Exiting.
DryRunExit: Dry run. Exiting.
[conda@0fc3fa546c5d ~]$ conda remove --force -yq mamba
## Package Plan ##
environment location: /opt/conda
removed specs:
- mamba
The following packages will be REMOVED:
mamba-1.5.3-py310h51d5547_2
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
(base) [conda@0fc3fa546c5d ~]$ conda install -yq --no-deps mamba=1.5.3
Channels:
- conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
## Package Plan ##
environment location: /opt/conda
added / updated specs:
- mamba=1.5.3
The following NEW packages will be INSTALLED:
mamba conda-forge/linux-64::mamba-1.5.3-py310h51d5547_2
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
(base) [conda@0fc3fa546c5d ~]$ mamba update -d conda
Looking for: ['conda']
warning libmamba Cache file "/opt/conda/pkgs/cache/497deca9.json" was modified by another program
warning libmamba Cache file "/opt/conda/pkgs/cache/09cdf8bf.json" was modified by another program
conda-forge/noarch 12.8MB @ 14.6MB/s 0.9s
conda-forge/linux-64 31.0MB @ 15.3MB/s 2.2s
Pinned packages:
- python 3.10.*
- su-exec 0.2
- tini 0.19.0
Transaction
Prefix: /opt/conda
Updating specs:
- conda
- ca-certificates
- certifi
- openssl
Package Version Build Channel Size
──────────────────────────────────────────────────────────────────
Install:
──────────────────────────────────────────────────────────────────
+ menuinst 2.0.0 py310hff52083_1 conda-forge 134kB
+ distro 1.8.0 pyhd8ed1ab_0 conda-forge 41kB
Upgrade:
──────────────────────────────────────────────────────────────────
- libmamba 1.5.3 had39da4_2 conda-forge Cached
+ libmamba 1.5.4 had39da4_0 conda-forge 2MB
- libmambapy 1.5.3 py310h39ff949_2 conda-forge Cached
+ libmambapy 1.5.4 py310h39ff949_0 conda-forge 302kB
- conda 23.10.0 py310hff52083_1 conda-forge Cached
+ conda 23.11.0 py310hff52083_1 conda-forge 979kB
- mamba 1.5.3 py310h51d5547_2 conda-forge Cached
+ mamba 1.5.4 py310h51d5547_0 conda-forge 52kB
Summary:
Install: 2 packages
Upgrade: 4 packages
Total download: 3MB
──────────────────────────────────────────────────────────────────
Dry run. Exiting.
DryRunExit: Dry run. Exiting.
As said, this is all in containers from the current |
|
Hey folks, sorry for the brevity as I type this afk. IIUC, this has to do with the history blocking the update. The usual workaround is to enumerate all the packages that should be updated:
Let me know if that helps. There's a rationale behind this that I'd be happy to discuss too, but it's a bit tricky to type all of that on the phone. |
tl;dr Such a CI pipeline already exists, but it requires more attention when it fails To clarify, the mamba repository already has a CI pipeline to test against conda from the conda-canary channel. It runs every Sunday https://github.com/mamba-org/mamba/blob/main/.github/workflows/conda_canary.yml It opens an Issue if it fails, and it has been failing for weeks for unrelated reasons https://github.com/mamba-org/mamba/issues?q=is%3Aissue+Bot+failure+ Unfortunately the PR to fix the scheduled canary build (#2950) wasn't merged prior to the release of conda 23.11.0. The CI run on this PR actually caught this compatibility error: #3029 (comment) Now that the CI fix has been merged, the canary CI is passing again, I assume thanks to the recently merged PR #3040 https://github.com/mamba-org/mamba/actions/runs/7114168786 Thus in order to catch these types of compatibility errors prior to the next release, we don't necessarily need more CI infrastructure (though more is always better), but we do need to better monitor and address the Issues that are auto-opened when a canary CI run fails |
|
I just want to comment that it cannot possibly be correct behavior for “mamba update —all” to make updates to the packages that violate constraints from the downloaded repodata. |
|
mamba repoquery search not working. Mamba version 1.5.6. Conda version 23.11.0. Python 3.11 |
|
I also found this and finally decided to start over with a fresh Miniforge and stop using the mamba commands at all. The conda commands seem to be just as fast with the libmamba solver installed. |
Can you post the result of # Name Version Build Channel
_libgcc_mutex 0.1 conda_forge conda-forge2
_openmp_mutex 4.5 2_gnu conda-forge2
archspec 0.2.2 pyhd8ed1ab_0 conda-forge2
boltons 23.0.0 pyhd8ed1ab_0 conda-forge2
brotli-python 1.0.9 py310hd8f1fbe_9 conda-forge2
brotlipy 0.7.0 py310h5764c6d_1005 conda-forge2
bzip2 1.0.8 h7f98852_4 conda-forge2
c-ares 1.24.0 hd590300_0 conda-forge2
ca-certificates 2023.11.17 hbcca054_0 conda-forge2
certifi 2023.11.17 pyhd8ed1ab_0 conda-forge2
cffi 1.15.1 py310h255011f_3 conda-forge2
charset-normalizer 3.2.0 pyhd8ed1ab_0 conda-forge2
colorama 0.4.6 pyhd8ed1ab_0 conda-forge2
conda 23.11.0 py310hff52083_1 conda-forge2
conda-libmamba-solver 23.12.0 pyhd8ed1ab_0 conda-forge2
conda-package-handling 2.2.0 pyh38be061_0 conda-forge2
conda-package-streaming 0.9.0 pyhd8ed1ab_0 conda-forge2
cryptography 41.0.2 py310h75e40e8_0 conda-forge2
distro 1.9.0 pyhd8ed1ab_0 conda-forge2
fmt 10.1.1 h00ab1b0_1 conda-forge2
icu 72.1 hcb278e6_0 conda-forge2
idna 3.4 pyhd8ed1ab_0 conda-forge2
jsonpatch 1.32 pyhd8ed1ab_0 conda-forge2
jsonpointer 2.0 py_0 conda-forge2
keyutils 1.6.1 h166bdaf_0 conda-forge2
krb5 1.21.2 h659d440_0 conda-forge2
ld_impl_linux-64 2.40 h41732ed_0 conda-forge2
libarchive 3.7.2 h039dbb9_0 conda-forge2
libcurl 8.5.0 hca28451_0 conda-forge2
libedit 3.1.20191231 he28a2e2_2 conda-forge2
libev 4.33 h516909a_1 conda-forge2
libffi 3.4.2 h7f98852_5 conda-forge2
libgcc-ng 13.1.0 he5830b7_0 conda-forge2
libgomp 13.1.0 he5830b7_0 conda-forge2
libiconv 1.17 h166bdaf_0 conda-forge2
libmamba 1.5.6 had39da4_0 conda-forge2
libmambapy 1.5.6 py310h39ff949_0 conda-forge2
libnghttp2 1.58.0 h47da74e_1 conda-forge2
libnsl 2.0.0 h7f98852_0 conda-forge2
libsolv 0.7.24 hfc55251_1 conda-forge2
libsqlite 3.42.0 h2797004_0 conda-forge2
libssh2 1.11.0 h0841786_0 conda-forge2
libstdcxx-ng 13.1.0 hfd8a6a1_0 conda-forge2
libuuid 2.38.1 h0b41bf4_0 conda-forge2
libxml2 2.11.5 h0d562d8_0 conda-forge2
libzlib 1.2.13 hd590300_5 conda-forge2
lz4-c 1.9.4 hcb278e6_0 conda-forge2
lzo 2.10 h516909a_1000 conda-forge2
mamba 1.5.6 py310h51d5547_0 conda-forge2
menuinst 2.0.1 py310hff52083_0 conda-forge2
ncurses 6.4 hcb278e6_0 conda-forge2
openssl 3.2.0 hd590300_1 conda-forge2
packaging 23.1 pyhd8ed1ab_0 conda-forge2
pip 23.1.2 pyhd8ed1ab_0 conda-forge2
platformdirs 4.1.0 pyhd8ed1ab_0 conda-forge2
pluggy 1.2.0 pyhd8ed1ab_0 conda-forge2
pybind11-abi 4 hd8ed1ab_3 conda-forge2
pycosat 0.6.4 py310h5764c6d_1 conda-forge2
pycparser 2.21 pyhd8ed1ab_0 conda-forge2
pyopenssl 23.2.0 pyhd8ed1ab_1 conda-forge2
pysocks 1.7.1 pyha2e5f31_6 conda-forge2
python 3.10.12 hd12c33a_0_cpython conda-forge2
python_abi 3.10 3_cp310 conda-forge2
readline 8.2 h8228510_1 conda-forge2
reproc 14.2.4 h0b41bf4_0 conda-forge2
reproc-cpp 14.2.4 hcb278e6_0 conda-forge2
requests 2.31.0 pyhd8ed1ab_0 conda-forge2
ruamel.yaml 0.17.32 py310h2372a71_0 conda-forge2
ruamel.yaml.clib 0.2.7 py310h1fa729e_1 conda-forge2
ruamel_yaml 0.15.80 py310h5764c6d_1008 conda-forge2
setuptools 68.0.0 pyhd8ed1ab_0 conda-forge2
tk 8.6.12 h27826a3_0 conda-forge2
toolz 0.12.0 pyhd8ed1ab_0 conda-forge2
tqdm 4.65.0 pyhd8ed1ab_1 conda-forge2
truststore 0.8.0 pyhd8ed1ab_0 conda-forge2
tzdata 2023c h71feb2d_0 conda-forge2
urllib3 2.0.3 pyhd8ed1ab_1 conda-forge2
wheel 0.40.0 pyhd8ed1ab_0 conda-forge2
xz 5.2.6 h166bdaf_0 conda-forge2
yaml 0.2.5 h7f98852_2 conda-forge2
yaml-cpp 0.8.0 h59595ed_0 conda-forge2
zstandard 0.22.0 py310h1275a96_0 conda-forge2
zstd 1.5.5 hfc55251_0 conda-forge2EDIT: don't pay attention to the |
|
Is there a chance Python 3.11 is in use? xref conda/conda-libmamba-solver#303 for context. |
I was using Python 3.11. I suspect it is Python 3.11 that has the problem.
Yes. I was using Python 3.11. Rolling back to Python 3.10 fixed the issue for me. |
|
Same issue: mamba
|
|
@LiutongZhou, @b-a0, could you provide information of you installations, i.e., the outputs of |
|
Sure, this is the output after downgrading my base environment to python 3.10.
|
|
Thanks, @b-a0. |
|
Should be fixed by gh-3170 once we have those changes released. |
After lowering conda to 23.10 with this method, everything is updating normally again. Thank you. |
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
is:issue is:open 1.5.3
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
Mamba 1.5.3 refuses to run any command. It always fails with "Currently, only install, create, list, search, run, info, clean, remove, update, repoquery, activate and deactivate are supported through mamba."
In the following output, I do the following:
mamba infoin the base environment, works as expectedmambaon the base environment to latest (1.5.3)mamba info, now it fails with "Currently, only install, create, list, search, run, info, clean, remove, update, repoquery, activate and deactivate are supported through mamba."Not showing in the output, but downgrading to 1.5.2 makes
mambawork again. Then mysteriously upgrading to 1.5.3 again works.Output
mamba info / micromamba info
Logs
environment.yml
No response
~/.condarc
No response
The text was updated successfully, but these errors were encountered: