Update pinnings on R-base

[dpryan79]

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-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.

[dpryan79]

This will of course require a migration beforehand, which I presume is done elsewhere (not sure how that's orchestrated on conda-forge).

[ocefpaf]

If you want to start a migration take a look at #1513. However, the bot should've picked this one up automatically. Not sure what is going on here.

[CJ-Wright]

@ocefpaf my knowledge could be quite out of date, but r_base doesn't have a compatibility specification in either the meta.yaml as a run_exports or in the pinning conda_build_config. All of the r migrations in the past have been started by hand.

I am making this comment solely in my personal capacity and am not conveying any rights to any intellectual property of any third parties.

edit: it does have a min/max pin in the conda-build-config.

[hmaarrfk]

to be honest, I think that the r-base recipe may need a bit of touchups in light of the challenges encountered in conda-forge/r-base-feedstock#213

that PR seems to resolve some important issues, but it seems like the maintainers haven't had time to provide feedback or the cleanup necessary.

I would be cautious in starting a migration for r-base in light of the lack of comments on that PR from the r-base maintainers

[dpryan79]

Now that conda-forge/r-base-feedstock#213 has been merged in, shall we consider again moving forward with a migration?

[hmaarrfk]

Is there any interest in waiting for conda-forge/r-base-feedstock#210

[dpryan79]

No need to wait from my side. This migration is needed for ~3000 package updates over on Bioconda and we don't build for Windows.

[bgruening]

This looks good to me. Thanks @isuruf for adding the migration.
Can we merge this PR?

[hmaarrfk]

Sorry for the delay, I didn't see that you were listed as a maintainer in r-base bgruening

[jdblischak]

Why is the recipe number bumped for the migration to R 4.2? This causes a new R 4.1 version to be uploaded as well, which seems unnecessary, at least to me. It wouldn't really matter for a few recipes, but this is going to upload thousands of essentially duplicate r41 binaries to anaconda.org (the only difference being the build number).

[isuruf]

Even if the build number was not bumped, there'll be a new version uploaded because some of the pinnings (like compiler) have changed and there's a different hash than the one when it was last rebuilt. Therefore bumping the build number avoids two packages with R 4.1 with the same build number, but different hashes.