On Wed, 18 Aug 2021 at 12:07, Ricardo Wurmus
wrote:
We have since upgraded to 4.10.3, but the problems still
persist. Conda still
asks users to run “conda init”, which attempts to run “sudo”
to modify
root-owned files. It’s a big mess.
I don't think conda init will ever work on Guix, and
Dominic Martinez writes:
> [[PGP Signed Part:Undecided]]
>
>>> On Wed, 18 Aug 2021 at 12:07, Ricardo Wurmus
>>> wrote:
We have since upgraded to 4.10.3, but the problems still
persist. Conda still
asks users to run “conda init”, which attempts to run “sudo”
to modify
>>>
zimoun writes:
> On Wed, 18 Aug 2021 at 12:07, Ricardo Wurmus wrote:
>> We have since upgraded to 4.10.3, but the problems still persist. Conda still
>> asks users to run “conda init”, which attempts to run “sudo” to modify
>> root-owned files. It’s a big mess.
>
> What is the point to have C
Hi Ricardo,
On Wed, 18 Aug 2021 at 12:07, Ricardo Wurmus wrote:
> We have since upgraded to 4.10.3, but the problems still persist. Conda still
> asks users to run “conda init”, which attempts to run “sudo” to modify
> root-owned files. It’s a big mess.
What is the point to have Conda installed
We have since upgraded to 4.10.3, but the problems still persist.
Conda still asks users to run “conda init”, which attempts to run
“sudo” to modify root-owned files. It’s a big mess.
Any ideas?
--
Ricardo
Hi Ricardo et al.,
I've not yet looked into updating the conda package, but want to add a
small thing to the bug report, so it can easily be found.
Lines in the sourced conda.sh script like the one below won't work anymore
once the conda executable is wrapped in the guix shell script, because PS1
Hi Ricardo,
On Tue, 25 Aug 2020 at 14:35, Ricardo Wurmus wrote:
>
> > The problem with the prompt arises from step 4), because 'conda' has bash
> > as interpreter, and "non-interactive bashes go out of their way to unset
> > PS1":
> >
> https://superuser.com/questions/663069/why-does-subshell-no
Hi Hugo,
> The problem with the prompt arises from step 4), because 'conda' has bash
> as interpreter, and "non-interactive bashes go out of their way to unset
> PS1":
> https://superuser.com/questions/663069/why-does-subshell-not-inherit-exported-variable-ps1
> https://tldp.org/HOWTO/Bash-Promp
Just sharing a bit of more info about why the conda prompt breaks.
On Fri, 21 Aug 2020 at 05:52, Ricardo Wurmus wrote:
>
> Hugo Buddelmeijer writes:
>
> > 2. The prompt is not set correctly, as in, what should happen is that the
> > current conda environment is added to the prompt. Instead, the
Hugo Buddelmeijer writes:
> So there are three problems:
>
> 1. The PATHS in .bashrc should be to ~/.guix-profile/etc/profile.d/, not to
> /gnu/store directly. This is trivial to fix manually.
Perhaps we can replace these locations with
${GUIX_PROFILE:-/gnu/store/…} just as we do in our genera
Hi Ricardo,
On Wed, 19 Aug 2020 at 12:07, Ricardo Wurmus wrote:
>
> > The conda 4.8.3 package on guix does not seem to work as expected.
>
> Thanks for letting me know. The upgrade took a long time and required
> quite a bit of patching.
>
Thanks for doing this hard work! It is much appreciate
Hi Hugo,
> The conda 4.8.3 package on guix does not seem to work as expected.
Thanks for letting me know. The upgrade took a long time and required
quite a bit of patching.
> But activating it does not work properly:
>
> hugo@alex ~$ conda activate testenv
>
> CommandNotFoundError: Your shell
Dear Ricardo et al.,
The conda 4.8.3 package on guix does not seem to work as expected.
Conda info:
hugo@alex ~$ which conda
/home/hugo/.guix-profile/bin/conda
hugo@alex ~$ realpath $(which conda)
/gnu/store/ihn8dbs84rmc3ai7r1vkvh4cya518wmx-conda-4.8.3/bin/conda
hugo@alex ~$ conda -V
conda 4.8.3
13 matches
Mail list logo
