by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 16:52
    cjw296 commented #10136
  • 16:13
    chenghlee commented #10136
  • 16:09
    chenghlee labeled #10136
  • 16:09
    chenghlee labeled #10136
  • 16:09
    nickhir opened #10142
  • 14:22
    tottokuschel commented #10130
  • 14:00
    gerileka commented #9746
  • 13:37
    chenghlee commented #10141
  • 06:38
    yezhengli-Mr9 commented #9794
  • 03:39
    xingxinggui opened #10141
  • 02:39
    KrishJee commented #9746
  • Aug 09 19:20
    Anken-Aoudia commented #10140
  • Aug 09 19:16
    Anken-Aoudia commented #10140
  • Aug 09 19:15
    Anken-Aoudia commented #10140
  • Aug 09 19:14
    Anken-Aoudia commented #10140
  • Aug 09 19:13
    Anken-Aoudia commented #10140
  • Aug 09 16:27
    mingwandroid closed #10140
  • Aug 09 16:27
    mingwandroid commented #10140
  • Aug 09 16:03
    ankush2kn commented #9867
  • Aug 09 08:54
    aoudias opened #10140
Alex
@droctothorpe
Hey all, I'm trying to configure a multi-user conda environment. I have a docker container that installs conda as the root user for a Jupyter notebook. At runtime, new Linux users are dynamically added. I want those users to be able to add packages to the environment, but they don't have write permissions. I've been trying to take a group-based approach, but if I chown at 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.
Wolf Vollprecht
@wolfv
not sure if this can help you
Alex
@droctothorpe
Thanks, Wolf. Def a start.
Jonathan J. Helmus
@jjhelmus
@wolfv sha256 data is only provided for channels like conda-forge that are served from a CDN. Other channels will only have md5 hash information.
Philippe Blain
@phil-blain

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..

Philippe Blain
@phil-blain

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...

