Open gzm55 opened 1 week ago
This is because of the way things are packaged in conda-forge, which (after many many years of talking about it), switch to CentOS 7 / glibc 2.17 by default a few months ago. If you can convince the mamba-feedstock maintainers, it might still technically be possible to opt into building against an older c_stdlib_version
...
This is because of the way things are packaged in conda-forge, which (after many many years of talking about it), switch to CentOS 7 / glibc 2.17 by default a few months ago. If you can convince the mamba-feedstock maintainers, it might still technically be possible to opt into building against an older
c_stdlib_version
...
this breaking change should be introduced in mamba 2.0, not a patch version.
This is because of the way things are packaged in conda-forge, which (after many many years of talking about it), switch to CentOS 7 / glibc 2.17 by default a few months ago. If you can convince the mamba-feedstock maintainers, it might still technically be possible to opt into building against an older
c_stdlib_version
...
@h-vetinari did you mean https://github.com/conda-forge/mamba-feedstock this repo?
Given the title of the issue, you probably want https://github.com/conda-forge/micromamba-feedstock
this breaking change should be introduced in mamba 2.0, not a patch version.
CentOS 6 is EOL for 4 years. It's not a breaking change, you're just on an unsupported system. (Also, how would you imagine 1000s of libraries to all synchronize a new major version release for a change like this? 🤔)
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Micromamba
Search tried in issue tracker
glibc
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
from 1.5.9, micromamba requires GLIBC 2.17, which cannot run on CentOS 6.
mamba info / micromamba info
No response
Logs
No response
environment.yml
No response
~/.condarc
No response