RMI / RMI/resources

Work around for Error ... there is no package called 'utf8'

Open
#192 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug r-stats troubleshoot
Dominant language
No language data
Stars
17
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Our process to release a package walks through the steps in usethis::use_release_issue(). Unfortunately, the check on Windows that rhub::check_for_cran() runs fails with Error ... there is no package called 'utf8'. The workaround is this:

rhub::check(
  platform="windows-x86_64-devel",
  env_vars=c(R_COMPILE_AND_INSTALL_PACKAGES = "always")
)

Or maybe

ck <- rhub::check_for_cran(env_vars=c(R_COMPILE_AND_INSTALL_PACKAGES = "always"))

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the release steps in usethis::use_release_issue() and the Windows check performed by rhub::check_for_cran(). Reproduce the missing utf8 package error, then compare behavior with R_COMPILE_AND_INSTALL_PACKAGES set to "always"; done means the Windows release check completes without requiring the documented workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.