Skip to content

MatchSpec.conda_build_form() expects version to be set #11200

@jaimergp

Description

@jaimergp

Acceptance Criteria

Checklist

  • I added a descriptive title
  • I searched for other issues and couldn't find a solution or duplication
  • I already searched in Google and didn't find any good information or help
  • I looked at the docs and didn't see anything to help

What happened?

The compatibility layer between conda-build and conda has some rough edges here and there. Here you can see one more.

conda_build_form() expects the version field to be populated, otherwise it fails with an AssertionError. However, it could default to * instead of erroring out.

Conda info

active environment : base
    active env location : /opt/conda
            shell level : 1
       user config file : /home/test_user/.condarc
 populated config files : 
          conda version : 4.11.0.post55+0c7211356
    conda-build version : 3.21.7
         python version : 3.7.11.final.0
       virtual packages : __linux=5.11.0=0
                          __glibc=2.28=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /opt/conda  (read only)
      conda av data dir : /opt/conda/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /opt/conda/pkgs
                          /home/test_user/.conda/pkgs
       envs directories : /home/test_user/.conda/envs
                          /opt/conda/envs
               platform : linux-64
             user-agent : conda/4.11.0.post55+0c7211356 requests/2.27.1 CPython/3.7.11 Linux/5.11.0-1028-azure debian/10 glibc/2.28
                UID:GID : 1001:1001
             netrc file : None
           offline mode : False

Conda config

Same as CI for Docker image

Conda list

Same as CI for Docker image

Additional Context

This is an error we are seeing while running the solver tests for libmamba. We are patching the tests instead, but I think it would be cleaner to fix this "bug".

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogissue has been triaged but has not been earmarked for any upcoming releaseseverity::4low; functionality is inconvenientsource::partnercreated by or for an Anaconda, Inc. partner companystale::recovered[bot] recovered after being marked as staletype::bugdescribes erroneous operation, use severity::* to classify the type

    Type

    No type

    Projects

    Status

    🏁 Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions