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

INSTALL.sh cannot find conda installation #9

Open
balabanmetin opened this issue Jan 14, 2021 · 1 comment
Open

INSTALL.sh cannot find conda installation #9

balabanmetin opened this issue Jan 14, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@balabanmetin
Copy link

I have miniconda 4.6.10 installed in my machine. In this version, "conda" command does not execute a binary file directly, it is a function added to .bashrc during installation. INSTALL.sh checks whether conda is installed using the "command -v" command. this command cannot locate functions defined in bashrc. As a result, PEWO installation fails with the error message :
PEWO installer: Command 'conda' not found.
PEWO installer: This is a requirement to PEWO installation. See documentation.

@balabanmetin balabanmetin changed the title INSTALL.sh cannot find condo installation INSTALL.sh cannot find conda installation Jan 14, 2021
@blinard-BIOINFO
Copy link
Member

blinard-BIOINFO commented Jan 15, 2021

Hi,
command is a bash built-in and PEWO installation script calls #!/bin/bash.
And as you mentionned, conda installation adds an init block at the end of the bashrc file.
Not this is default behaviour, but alternatives initialisation methods exists.

I agree this make one assumption : bash is installed and used to install PEWO. Now, considering that the vast majority of Unix systems comes with bash built-in, this should be fine.

In your case, you need to understand if your bashrc is not read correctly at session initialisation or if the conda init block is somehow not functionnal. If it was, the conda command would be available in your bash session, this is the default behaviour in a bash+conda installation.

Maybe you run a session in a cluster (via slumr/qsub?) which do not use bash ? another user which has another bashrc not containing the conda init block ?

Also, if you have suggestion for an alternative test, I'm happy to consider them.

@blinard-BIOINFO blinard-BIOINFO added documentation Improvements or additions to documentation enhancement New feature or request and removed documentation Improvements or additions to documentation labels Jan 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants