Skip to content

Conversation

@tjwilli58
Copy link
Contributor

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.

Created from PR conda-forge/gstreamer-feedstock#170

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Nov 12, 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/gst-rstp-server/meta.yaml) and found some lint.

Here's what I've got...

For recipes/gst-rstp-server/meta.yaml:

  • ❌ The home item is expected in the about section.
  • ❌ The license item is expected in the about section.
  • ❌ The summary item is expected in the about section.

For recipes/gst-rstp-server/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

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

@github-actions
Copy link
Contributor

github-actions bot commented Nov 12, 2025

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

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

  • LICENSE.txt:
    • lints:
      • Do not edit files outside of the recipes/ directory.

@tjwilli58 tjwilli58 marked this pull request as draft November 12, 2025 14:33
@github-actions
Copy link
Contributor

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

@tjwilli58 tjwilli58 marked this pull request as ready for review November 12, 2025 15:07
@github-actions
Copy link
Contributor

github-actions bot commented Nov 12, 2025

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

File-specific lints and/or hints:

  • recipes/gst-rstp-server/meta.yaml:
    • lints:
      • The following maintainers have not yet confirmed that they are willing to be listed here: hmaarrfk, yishai1999. Please ask them to comment on this PR if they are.

@tjwilli58 tjwilli58 closed this Nov 12, 2025
@tjwilli58 tjwilli58 deleted the gst-rstp-server branch November 12, 2025 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gstreamer Plugins RTSP Server & V4L2 source

2 participants