rerender with new GL dependency management #50
Conversation
conda-forge-admin
requested review from
adam-urbanczyk and
whophil
as code owners
|
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 ( |
…nda-forge-pinning 2024.08.27.19.11.25
hmaarrfk
force-pushed
the
conda_forge_admin_49
branch
from
fd1eca5
to
0925774
Compare
…nda-forge-pinning 2024.08.27.19.11.25
…nda-forge-pinning 2024.08.27.19.11.25
| - {{ pin_compatible('occt', exact=True) }} | ||
| - {{ pin_compatible('vtk', max_pin='x.x') }} | ||
| - {{ pin_compatible('occt', max_pin='x.x.x') }} |
There was a problem hiding this comment.
Pinning occt to exact will give you trouble when a new build number of occt comes out, our infrastructure won't retrigger your build.
Let vtk manage its own pinning with run exports.
There was a problem hiding this comment.
ocp is a bindings project for occt. The bindings code is typically tied to an exact version of occt, so we have to wait for the bindings to be (semi-manually) generated before we can release a new ocp conda package.
Would you still recommend against an exact pin in this case?
|
@conda-forge-admin please rerender |
…nda-forge-pinning 2024.08.28.05.05.18
|
i'm not sure if it makes a difference but one found vtk - osmeta, the other found vtk - qt. vtk - qt failed. |
Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #49.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.