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 intervalues #29110

Merged
merged 18 commits into from
Feb 14, 2025
Merged

Add intervalues #29110

merged 18 commits into from
Feb 14, 2025

Conversation

apcamargo
Copy link
Contributor

@apcamargo apcamargo commented Feb 12, 2025

This PR adds intervalues, by @debruijn.

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

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

@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/intervalues/meta.yaml) and found it was in an excellent condition.

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

For recipes/intervalues/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/13293232867. 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 wanted to let you know that I linted all conda-recipes in your PR (recipes/intervalues/meta.yaml) and found some lint.

Here's what I've got...

For recipes/intervalues/meta.yaml:

For recipes/intervalues/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/13293389182. Examine the logs at this URL for more detail.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 12, 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/intervalues/meta.yaml) and found it was in an excellent condition.

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

For recipes/intervalues/meta.yaml:

  • ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
    • 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/13295504901. 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 wanted to let you know that I linted all conda-recipes in your PR (recipes/intervalues/meta.yaml) and found some lint.

Here's what I've got...

For recipes/intervalues/meta.yaml:

  • ❌ Non noarch packages should have python requirement without any version constraints.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13296581188. 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/intervalues/meta.yaml) and found it was in an excellent condition.

@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/intervalues/meta.yaml) and found some lint.

Here's what I've got...

For recipes/intervalues/meta.yaml:

  • ❌ Non noarch packages should have python requirement without any version constraints.
  • ❌ Non noarch packages should have python requirement without any version constraints.

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

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 13, 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/intervalues/meta.yaml) and found it was in an excellent condition.

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

For recipes/intervalues/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 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/13320107750. Examine the logs at this URL for more detail.

@apcamargo
Copy link
Contributor Author

@conda-forge/help-python The Linux test is failing because of a OverLinkingError. Any idea what could be happening here?

Packaging intervalues
Packaging intervalues-0.3.0-py312he4ac13c_0
compiling .pyc files...
number of files: 29
Warning: rpath /home/conda/staged-recipes/build_artifacts/intervalues_1739401996777/_build_env/lib is outside prefix /home/conda/staged-recipes/build_artifacts/intervalues_1739401996777/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold (removing it)
   INFO: sysroot: '/home/conda/staged-recipes/build_artifacts/intervalues_1739401996777/_build_env/x86_64-conda-linux-gnu/sysroot/' files: '['usr/share/zoneinfo', 'usr/share/locale/zh_TW/LC_MESSAGES/libc.mo', 'usr/share/locale/zh_CN/LC_MESSAGES/libc.mo', 'usr/share/locale/vi/LC_MESSAGES/libc.mo']'
  ERROR (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO lib/libgcc_s.so.1 found in ['conda-forge/linux-64::libgcc==14.2.0=h77fa898_1']
  ERROR (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): .. but ['conda-forge/linux-64::libgcc==14.2.0=h77fa898_1'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)
   INFO (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO x86_64-conda-linux-gnu/sysroot/lib64/librt.so.1 found in CDT/compiler package conda-forge/noarch::sysroot_linux-64==2.17=h0157908_18
   INFO (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO x86_64-conda-linux-gnu/sysroot/lib64/libpthread.so.0 found in CDT/compiler package conda-forge/noarch::sysroot_linux-64==2.17=h0157908_18
   INFO (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO x86_64-conda-linux-gnu/sysroot/lib64/libm.so.6 found in CDT/compiler package conda-forge/noarch::sysroot_linux-64==2.17=h0157908_18
   INFO (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO x86_64-conda-linux-gnu/sysroot/lib64/libdl.so.2 found in CDT/compiler package conda-forge/noarch::sysroot_linux-64==2.17=h0157908_18
   INFO (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO x86_64-conda-linux-gnu/sysroot/lib64/libc.so.6 found in CDT/compiler package conda-forge/noarch::sysroot_linux-64==2.17=h0157908_18
   INFO (intervalues,lib/python3.12/site-packages/intervalues_pyrust.cpython-312-x86_64-linux-gnu.so): Needed DSO x86_64-conda-linux-gnu/sysroot/lib64/ld-linux-x86-64.so.2 found in CDT/compiler package conda-forge/noarch::sysroot_linux-64==2.17=h0157908_18
WARNING (intervalues): interpreter (Python) package conda-forge/linux-64::python==3.12.8=h9e4cc4f_1_cpython in requirements/run but it is not used (i.e. it is overdepending or perhaps statically linked? If that is what you want then add it to `build/ignore_run_exports`)
Traceback (most recent call last):
  File "/home/conda/staged-recipes-copy/.ci_support/build_all.py", line 356, in <module>
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/lib/python3.12/site-packages/conda_build/post.py", line 1566, in check_overlinking_impl
    raise OverLinkingError(overlinking_errors)
conda_build.exceptions.OverLinkingError: <exception str() failed>

@ocefpaf
Copy link
Member

ocefpaf commented Feb 13, 2025

You may have thirdpaty license in the rust package. Can you use cargo bundle license here? See https://github.com/conda-forge/staged-recipes/pull/28803/files for an example.

@apcamargo
Copy link
Contributor Author

apcamargo commented Feb 13, 2025

Done, @ocefpaf

The OverLinkingError persists, tough. I couldn't find anything about it in the documentation.

Update: Adding libgcc as a runtime requirement in Linux fixed the issue.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 14, 2025

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/intervalues/meta.yaml) and found some lint.

Here's what I've got...

For recipes/intervalues/meta.yaml:

  • ❌ Non noarch packages should have python requirement without any version constraints.
  • ❌ Non noarch packages should have python requirement without any version constraints.

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

@apcamargo
Copy link
Contributor Author

@conda-forge/help-python, ready for review. The builds and tests seem to be all fine.

The linter is complaining that non-noarch recipes should not have version constraints for Python. However, this library has set the minimum version to 3.10 in the source code and the CI fails when it tries to build for Python 3.9. Not sure what is the proper thing to do in a case like this.

@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/intervalues/meta.yaml) and found it was in an excellent condition.

@apcamargo
Copy link
Contributor Author

Thanks, @ocefpaf!

@ocefpaf ocefpaf merged commit ce15ee0 into conda-forge:main Feb 14, 2025
7 checks passed
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.

3 participants