[X] My problem is not solved in the Troubleshooting docs
Anaconda default channels
[X] I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
Micromamba
Search tried in issue tracker
umask
Latest version of Mamba
[X] My problem is not solved with the latest version
Tried in Conda?
Not applicable
Describe your issue
I'm looking into some reports having to do with umask and permissions. Apparently some files of the Miniconda and Miniforge installations are extracted with permissions that do not respect the users umask.
I looked into what conda-standalone does for this, and we were blindly taking contents from the tarball (not the packages, but the installer logic) blindly. This led to ignoring the umask settings.
I'm opening this issue to discuss whether micromamba needs a similar fix. For conda-standalone, this was enough, thanks to this PR in conda-package-handling. You might want to take a look :D
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Micromamba
Search tried in issue tracker
umask
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
I'm looking into some reports having to do with
umaskand permissions. Apparently some files of the Miniconda and Miniforge installations are extracted with permissions that do not respect the users umask.I looked into what conda-standalone does for this, and we were blindly taking contents from the tarball (not the packages, but the installer logic) blindly. This led to ignoring the umask settings.
I'm opening this issue to discuss whether micromamba needs a similar fix. For conda-standalone, this was enough, thanks to this PR in conda-package-handling. You might want to take a look :D
xref https://github.com/conda-forge/miniforge/issues/506#issue-1968846490.
mamba info / micromamba info
No response
Logs
No response
environment.yml
No response
~/.condarc
No response