qt5

[looooo]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

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

Here's what I've got...

For recipe/meta.yaml:

• ❌ The recipe must have some tests.
• ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [57]
• ❌ There are too few lines. There should be one empty line at the end of the file.

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

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

[looooo]

@adrianinsaval do you know which versions we should build the qt5-branch against? occt? vtk? boost?