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 reprostim #29029

Merged
merged 26 commits into from
Feb 11, 2025
Merged

Add reprostim #29029

merged 26 commits into from
Feb 11, 2025

Conversation

vmdocua
Copy link
Contributor

@vmdocua vmdocua commented Feb 4, 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 4, 2025

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

File-specific lints and/or hints:

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

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

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

For recipes/reprostim/meta.yaml:

  • ℹ️ Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

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

@vmdocua vmdocua changed the title Adding reprostim Add recipe for reprostim Feb 4, 2025
@vmdocua vmdocua changed the title Add recipe for reprostim Add reprostim Feb 5, 2025
@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/reprostim/meta.yaml) and found it was in an excellent condition.


extra:
recipe-maintainers:
- yarikoptic
Copy link
Contributor

Choose a reason for hiding this comment

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

I confirm to agree to co-maintain this recipe!

Copy link
Contributor

github-actions bot commented Feb 7, 2025

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

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 7, 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/reprostim/meta.yaml) and found some lint.

Here's what I've got...

For recipes/reprostim/meta.yaml:

  • ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [37, 39]
  • ❌ 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/13205273913. 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/reprostim/meta.yaml) and found it was in an excellent condition.

@vmdocua vmdocua marked this pull request as ready for review February 8, 2025 08:19
@yarikoptic
Copy link
Contributor

@conda-forge/staged-recipes I think this recipe is ready happen someone has cycles to review/feedback/merge.

Cheers

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!

@yarikoptic
Copy link
Contributor

@conda-forge/help-python I think this recipe is ready happen someone has cycles to review/feedback/merge.

sha256: f735714a725998816617df9ab84c9e0f79e6749544b0ab1d27d0fd0c5672d6c2

build:
skip: True # [win]
Copy link
Member

Choose a reason for hiding this comment

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

Looks like this one could be noarch.

It is OK for noarch package to fails on Windows with a missing dependency. We prefer noarch b/c it is faster to build and the package will be ready when the missing dependency is available on Windows.

sha256: f735714a725998816617df9ab84c9e0f79e6749544b0ab1d27d0fd0c5672d6c2

build:
skip: True # [win]
Copy link
Member

Choose a reason for hiding this comment

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

It seems like this should be noarch: python. I can see you were having issues with dependency availability on windows, but typically we ignore those since that's an ecosystem issue rather than an issue with this package.

Copy link
Member

Choose a reason for hiding this comment

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

That is to say, if all of the CI is passing except windows and the windows issue is just that a dependency isn't available, then we will merge it if it's a noarch: python package.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, switched to noarch.

- numpy >=1.26.4
- qrcode >=8.0
- opencv >=4.9.0
- zbar # [not win]
Copy link
Member

Choose a reason for hiding this comment

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

This is not a direct dependency and should be pulled in by pyzbar

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, zbar removed + pyzbar downgraded to v.0.1.8, as the latest version try to install zbar DLL and package which physically not exists at all for Windows (as was reprorted by maintainers). Interesting enough how conda-forge pyzbar v0.1.9 updated recipe and passed check in conda like this windows build w/o zbar, but this is probably another story..

This change was not enough to fix build, as looks like under Windows-based python we need to explicitly specify entry point, as otherwise it fails in contrast to Linux/macOS.


test:
imports:
- reprostim # [not win]
Copy link
Member

Choose a reason for hiding this comment

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

Remove win selectors.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, all selectors were removed.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Feb 10, 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/reprostim/meta.yaml) and found some lint.

Here's what I've got...

For recipes/reprostim/meta.yaml:

  • noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

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

 The following package could not be installed

pyzbar >=0.1.9 * is not installable because it requires

zbar =* *, which does not exist (perhaps a missing channel).
…e run section of recipe, you should usually use python >={{ python_min }} for the python entry"
…Noarch package contains binary script: reprostim.exe
@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/reprostim/meta.yaml) and found it was in an excellent condition.

@vmdocua
Copy link
Contributor Author

vmdocua commented Feb 10, 2025

Just for information, on the same plate, created issue at pyzbar-feedstock #5 as well.

@synapticarbors synapticarbors merged commit bf5cfc5 into conda-forge:main Feb 11, 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.

5 participants