CRbeam program

[okolo]

No description provided.

[conda-forge-webservices]

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

Here's what I've got...

For recipes/crbeam/meta.yaml:

• requirements: build: gsl==2.6 must contain a space between the name and the pin, i.e. gsl ==2.6
• requirements: build: boost==1.82.0 must contain a space between the name and the pin, i.e. boost ==1.82.0
• requirements: host: gsl==2.6 must contain a space between the name and the pin, i.e. gsl ==2.6
• requirements: host: boost==1.82.0 must contain a space between the name and the pin, i.e. boost ==1.82.0
• requirements: run: gsl==2.6 must contain a space between the name and the pin, i.e. gsl ==2.6
• requirements: run: boost==1.82.0 must contain a space between the name and the pin, i.e. boost ==1.82.0
• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-webservices]

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

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

For recipes/crbeam/meta.yaml:

• The boost output has been superseded by libboost-python-devel (as of 1.82), which now comes with a run-export (on libboost-python) as well.

[conda-forge-webservices]

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

Here's what I've got...

For recipes/crbeam/meta.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

For recipes/crbeam/meta.yaml:

• The boost output has been superseded by libboost-python-devel (as of 1.82), which now comes with a run-export (on libboost-python) as well.

[conda-forge-webservices]

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

Here's what I've got...

For recipes/crbeam/meta.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-webservices]

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

[volodymyrss]

Maybe we should ask conda-forge maintainers to understand why the build is different from that in local environment.

Also need we need to figure out licensed code in the package.

[github-actions]

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

I Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge/staged-recipes/actions/runs/11107381737.}

[github-actions]

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

[conda-forge-admin]

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

I Failed to even lint the recipe, probably because of a conda-smithy
bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge-webservices/actions/runs/11143432183.}

[beckermr]

@conda-forge-admin relint

[conda-forge-admin]

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/crbeam/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipes/crbeam/meta.yaml:

• You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

[conda-forge-admin]

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

[conda-forge-admin]

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/crbeam/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipes/crbeam/meta.yaml:

• You should not need to depend on libboost directly. If your package is linking to boost libraries, use libboost-devel in the host environment (which will create the correct dependence at runtime through a run-export), or use libboost-headers if you only need the boost headers.

[conda-forge-admin]

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

[okolo]

@xhochy I think the recipe is ready for merge. I have addressed all your suggestions.

[okolo]

@conda-forge/help-c-cpp ready for review

[okolo]

Please loosen/remove all/most of the pins. Otherwise this package will be incompatible with the rest of the ecosystem.

done

[volodymyrss]

@bgruening FYI, this is need for our ESG work.

[bgruening]

@okolo this looks pretty good! Well done. There is one co fusion about the version. Can you maybe release a.proper 1.1.1 version?

[bgruening]

Merci!