by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 13:24
    cristi-neagu commented #10053
  • 13:23
    cristi-neagu commented #10013
  • 10:37
    lhoupert opened #10059
  • 06:36
    JohnatanPalacios commented #8612
  • 06:36
    JohnatanPalacios commented #8612
  • 06:36
    JohnatanPalacios commented #8612
  • 05:43
    Myridium commented #9735
  • 00:45
    Davidvandijcke commented #6986
  • Jul 09 17:48
    drishh207 commented #9867
  • Jul 09 17:35
    analog-cbarber commented #9665
  • Jul 09 16:21
    necaris commented #8727
  • Jul 09 15:13
    aakhmetz closed #10020
  • Jul 09 15:13
    aakhmetz commented #10020
  • Jul 09 14:00
    necaris synchronize #8727
  • Jul 09 13:48
    jrockwar commented #9038
  • Jul 09 13:03
    necaris synchronize #8727
  • Jul 09 13:03
    necaris synchronize #8727
  • Jul 09 13:00
    necaris synchronize #8727
  • Jul 09 12:56
    necaris synchronize #8727
  • Jul 09 12:00
    necaris review_requested #8727
Michael Milton
@TMiguelT
I think you can force a downgrade with conda install python=3.7
Or something like that
Vincent
@vsiles
Will try. Thanks for the assist ! Have a nice day
Wolf Vollprecht
@wolfv
@kalefranz @jjhelmus btw if you guys ever want to have a discussion on mamba / micromamba just let me know ... I would be more than happy to talk a little about our current plans if you are interested
Wolf Vollprecht
@wolfv
specifically micromamba is a pure C++ implementation of conda/mamba that we can hopefully soon compile into a small, statically linked binary that can be used on CI services
and one next thing I really want to tackle soon(ish) is mamba-build because we have super-large meta.yaml files with hundreds of outputs for ROS recipes and it takes too long with conda-build
I believe with the new API of mamba it will be fairly straightforward to implement the package building part
Matthew R Becker
@beckermr
@wolfv would it be possible to simply add hooks to conda-build so that it can call the mamba solver?
this idea is from @msarahan
Wolf Vollprecht
@wolfv
I haven’t looked into conda build that much yet
Would be cool if that was possible indeed
But I also want to change some things on a logic level specifically for huge builds
A lot of times conda build seems to solve the same thing over and over. Also it often says „fetching repodata“ - I’m not sure what triggers this under the hood
Matthew R Becker
@beckermr
Mamba is so fast that I’m not actually worried about these things.
Wolf Vollprecht
@wolfv
one thing that I believe is possible -- at least for these ROS builds -- is that one can solve over the "union" of the dependencies of the different recipes
e.g. if i have ros-pkg1 and ros-pkg2 and both depend on Python in the host section, then Python should be exactly the same in both cases
so if one first removes all packages that are part of the build from the dependencies, and then creates one big (fake) host section, then solves, then one should have the correct deps for all packages
this would cut the build time for our ROS meta.yamls by an hour easily :) so I really need to get to that
Matthew R Becker
@beckermr
interesting
at some point conda build was caching envs iiuic but this led to issues
Wolf Vollprecht
@wolfv
@kalefranz I have compiled a short list of low-level things that I think could be improvements to conda: https://docs.google.com/document/d/1nNvHbCmvK9lNzRd28Ki3rFHSEiXzPaR7vP6830tbXlA/edit?usp=sharing
I think gradually we'll try to tackle them in mamba
maybe you guys want to chime in?
Pat Gunn
@pgunn
Is there a way to tell what packages are in a conda environment without running any conda commands?
Wolf Vollprecht
@wolfv
conda list?
or check te files in conda-meta
Pat Gunn
@pgunn
without running any conda commands :)
I work in academia and we're trying to figure out a backup policy that lets us skip backing up conda while still preserving the info needed for users to recreate their environment if need be. We don't want our backup scripts to su to the user to run conda stuff.
wes
@wscarter
@pgunn there might be a better option but there is a list of package jsons in $HOME/.miniconda3/envs/<my_env>/conda-meta
that's assuming miniconda but i guess it's probably similar for other install methods
you could write a shell script to parse the package name out of the filename
Jonathan J. Helmus
@jjhelmus
The conda-meta directory exists for every conda environment
Pat Gunn
@pgunn
that'll do
Christian Roth
@croth1
When I do conda create -n testfoo -c bioconda --override-channels scanpy --dry-run (which is not solvable), I do not get any Information apart from: UnsatisfiableError: - is that a regression?
Jonathan J. Helmus
@jjhelmus
Perhape
Note that --override-channels means that no additional channels are searched for dependencies. Since bioconda does not provide many of the core packages, e.g. python, matplotlib no solution can be found.
Christian Roth
@croth1
The solver error was expected, I just expected it to give me the same results as if I had removed the conda-forge channel from my .condarc and was a bit surprised.
Jonathan J. Helmus
@jjhelmus
Yes, older versions of conda gave more information, feel free to open an issue
Antoine Prouvost
@AntoinePrv

Hello,

Is the information in Compiler tools / Aside CMake SysRoot still relevant for recent version of CMake/conda?
I see the CMake issue refered to is still open, but I can build a conda package with CMake without cross-linux.cmake toolchain file without issues (except for $AR not being properly detected). Will it break once in someonelse's computer?

Sorry if this can be answered with the current doc. I'm quite new to CMake and conda-build, and this is a lot of information at once.

Wolf Vollprecht
@wolfv
I tried to sign up for a paid account on Anaconda.org and I get an email that tells me that my email isn't associated with an Enterprise account
Dave Hirschfeld
@dhirschfeld
Catch-22!
rachmaninovquartet
@rachmaninovquartet
We made the switch today from the old repo.continuum as it was giving us 404s to https://repo.anaconda.com/pkgs
there is some strange intermittent issue yielding this:
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to repo.anaconda.com:443
it happens maybe 20% of the time when cURLing to test
downloading a package
the network admins are suspicious it is something to do with cloudflare
we are sending our CLIENT_HELLO - OUT but do not get a SERVER_HELLO back IN
Wolf Vollprecht
@wolfv
just wondering, i made my own channel on anaconda.org, but it doesn't have SHA256 data in the repodata? https://conda.anaconda.org/robostack/linux-64/repodata.json
is that expected or am I doing something wrong?