Skip to content
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

Update README.md: some information about Arch #17

Closed
wants to merge 1 commit into from
Closed

Update README.md: some information about Arch #17

wants to merge 1 commit into from

Conversation

alerezaaa
Copy link

Hi

I installed miniconda3 from AUR and I couldn't install conda-bash-completion using provided command in Normal user (I dont know why)

I tried installing it by root user and it was successful, so I decided to add this part which maybe helpful

Thanks

@tartansandal
Copy link
Owner

Hi @alerezaaa. Thanks for the PR. 😄

The root cause of the problem is the AUR miniconda package installing into a directory that a normal user does not have write permissions, but without documenting how that normal user is then expected to use the conda command.

This problem is going to occur for any conda package installed with this AUR miniconda. Looking at the comments under https://aur.archlinux.org/packages/miniconda3, I see the same problem with installing jupyterlab.

Running the conda commands as root does work, but it's not ideal for the security of your system.

A better solution is documented here. The special group should really be created by the AUR package and instructions for its use documented by the package maintainer. There is probably another solution involving environment variables, but it's up to the AUR package maintainer(s) to solve all the related problems and document how it is supposed to work.

I'm closing this PR for now, because I don't think it is the right place to document getting conda-bash-completion to work in this situation. Please feel free to comment or reopen if you think I've got this wrong. ☝️

Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants