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

Remove caps for mamba & conda-build #74

Merged
merged 5 commits into from
Sep 6, 2023
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions .azure-pipelines/azure-pipelines-linux.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions recipe/meta.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ source:

build:
script: {{ PYTHON }} -m pip install . --no-deps -vv
number: 0
number: 1
noarch: python
entry_points:
- conda-mambabuild = boa.cli.mambabuild:main
Expand All @@ -24,7 +24,7 @@ requirements:
run:
- python >=3.6
- conda-build >=3.24,<3.26
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- conda-build >=3.24,<3.26
- conda-build >=3.24

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why unpin conda-build? This change is one of the causes for mamba-org/boa#388.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because that was a long-running effort to unblock many other things that required newer conda-build. The previous cap was there due to explicit incompatibilities, which were removed, hence the cap could be removed.

Now a new incompatibility got introduced with 3.28. It's a separate topic. The only take-away perhaps is to be more defensive on the pins here, and use <={last_working_conda_build}. In an ideal world that shouldn't be necessary (conda-build should deprecate behaviour changes, rather than just break things), but well...

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, thanks for clarifying.

Lately my practice has been to pin on major versions (i.e. conda-build >=3.24,<4) as those are likely to come with breaking changes. However, as we see in this case, there's still the possibility of breaking changes coming in minor version updates, which is unfortunate...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not everyone does versioning according to the server spec...

- mamba >=1.0,<=1.4.2
- mamba >=1.4.5,<=1.4.9
rohan-shah-nearmap marked this conversation as resolved.
Show resolved Hide resolved
- ruamel.yaml
- jinja2
- rich
Expand Down