Rebuild for proj-6.2.1

[xylar]

Checklist

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

[conda-forge-linter]

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.

[xylar]

@conda-forge-admin, please rerender

[xylar]

I got a little over eager. GDAL isn't there yet.

[hobu]

The conflict is confusing (and has been there a while).

libgdal=3.0 -> libuuid[version='>=2.32.1,<3.0a0']
postgresql -> libuuid=1.0

Does this mean that the postgresql feedstock needs to be bumped to catch a newer libuuid?

[xylar]

@hobu, my experience is that these conflict reports are not usually very helpful. I think the problem is actually that the gdal rebuild hasn't finished yet and the new versions aren't yet available on conda-forge but the solver found a set of packages that it thinks would work except for this conflict with libuuid. I think that's not the path we would want to take so the error just isn't very helpful.

I usually debug these kinds of things by using conda create and just adding libraries one by one until the conflict emerges (usually with a more helpful message about the conflict). It's tedious but gets me where I need to be, whereas these default conflict reports are nearly always totally useless to me.

[xylar]

@sodre or @dwnoble, I think we're good here. Please merge if you're okay with the rebuild for the latest proj.