Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conda-build should check if runtime dependencies are valid matchspecs #5047

Closed
jaimergp opened this issue Oct 30, 2023 · 0 comments · Fixed by #5359
Closed

conda-build should check if runtime dependencies are valid matchspecs #5047

jaimergp opened this issue Oct 30, 2023 · 0 comments · Fixed by #5359
Labels
source::contributor created by a frequent contributor type::feature request for a new feature or capability

Comments

@jaimergp
Copy link
Contributor

jaimergp commented Oct 30, 2023

What happened?

It doesn't seem like conda-build ensures that run and run_constrained dependencies are valid MatchSpec objects. Otherwise, I don't know how to explain this issue, where a package had wrongly specified the following run_constrained item:

 - cloudpickle >=2.2.1<2.3.0 

Which results in the following error when conda classic tries to install it:

InvalidVersionSpec: Invalid version '2.2.1<2.3.0': invalid character(s)

I'd say conda-build should try to convert all those items to a MatchSpec before reporting the package as successfully built.

Conda Details

conda info
active environment : conda-dev
    active env location : /Users/jrodriguez/.local/anaconda/envs/conda-dev
            shell level : 2
       user config file : /Users/jrodriguez/.condarc
 populated config files : /Users/jrodriguez/.local/anaconda/.condarc
                          /Users/jrodriguez/.condarc
          conda version : 23.9.0
    conda-build version : 3.26.1
         python version : 3.9.9.final.0
       virtual packages : __archspec=1=m1
                          __osx=13.5.2=0
                          __unix=0=0
       base environment : /Users/jrodriguez/.local/anaconda  (writable)
      conda av data dir : /Users/jrodriguez/.local/anaconda/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-arm64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/jrodriguez/.local/anaconda/pkgs
                          /Users/jrodriguez/.conda/pkgs
       envs directories : /Users/jrodriguez/.local/anaconda/envs
                          /Users/jrodriguez/.conda/envs
               platform : osx-arm64
             user-agent : conda/23.9.0 requests/2.31.0 CPython/3.9.9 Darwin/22.6.0 OSX/13.5.2 solver/libmamba conda-libmamba-solver/23.9.1 libmambapy/1.5.1
                UID:GID : 501:20
             netrc file : None
           offline mode : False
conda config
==> /Users/jrodriguez/.local/anaconda/.condarc <==
channels:
  - conda-forge

==> /Users/jrodriguez/.condarc <==
add_pip_as_python_dependency: False
auto_update_conda: False
local_repodata_ttl: 0
channel_priority: strict
channels:
  - conda-forge
show_channel_urls: True
report_errors: False
experimental:
  - jlap
solver: libmamba
@jaimergp jaimergp added the type::bug describes erroneous operation, use severity::* to classify the type label Oct 30, 2023
@travishathaway travishathaway added the source::contributor created by a frequent contributor label Nov 6, 2023
@kenodegard kenodegard added type::feature request for a new feature or capability and removed type::bug describes erroneous operation, use severity::* to classify the type labels Nov 6, 2023
@jaimergp jaimergp linked a pull request May 24, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
source::contributor created by a frequent contributor type::feature request for a new feature or capability
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants