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.
chownat the end of the Dockerfile, it adds approximately ten minutes to my build time. I'd like to preconfigure the ownership so that I can add/remove packages in the Dockerfile without having to chown at the end of the process. Is there an idiomatic way to handle this kind of problem? I've been referencing https://medium.com/@pjptech/installing-anaconda-for-multiple-users-650b2a6666c6 so far.
hi everyone ! I just clone the conda repo on my macOS 10.11 system and did
source dev/start. I get conflicts:
Solving environment: ...working... Found conflicts! Looking for incompatible packages. This can take several minutes. Press CTRL-C to abort. failed UnsatisfiableError: The following specifications were found to be incompatible with a past explicit spec that is not an explicit spec in this operation (conda): - conda-build -> conda[version='>=4.1,<4.3|>=4.1|>=4.1,<4.4|>=4.3|>=4.5'] The following specifications were found to be incompatible with each other: # and then pages after pages of conflicts...
I'm not sure what to do about that..
it appears my
~/.condarc file, with the following content, created that situation:
auto_activate_base: false changeps1: false channels: - conda-forge - defaults channel_priority: strict anaconda_upload: false
the super long list of conflicts ended with "Note that strict channel priority may have removed packages required for satisfiability.", which made me think of trying again after moving my
~/.condarc out of the way...
noarch: pythonpackages. Other packages, include
noarch: genericwill match the file list given in info/files or info/paths.json.
-vvv. Look for lines like:
TRACE conda.core.path_actions:execute(374): linking /home/jhelmus/conda/pkgs/imagesize-1.2.0-py_0/site-packages/imagesize-1.2.0.dist-info/RECORD => /home/jhelmus/conda/envs/test/lib/python3.8/site-packages/imagesize-1.2.0.dist-info/RECORD
noarch: generichas no special cases around files. The files in the package and linked/copied into the environment in the same manner as
noarch: falsepackages. What makes them "special" is that they are not restricted to a particular platform.
cph t ca-certificates-2019.5.15-1.tar.bz2 .conda