Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • 09:51
    dbast synchronize #11909
  • 09:36
    dholth commented #11794
  • 09:27
    ForgottenProgramme labeled #11900
  • 09:25
    pre-commit-ci[bot] synchronize #11909
  • 09:21
    dbast commented #11909
  • 09:18
    pre-commit-ci[bot] synchronize #11909
  • 09:16

    dbast on pyupgrade


  • 09:15
    dbast synchronize #11909
  • 09:15

    dbast on pyupgrade

    Add pyupgrade to pre-commit (compare)

  • 09:14
    dbast commented #11909
  • 09:13
    conda-bot labeled #11909
  • 09:13
    dbast opened #11909
  • 04:41
    github-actions[bot] labeled #10998
  • 04:41
    github-actions[bot] commented #10998
  • 04:41
    github-actions[bot] labeled #10821
  • 04:41
    github-actions[bot] unlabeled #10821
  • 04:41
    github-actions[bot] closed #10202
  • 04:41
    github-actions[bot] labeled #10202
  • 04:41
    github-actions[bot] labeled #7713
  • 04:41
    github-actions[bot] commented #7713
I have conda installed by rpm on Centos 7.
I created a conda environment and installed conda on the environment.
The conda provided by the rpm masks the conda in the environment.
How should I configure the conda environment so that the conda inside the environment is used instead?
Pat Gunn
Is there a reason you didn't update the base environment instead?
@aceenprsu Anyhow, you should be able to edit the rpm-based conda init stuff out of your environment and put a replacement with different paths in your dotfiles
All the rpm does, presumably, is edit the /etc/profile.d/ and similar standard dotfiles; have your account dotfiles undo those changes and init with your conda env.
(the term "environment" might be a bit confusing here as it could either mean a conda virtualenv-based environment, or an install of the conda codebase with its individual environment store and so on)
Pat Gunn

I'm running into an issue where I cannot create a new environment with conda create ... with an existing conda install (with a lot of other environments), but I can make the same environment with a completely fresh install of conda. Any idea what might cause this?

(I'm actually trying to help out a user with this problem; there may be some turnaround in poking around)

Jaime Rodríguez-Guerra
what's the error? it might be due to conda versions, space limitations, permissions... plenty of possible causes
Pat Gunn
Version conflicts between packages.
Jaime Rodríguez-Guerra
have you added extra configuration keys to your .condarc? e.g. create_default_packages, pinned_packages, aggresive_updates?
or maybe the default channels are different?
Pat Gunn
I asked this prematurely; I need to get access to this person's laptop to see what's going on. Probably really inefficient to try to manage those timescales and gitter. Thanks for the ideas though.
Jaime Rodríguez-Guerra
No problem! Ping me if needed!
Faustin Carter
When running conda-build on Windows, I'm getting a bunch of new output related to LIEF. Is there a way to skip these ( other than downgrading to an earlier version of conda-buidl?)
Christian Roth

Can anybody help me understand how to read this solving config error?

Package cudnn conflicts for:
pytorch-lightning=1.4.5 -> pytorch[version='>=1.6'] -> cudnn[version='>=7.6,<8.0a0|>=,<8.0a0|>=,<9.0a0|>=,<9.0a0']
pytorch::torchvision=0.10.0 -> pytorch==1.9.0 -> cudnn[version='>=,<8.0a0|>=,<9.0a0']The following specifications were found to be incompatible with your system:

  - feature:/linux-64::__glibc==2.27=0
  - nvidia::cudatoolkit=11.1.1 -> __glibc[version='>=2.17,<3.0.a0']
  - pytorch-lightning=1.4.5 -> pytorch[version='>=1.6'] -> __glibc[version='>=2.17|>=2.17,<3.0.a0']
  - pytorch::pytorch=1.9.0 -> cudatoolkit[version='>=11.1,<11.2'] -> __glibc[version='>=2.17,<3.0.a0']
  - pytorch::torchvision=0.10.0 -> cudatoolkit[version='>=11.1,<11.2'] -> __glibc[version='>=2.17|>=2.17,<3.0.a0']

Your installed version is: 2.27

Why would __glibc==2.27 conflict with __glibc[version='>=2.17|>=2.17,<3.0.a0']? What am I overlooking here?

Jaime Rodríguez-Guerra
Might be a red herring. If pytorch is involved (which requires 2.17 as you see), there's a chance a package for 2.12 is involved somehow in the dependency tree. Try solving with mamba and see if their error is a bit clearer.
1 reply
Marcelo Duarte Trevisani
Could someone please review this PR?
Maximilian Koch

Hi all,

I'm trying to build a package which includes h5py. When using conda build, it seems to install the wrong version of the dependency. It installs 3.2.1-py37h6c542dc_0, which includes hdf5: 1.10.6-nompi_h6a2412b_1114. The problem is that this hdf5 lib, seems to have these setting:
(Read-Only) S3 VFD: yes

This causes an error for me. When just running conda install h5py==3.2.1, it does install the right version.

Chris Meyer
Hi all, I noticed that packages for Python 3.10 are starting to become available. However, some packages (like h5py) are not yet available on Windows. h5py depends on pkgconfig, which is also not available on Windows. Are these packages expected to be available currently or are they still being built or is there some other reason they are not available on Windows?
Pat Gunn
Could whomever maintains the anaconda/miniconda docker images consider adding mamba to those images? It's pretty important for CI use.
7 replies
Isuru Fernando
@jezdez, can we speed up the conda-build issue/PR locking? I get around 5 emails everyday for about 5 days now and it's annoying
2 replies
cc @chenghlee
Fred Eisele
Is there a way to promote a conda environment to configure the default os environment?
I am not referring to the conda base environment.
Benjamin Bertrand
conda environments are isolated by nature. What I have done in the past is to automatically activate a specific environment using a file under /etc/profile.d on Linux so that users can use that env directly. For command line tools, another solution I used is to create simple wrappers under /usr/local/bin. Users can launch a tool without knowing it's installed in a conda env.
Ian Stokes-Rees
I'm getting repeated HTTPS connection errors from conda when trying to do conda update conda (currently running 4.11.0) -- using --debug the problem seems to be [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate -- is this just me or is there some kind of server-side issue? If it is just me can someone suggest what I need to do to correct this?
1 reply
Pat Gunn
I'm wondering if there's an existing tool to relocate a conda directory, before I get too deep into writing one for our particular needs
Right now it looks like the user's conda install path gets written into a lot of things under each environment's BASE/bin, the main CONDA_BASE/bin, as well as ~/.conda/environments.txt
Pat Gunn
It looks like conda-pack does a subset of what I want, but I was hoping for something that rewrites paths for every environment
Jannis Leidel
Andrew Kapocsi
The link to the conda mailing list in the README of the conda repo is dead: https://github.com/conda/conda#getting-help
Anyone know if there is a replacement?
Leo Fang
Any chance CDN sync has not happened in the past ~4 hrs? I am seeing packages that were uploaded a few hrs ago are not yet visible to the conda solver.
1 reply
the new multi-platform conda-ci container enable much faster test executions on Apple M1:
  • time docker run --platform linux/amd64 --rm -v ${PWD}:/opt/conda-src -e TEST_SPLITS=3 -e TEST_GROUP=1 ghcr.io/conda/conda-ci:master-linux-python3.9 /opt/conda-src/dev/linux/unit.sh needs 9:17.24
  • time docker run --platform linux/arm64 --rm -v ${PWD}:/opt/conda-src -e TEST_SPLITS=3 -e TEST_GROUP=1 ghcr.io/conda/conda-ci:master-linux-python3.9 /opt/conda-src/dev/linux/unit.sh needs 2:41.42 -> factor 3.4 faster :)
