Fix dependencies

[isuruf]

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-webservices]

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.

[isuruf]

Going to merge this and if something breaks we can remove the builds.

[mbargull]

Thanks for looking into that!

It'd be helpful if you add a short description with references for pull requests.
Doesn't have to be much (I actually prefer it to be succinct -- to not waste your and others' time), e.g.,

Fixes <problem> encountered at <issue link> .
refs:
- <additional link 1>
- <additional link 2>

Adding references tremendously helps with (re-)discoverability and traceability (esp. once time passes).

[mfansler]

To what extent should the changes here be applied to the other branches?

Currently, appears that removing these pinned dependencies from the main branch has led to a situation where the other branches no longer get migrations for their distinct dependencies. A specific example is the libxml2212 migration. A proj931 migration PR on r-rgdal-feedstock cannot solve a valid host environment for any R 4.2 builds due to the latest libgdal using libxml2=2.12, but no r-base=4.2 builds have built against that. That is, main here no longer has libxml2, while the other branches still include it, but there have been no PRs from libxml2212 migration for them.

[jdblischak]

The lack of libxml2 migration to the 4.2.x branch is also causing a problem in conda-forge/r-tiledb-feedstock#70 (comment). Can we manually open a PR to migrate to libxml2 2.12?

[jdblischak]

For the short-term, I manually opened a PR to migrate r-base 4.2 to libxml2 2.12 (#288). But longer-term it would be nice to somehow address the lack of automated migrations to these supported branches

[mbargull]

longer-term it would be nice to somehow address the lack of automated migrations to these supported branches

Yep, I've opened regro/cf-scripts#1979 to track this.
But I'm not one of our infrastructure gurus, so can't really tell how much has to be done to get this working...