unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Hugo Buddelmeijer <hugo@buddelmeijer.nl>
To: 59772@debbugs.gnu.org
Subject: bug#59772: conda 22.9.0 breaks "conda init bash"
Date: Fri, 2 Dec 2022 12:48:53 +0100	[thread overview]
Message-ID: <CA+Jv8O0siPiEMzzgLYNDJ=P-O7Y3MXJ+LoxURC9tXFx4juLn9A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

Hi all,

Conda 22.9.0 breaks "conda init bash". Conda requires some functions to be
present in ~/.bashrc (or equivalent dot file for other shells) in order to
function as intended [*]. These functions are added there through "conda
init bash", which each conda user should run once.

$ guix shell -C conda sudo

[env]$ conda --version
conda 22.9.0

[env]$ conda init bash
[..]
      File
"/gnu/store/lvip6h5pamjwmvnkwg60sjb63ph8698k-python-3.9.9/lib/python3.9/subprocess.py",
line 19
59, in _communicate
        input_view = memoryview(self._input)
    TypeError: memoryview: a bytes-like object is required, not 'str'
[...]

However, it seems that this is a conda problem (not sure), and not a guix
problem. E.g. see
   https://github.com/conda/conda/issues/11885
   "conda 22.9.0 breaks bash command prompt"
The suggested solution there is to do "sudo $(which conda) init bash",
which is not really acceptable for us.

Also, "conda init bash" does seem to actually do what it is supposed to do:
add conda functions to ~/.bashrc; the error occurs after that. So maybe we
can just wait this out, or try to see whether it works with conda 22.11.0.

Greetings,
Hugo

[*] There are also some problems in the interplay between guix and the
conda functions in .bashrc. I'll report those later.

[-- Attachment #2: Type: text/html, Size: 1761 bytes --]

                 reply	other threads:[~2022-12-02 11:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CA+Jv8O0siPiEMzzgLYNDJ=P-O7Y3MXJ+LoxURC9tXFx4juLn9A@mail.gmail.com' \
    --to=hugo@buddelmeijer.nl \
    --cc=59772@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).