1 reply
Getting 403 errors trying to install pytorch packages with conda -- is there any known outages right now? --
The packages are listed in the directory listing for the server, but clicking on them gives an XML error and 403 message saying "Access Denied" and "Request has Expired":
Mark Harfouche
There was a known outage. Not sure if it is resolved. Definitely fewer error this morning.
might be related.
Cheng H. Lee
It was cloudflare-related but nothing to do with the outages posted on their status page. In any case, Anaconda pushed a hotfix to anaconda.org that should mitigate the issue.
1 reply
Heya! keeps trying to install different Python versions and then failing when it doesn't find some dep - example error: - nothing provides openssl >=1.1.1,< needed by python-3.7.1-h0371630_3
I explicitly put python==3.8.* (also tried it with a single = in my yaml file.
Not really sure what to do? Is there a reliable way to pin the Python version? Is there a reliable way to do detective work and see what package in my yaml file is responsible for this chain of events?
Stephen Nayfach
I updated my package checkv yesterday (https://anaconda.org/bioconda/checkv) but the new version (1.0.0) still is not available when I run conda install -c bioconda checkv. Is there something I did wrong when I updated the recipe?
1 reply
Dave Clements
We are pleased to announce that conda 4.14.0 & conda-build 3.22.0 releases are now available, featuring
⇒ rename conda environments
⇒ channel notifications
⇒ better error handling
⇒ and more!
Many thanks to all our contributors, especially the 14 new contributors who helped make this happen
Griffin Tabor

So I ran into this trying to update figure out the right workflow for my system

So its clear what I want to do is not the "conda approved" workflow so I am trying to figure out the right method.

I have software repo A that provides a conda environment to run it. Then I have software repo B that uses repo A as a dependency but also adds a number of additional dependencies that are not needed for repo A.

It seems like what I would want is to specify a new environment in repo B that is something like "these dependencies plus whatever is in the repo A environment file" and for the package manager to solve for if that's possible (and it will be) and build me that environment. If its not possible it would throw and error just like it does if I make a single environment file that isn't possible, like asking for specific versions of packages that don't go together.

What is the suggested workflow for this? Would env update second_file.yaml work to add second set of dependencies?

Alan Hoyle
I installed a tool with micromamba on a CentOS 7 machine. The install worked fine, but when I try to run it, I get an error: ImportError: libffi.so.7: cannot open shared object file: No such file or directory I see libffi.so.6 in the system lib64, and libffi.so.8 in my ~/micromamba/lib (it's a symbolic link to somewhere else in the hierarchy). Is this most likely a problem with the conda package?
1 reply
Daniel Holth
Hello condans
Jaime Rodríguez-Guerra
Pat Gunn
I'm wondering if people have hints as to how to debug when a package on a conda channel is not considered a candidate for installation (apart from the obvious "wrong arch")
Pat Gunn
This fails: conda create -n assimp_test -c flyem-forge -c conda-forge assimp=4.0.1 but I can see in the flyem-forge channel that there is a Linux package of assimp 4.0.1. Unclear how to debug further
4 replies
Pat Gunn
Weird. I can download the bz2 package and manually put it into an environment first, then build the rest of the environment. Wondering if this is some channel index issue