mamba · Issues· 453 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #4165
mamba run fails in non-TTY runners with "Undefined error: 0"
status::user_reply_neededUpdated Sep 14, 2026 - #4393
Track conda-forge win-arm64 packages needed to drop environment-dev-win-arm64.yml
type::general-improvementwhat::ciwhere::windowsUpdated Sep 7, 2026 - #4394
[libmamba] Per-package repodata `url`/`urls` are discarded: `set_solvables_url` overwrites every solvable's URL with the channel-derived one
Updated Sep 1, 2026 - #1885
Mamba does not include configured subdirs in package search
type::bugUpdated Aug 26, 2026 - #4392
Long path support not enabled on AppVeyor with 2.9
Updated Aug 25, 2026 - #4389
Security warning should mention which package executes package scripts
Updated Aug 19, 2026 - #4372
Check/Add specific tests
Updated Aug 5, 2026 - #3879
`mamba activate` fails in Windows after starting cmd.exe with `activate.bat`, shell not initialized
where::windowsUpdated Aug 5, 2026 - #4263
Surprisingly hard environment specification to solve for `libsolv`
Updated Aug 4, 2026 - #4156
BUG: mamba does not apply repodata patches for already-downloaded packages
Updated Aug 4, 2026 - #4014
error libmamba Could not solve for environment specs
Updated Jul 31, 2026 - #3535
Missing command options in micromamba
type::feature-requesttype::general-improvementUpdated Jul 29, 2026 - #4216
`micromamba run` should accept a trailing `--` as `conda` does
type::feature-requestUpdated Jul 27, 2026 - #4360
Allow cancelling when waiting for other mamba process to finish
Updated Jul 27, 2026 - #3684
Micromamba: Cannot activate env because cannot initialize shell cmd.exe (corp env)
where::windowsUpdated Jul 11, 2026