Steven C. Howell
@StevenCHowell
I'm experiencing an issue where my Jupyter instance cannot activate kernels other than the one Jupyter is actually installed in. I get the error, "'activate' is not recognized as an internal or external command, operable program or batch file."
I think this is caused because the conda bin command is not actually on the path. I am on Windows 10, with the user-only install of Miniconda.
Should I file an issue or is there a simple way to correct this?
Anthony Scopatz
@scopatz
Is there a way to get conda to spit out the files that is actually installs, rather than what is in the info/files of the tarball
Wolf Vollprecht
@wolfv
I don't know, but the only special case is with noarch packages I believe
and with them, it depends on your Python version what files get installed
e.g. `pycache/....py38.pyc or something like that
Anthony Scopatz
@scopatz
Yeah, I think noarch is the only special case too, but there is also noarch generic, etc
Jonathan J. Helmus
@jjhelmus
Post install the list of installed files is pkg_name.json file in the conda-meta folder of the environment in the "files" key. That will include .pyc files generated for noarch: python packages. Other packages, include noarch: generic will match the file list given in info/files or info/paths.json.
Conda will display the actions that is performs in the log if you run the command with -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: generic has no special cases around files. The files in the package and linked/copied into the environment in the same manner as noarch: false packages. What makes them "special" is that they are not restricted to a particular platform.
Anthony Scopatz
@scopatz
Ahh that's cool @jjhelmus! Thanks I didn't know about pkg_name.json
Christopher Barber
@analog-cbarber
How do you build the new version 2 .conda packages? I don't see any obvious flags in the conda-build or meta.yaml documentation.
Jonathan J. Helmus
@jjhelmus
.conda packages can be created by transmuting .tar.bz2 packages with conda-package-handling
For example cph t ca-certificates-2019.5.15-1.tar.bz2 .conda
Christopher Barber
@analog-cbarber
Ok. It seems strange that you have to build a bz2 first. Is there eventually going to be a way to build them directly?
Wolf Vollprecht
@wolfv
I figured out that I can use the anaconda API to check the latest version of a given package (using latest as the version identifier)
is there also a way to get the latest version for a specific platform?
and more interestingly could I get the direct download link for the latest version for a specific platform? :)
Amir Mohammadi
@183amir
Hi guys, I was wondering to build osx-64 packages that are ABI compatible with the defaults channel, what build criteria are needed? In particular, I noticed that the defaults channel now uses clang 7 and macos 10.10 as the minimum supported version as specified in https://github.com/AnacondaRecipes/aggregate/blob/master/conda_build_config.yaml, but, in that file, some variables still point to 10.9 like https://github.com/AnacondaRecipes/aggregate/blob/master/conda_build_config.yaml#L139 is this an oversight or this is how this is supposed to be?
Sylvain Corlay
@SylvainCorlay
Hey, is it expected that conda update conda upgrades python from e.g. 3.6 to 3.8?
Jonathan J. Helmus
@jjhelmus
Recent conda version will not update the Python minor version unless explicitly specified
Jonathan J. Helmus
@jjhelmus
The code responsible for this is in core/solve.py, https://github.com/conda/conda/blob/4.8.3/conda/core/solve.py#L671-L697
mattchan-tencent
@mattchan-tencent
Is there a way to rebuild an existing conda package? The existing one links to a version of glibc that is too new for my system
Jonathan J. Helmus
@jjhelmus
In most cases the recipe used to build a conda package is included in tarball in the "info/recipe" directory. You can use conda-build to rebuild the package from that recipe.
mattchan-tencent
@mattchan-tencent
Hmm okay. So no automated way to do it
The source is not included in the info/recipe directory though right?
So if it's not pulling from a public git repo or something it won't rebuild?
Jonathan J. Helmus
@jjhelmus
There is not an automated method for rebuilding the package from the recipe inside the package. Typically the source is defined in a "source" section in the meta.yaml.template or meta.yaml file.
mattchan-tencent
@mattchan-tencent
Yep. Okay I'll peek at the tarball. Thanks for your help!
Sylvain Corlay
@SylvainCorlay

Recent conda version will not update the Python minor version unless explicitly specified

Thanks for the reply. Will check versions and report in the issue tracker if it is not the expected behavior for that version.

Piotr Zierhoffer
@pzierhoffer_gitlab
Hi. I'm not sure if this is the right channel to ask about anaconda, but I'm trying to use the CLI to get information about files in a particular label. While I can call anaconda show user/package and anaconda show user/package/version, I cant find anything about listing packages with a given label. Especially with a parsable output
Andrew Achkar
@hajapy
Is anyone able to respond to conda/conda#10053
dboeckenhoff
@dboeckenhoff
Hi. I am having problems with virtualenv called by pre-commit:

(py38) 20:14 dboe@fc-ubu1-005 ~/git/rna git commit -am "moving now everything to setup.cfg"
[INFO] Installing environment for https://gitlab.com/dboe/dough/.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: command: ('/opt/anaconda/bin/python', '-mvirtualenv', '/home/IPP-HGW/dboe/.cache/pre-commit/repohm1rb_i9/py_env-default', '-p', '/opt/anaconda/bin/python3.7')
return code: 1
expected return code: 0
stdout:
ImportError: cannot import name 'DETACHED_PROCESS' from 'virtualenv.util.subprocess' (/opt/anaconda/lib/python3.7/site-packages/virtualenv/util/subprocess/init.py)

stderr: (none)
Check the log at /home/IPP-HGW/dboe/.cache/pre-commit/pre-commit.log

Strange thing: It works on my laptop, so I thought conda was corrupted somehow. I reset the whole conda env to revision 0 but it keeps occuring.
The Traceback in the pre-commit.log is
Traceback (most recent call last):
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/error_handler.py", line 56, in error_handler
yield
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/main.py", line 372, in main
args=args.rest[1:],
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/commands/hook_impl.py", line 217, in hook_impl
return retv | run(config, store, ns)
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/commands/run.py", line 380, in run
install_hook_envs(hooks, store)
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/repository.py", line 200, in install_hook_envs
_hook_install(hook)
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/repository.py", line 83, in _hook_install
hook.prefix, hook.language_version, hook.additional_dependencies,
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/languages/python.py", line 212, in install_environment
cmd_output_b(*venv_cmd, cwd='/')
File "/opt/anaconda/lib/python3.7/site-packages/pre_commit/util.py", line 157, in cmd_output_b
raise CalledProcessError(returncode, cmd, retcode, stdout_b, stderr_b)
pre_commit.util.CalledProcessError: command: ('/opt/anaconda/bin/python', '-mvirtualenv', '/home/IPP-HGW/dboe/.cache/pre-commit/repohm1rb_i9/py_env-python3.7', '-p', '/opt/anaconda/bin/python')
Any idea? sorry for the long post.
Marcelo Duarte Trevisani
@marcelotrevisani
can you send the pre-commit log?
/home/IPP-HGW/dboe/.cache/pre-commit/pre-commit.log
dboeckenhoff
@dboeckenhoff