r-pak: prepare 0.11.1 update and add r-tstoml - #392
Draft
bshor wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update pak, an R package installer and dependency resolver, from 0.9.5 to 0.11.1 and add its missing TOML-editing dependency, r-tstoml. The existing r-tsitter recipe is unchanged. One commit per package.
Draft: not ready to merge. Verification exposed a system-dependency compatibility blocker described below.
548e2e71195906584b17ac0aa83e4d3edcef8da2, with a SHA-256 checksum and manual update tracking. It is not on CRAN and has no release tags; the published source asset still imports the obsoletetspackage, while this source importstsitter.Verification
test-ppm-sso.Rand two upstream skips; makepkg therefore fails in check().Blocker / Review Question
The packaged and current CRAN pkgcache 2.2.5 has
cran_app, but lacksppm_sso_app,ppm_sso_login,ppm_sso_status, andppm_sso_logout. Pak 0.11.1 bundles newer pkgcache code containing those functions, and its public SSO wrappers call them. With BioArchLinux's system-library patch, the SSO test errors withattempt to apply non-function.This is not merely a missing test fixture: suppressing the test would leave the new SSO feature broken. Should this update wait for a compatible pkgcache release, or would you prefer a separately reviewed pkgcache backport/development-source update? No tests have been disabled and no shared dependency has been changed in this PR.