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.

Sign up for GitHub

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

Jump to bottom

If the package SHA is not a SHA, treat as NA #18

Open
MilesMcBain opened this issue Apr 7, 2022 · 0 comments
Open

If the package SHA is not a SHA, treat as NA #18

MilesMcBain opened this issue Apr 7, 2022 · 0 comments

Comments

@MilesMcBain
Copy link
Owner

Due to some unfortunate legacy decisions, multiple RStudio packages (remotes, pak) will populate the SHA metadata with the version number if the package is downloaded from CRAN.

In capsule this can trigger a warning when comparing packages to the lockfile that the version numbers are the same but the SHAs are different. It might be possible to avoid this by just treating anything that is a version number as an NA for the SHA.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MilesMcBain