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 (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

ping @conda-forge/bot

wasn't sure if I was supposed to also update "version" in meta.yaml here or if that is automated somehow? I didn't look like the other open PRs modified that

The bot is currently undergoing some revisions so I'll try to put up a migrator when that is finished.

@grlee77, from the linked issue it was not clear to me whether downgrading to freetype 2.9.1 fixed the issue. Can you confirm?

I did not get a response, but can try it now locally and see if I can replicate the issue

@grlee77, from the linked issue it was not clear to me whether downgrading to freetype 2.9.1 fixed the issue. Can you confirm?

I could not reproduce the issue from conda-forge/vtk-feedstock#80. I tried creating a new virtual env with vtk 8.2 and freetype 2.10.0 . import vtk works fine and so does opening the mayavi2 application. I also tried from a linux system and didn't find problems there either

There were a handful of symbol differences reported between 2.9.1 and 2.10.0. How does one typically judge whether this is likely to be a problem? Sorry if this PR was a false alarm.

Let me know if you want me to remove the change in pinning and still bump the pinned version. Otherwise feel free to close this PR if you do not think we should change the pinning at this time.

How does one typically judge whether this is likely to be a problem?

If the removed symbols look like FT_Outline_Done_Internal, FT_Outline_New_Internal in a mature library then they are probably not of concern.

@grlee77 and @isuruf should we merge this one or is it OK to keep the current pinning?

I think the current pin is fine. If we can find a bug where the loose pinning is the culprit, we can merge this, but until then I'll leave this PR open.

If you want to close this that is fine. I could not reproduce the issue on the VTK end, but this issue is linked there so we can reopen as needed.