Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt at updating from R v4.1.3 to v4.2.0 #208

Closed
wants to merge 2 commits into from

Conversation

AstrobioMike
Copy link

@AstrobioMike AstrobioMike commented May 22, 2022

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.

Hi there :)

I'm trying to get R version 4.2.0 to be available to be installed through conda-forge r-base.

I'm not familiar with a lot of what is going on here, so it's possible/likely my simplistic changes here are not all that's needed to do this. I apologize for my ignorance if that's the case!

Only changes made were in recipe/meta.yaml
- changed version from 4.1.3 to 4.2.0
- updated sha256sum accordingly
- set build to 0

Thanks!

updated R version from 4.1.3 to 4.2.0, sha256sum accordingly, and set build to 0
@conda-forge-linter
Copy link

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.

@AstrobioMike
Copy link
Author

@conda-forge-admin, please rerender

@isuruf
Copy link
Member

isuruf commented May 22, 2022

See #205

@AstrobioMike
Copy link
Author

ah, silly of me not to have looked first, thanks! closing this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants