From: Frederick Muriithi <fredmanglis@gmail.com>
To: 27858@debbugs.gnu.org
Subject: bug#27858: Conda (on guix) does not activate environments
Date: Fri, 28 Jul 2017 08:49:26 +0300 [thread overview]
Message-ID: <CALjrZwatbyJ+8-GGXEBG8aGjfWMDY0MnNEiL2kKS6b2mFtc9Mg@mail.gmail.com> (raw)
I have come across a bug on conda, installed via guix, that does not
seem to be present when conda is installed via the process at
https://conda.io/docs/install/quick.html#linux-miniconda-install
The issue
---------
Conda (on guix) does not activate environments
Command ran
-----------
source activate test-env
Expected result
---------------
The envinment should be activated, and the prompt changes from
`frederick@localhost:/tmp$` to `(test-guix-conda)
frederick@localhost:/tmp$`
Actual result
-------------
The terminal window is exited.
Additional information
----------------------
This behaviour is not present on conda installed via the process
presented in the conda documentation.
The environment(s) created by conda on guix are available on, and can
be activated by conda installed via the process in the conda
documentation.
I ran `bash -c "source activate test-env"` and the following error
message was displayed:
/gnu/store/f2dr9xbimg93pljm7xgmqb4cm5bxy98r-conda-4.3.16/bin/.deactivate-real:
line 59: return: can only `return' from a function or sourced script
/gnu/store/f2dr9xbimg93pljm7xgmqb4cm5bxy98r-conda-4.3.16/bin/.deactivate-real:
line 94: return: can only `return' from a function or sourced script
I would appreciate any help that would help in resolving this issue.
next reply other threads:[~2017-07-28 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 5:49 Frederick Muriithi [this message]
2017-07-28 9:36 ` bug#27858: Conda (on guix) does not activate environments Pjotr Prins
2017-07-28 9:42 ` Frederick Muriithi
2021-02-01 19:37 ` Maxim Cournoyer
2017-07-28 10:20 ` Frederick Muriithi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALjrZwatbyJ+8-GGXEBG8aGjfWMDY0MnNEiL2kKS6b2mFtc9Mg@mail.gmail.com \
--to=fredmanglis@gmail.com \
--cc=27858@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).