Add net-snmp

[simon-ess]

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.

[conda-forge-admin]

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/net-snmp-feedstock/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/net-snmp-feedstock/recipe.yaml:

• ❌ The license item is expected in the about section.
• ❌ The recipe must have some tests.
• ❌ There are too few lines. There should be one empty line at the end of the file.

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

[github-actions]

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

[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/net-snmp-feedstock/recipe.yaml) and found it was in an excellent condition.

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

For recipes/net-snmp-feedstock/recipe.yaml:

• ℹ️ License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

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

[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/net-snmp-feedstock/recipe.yaml) and found it was in an excellent condition.

[simon-ess]

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

[simon-ess]

@conda-forge/staged-recipes @conda-forge/help-c-cpp, ready for review!

[github-actions]

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!

[traversaro]

It seems that the CI is failing, is this expected?

[simon-ess]

I have been meaning to get back to this :/

The CI tests are failing, but it isn't clear to me exactly why. The test pass locally so...

[traversaro]

The test pass locally so...

Did you tried with the build-locally.py python script?

I have been meaning to get back to this :/

When this is ready, feel free to ping the help team again, so the label review-requested is added again.

[simon-ess]

@conda-forge/staged-recipes @conda-forge/help-c-cpp, ready for review again.

Note that I have removed the make test stage in the build script. This is for two reasons:

• The tests pass locally but I am not able to make them pass in the github pipelines
• This isn't really even the correct location to be performing tests; it would presumably be better to set up a separate test stage, which would take a bit more work given how the build configuration is currently set up, and feels like an inappropriate blocker to getting this released. Some issues have been created on the upstream repository, at least in regards to tests failing in newer versions.

Given that the tests did not appear to be a hard requirement for a pass, I would like to request a revew of this recipe as it stands.

[github-actions]

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!

[conda-forge-admin]

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/net-snmp/recipe.yaml) and found some lint.

Here's what I've got...

For recipes/net-snmp/recipe.yaml:

• ❌ pin_compatible should be used instead of pin_subpackage for ${{ because it is not a known output of this recipe: ['net-snmp'].

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

[danielnachun]

Suggested change

- osx

Why is macOS being skipped? If it's failing please enable it so we can see what is wrong and potentially fix it.

[simon-ess]

Unfortunately it is failing, and the build doesn't seem to want to run locally either, but for different reasons. I'd rather remove it for now and fix it later.

[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/net-snmp/recipe.yaml) and found it was in an excellent condition.

[anderslindho]

@danielnachun @traversaro could you please check in again on this PR? We are waiting for the completion of this; we have downstream things that need it.