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

Add cerberecontrib-ghrsst recipe #29189

Merged
merged 20 commits into from
Feb 21, 2025
Merged

Add cerberecontrib-ghrsst recipe #29189

merged 20 commits into from
Feb 21, 2025

Conversation

cso2943
Copy link
Contributor

@cso2943 cso2943 commented Feb 17, 2025

Checklist

  • Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
  • License file is packaged (see here for an example).
  • Source is from official source.
  • Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
  • If static libraries are linked in, the license of the static library is packaged.
  • Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
  • Build number is 0.
  • A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
  • GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
  • When in trouble, please check our knowledge base documentation before pinging a team.

Copy link
Contributor

github-actions bot commented Feb 17, 2025

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

  • recipes/cerberecontrib_ghrsst/meta.yaml:
    • lints:
      • The following maintainers have not yet confirmed that they are willing to be listed here: marie59. Please ask them to comment on this PR if they are.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 17, 2025

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/cerberecontrib_ghrsst/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/cerberecontrib_ghrsst/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • For the host section of recipe, you should usually use python {{ python_min }} for the python entry.
    • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
    • For the test.requires section of recipe, you should usually use python {{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13393931224. Examine the logs at this URL for more detail.

@Marie59
Copy link
Contributor

Marie59 commented Feb 17, 2025

Hi ! I will look tomorrow if you need help on the checks ;)

@criou-cg
Copy link

ok

@erwanbodere
Copy link

ok

@jfpiolle
Copy link

ok

- python >=3.10.0,<3.11
- cerbere >=3.1.2

test:
Copy link
Contributor

Choose a reason for hiding this comment

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

So your test is failing.
cerberecontrib-ghrsst 0.0.0.post146767+30809b91c0 has requirement cerbere<4.0.0,>=3.1.2, but you have cerbere 0.0.0.post21+c94c7d1.
So I'd say maybe from this we need to add in the test the import of cerbere

Copy link
Contributor

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

- pip
run:
- python >=3.10.0,<3.11
- cerbere >=3.1.2
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- cerbere >=3.1.2
- cerbere >=3.1.2,4.0.0

imports:
- cerberecontrib_ghrsst
requires:
- cerbere
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- cerbere
- cerbere >=3.1.2,4.0.0

Copy link
Contributor

Choose a reason for hiding this comment

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

Okay let's put the version more strictly see if it's better

@Marie59
Copy link
Contributor

Marie59 commented Feb 18, 2025

Hi @conda-forge/help-python and @conda-forge/staged-recipes
We have one last error here and the message is a bit cryptic for us...
Do you have any suggestions ?
Thanks for the review !!

Copy link
Contributor

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

Copy link
Contributor

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

  • recipes/more_itertools/meta.yaml:
    • lints:
      • Feedstock with the same name exists in conda-forge.
    • hints:
      • A conda package with same name (more-itertools) already exists.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/more_itertools/meta.yaml, recipes/cerberecontrib_ghrsst/meta.yaml) and found some lint.

Here's what I've got...

For recipes/more_itertools/meta.yaml:

  • ❌ The recipe must have some tests.
  • ❌ Non noarch packages should have python requirement without any version constraints.
  • ❌ Non noarch packages should have python requirement without any version constraints.

For recipes/more_itertools/meta.yaml:

  • ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

For recipes/cerberecontrib_ghrsst/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • For the host section of recipe, you should usually use python {{ python_min }} for the python entry.
    • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
    • For the test.requires section of recipe, you should usually use python {{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13394217709. Examine the logs at this URL for more detail.

Copy link
Contributor

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 18, 2025

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/cerberecontrib_ghrsst/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/cerberecontrib_ghrsst/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13453437725. Examine the logs at this URL for more detail.

@Marie59
Copy link
Contributor

Marie59 commented Feb 18, 2025

@criou-cg I think it would be best to open one PR for each package

@Marie59
Copy link
Contributor

Marie59 commented Feb 18, 2025

I propose you remove the more-itertools from here and open a new one on other branch of your fork of staged-recipes

@cso2943
Copy link
Contributor Author

cso2943 commented Feb 18, 2025

@conda-forge/help-python my recipe is ready !

- poetry-dynamic-versioning >=1.0.0,<2.0.0
- pip
run:
- python {{ python_min }}
Copy link
Member

Choose a reason for hiding this comment

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

Is this py310 only? If not you need the >=.

Suggested change
- python {{ python_min }}
- python >={{ python_min }}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes it is py310 only.

@cso2943
Copy link
Contributor Author

cso2943 commented Feb 19, 2025

@conda-forge/help-python @conda-forge/staged-recipes my recipe is ready !

- pip
run:
- python {{ python_min }}
- cerbere >=3.1.2,<4.0.0
Copy link
Member

Choose a reason for hiding this comment

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

The metadata in this package should be fixed and pip-check added there as well to avoid regressions.

+ pip check
cerberecontrib-ghrsst 3.1.2 has requirement cerbere<4.0.0,>=3.1.2, but you have cerbere 0.0.0.post21+c94c7d1.

Copy link
Contributor

@Marie59 Marie59 Feb 21, 2025

Choose a reason for hiding this comment

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

@ocefpaf Is this an issue coming from the metadata within the pyproject.toml ? or somewhere else ?

Thanks a lot for the help and review !!

Copy link
Member

Choose a reason for hiding this comment

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

It depends on how the package creates the version info. Sadly the Python packaging ecosystem has way too many ways to do this. Depending on what you use we can "fake" a version and fix it later upstream, I'll check cerbere in a moment.

Copy link
Member

Choose a reason for hiding this comment

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

See https://github.com/conda-forge/cerbere-feedstock/pull/3/files#r1965168737. Once that one is merged and the new cerbere is available in the, we can restart the CIs here.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/cerberecontrib_ghrsst/meta.yaml) and found some lint.

Here's what I've got...

For recipes/cerberecontrib_ghrsst/meta.yaml:

  • ❌ There are 1 too many lines. There should be one empty line at the end of the file.

For recipes/cerberecontrib_ghrsst/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13454559391. Examine the logs at this URL for more detail.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/cerberecontrib_ghrsst/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/cerberecontrib_ghrsst/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13454985366. Examine the logs at this URL for more detail.

@cso2943
Copy link
Contributor Author

cso2943 commented Feb 21, 2025

@conda-forge/help-python @conda-forge/staged-recipes my recipe is ready !

Copy link
Contributor

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

@ocefpaf ocefpaf merged commit 8ec48f6 into conda-forge:main Feb 21, 2025
7 checks passed
@Marie59
Copy link
Contributor

Marie59 commented Feb 21, 2025

Thanks a lot @ocefpaf !!

@cso2943
Copy link
Contributor Author

cso2943 commented Feb 21, 2025

Thanks for your help @ocefpaf !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

7 participants