callr_remote_error: Cannot install packages...can't find on remote crazycapivara/h3-r

[7yl4r]

Describe the bug

Error: Error: <callr_remote_error: Cannot install packages:
  * deps::.: Can't install dependency h3
  * h3: Can't find package called h3.

To Reproduce

• link to the full logs of the failed build](https://github.com/marinebon/obisindicators/actions/runs/3482015857/jobs/5823833311).

Expected behavior
The package should install successfully as it does locally when doing devtools::install_local() or remotes::install_github()

Additional context
This package name is unusual in that it has a dash (-) in the name; there is some speculation that this may be related to the bug.

[gaborcsardi]

If the package name is not the same as the repo name, you need to tell pak what the name of the package is, like this:

Remotes:
    h3=crazycapivara/h3-r

[7yl4r]

trying that yielded a different error:

  Error: Error: <callr_remote_error: Cannot install packages:
  * pkgdown: dependencies must be TRUE, FALSE, NA or a list of dependency types>
   in process 10233 

• link to build error

[gaborcsardi]

Try using the latest actions, i.e. r-lib/actions/...@v2 everywhere, and specify pkgdown as any::pkgdown, like in the example workflow at https://github.com/r-lib/actions/blob/v2-branch/examples/pkgdown.yaml#L33

In general, it is best to follow the example workflows.

[7yl4r]

Thanks! I started over using the @ v2 example action. That has gotten us to a new error related to #2126. This one might might be a detail I am missing in the pkgdown docstring for one of our functions but I can't find it.

[gaborcsardi]

pkgdown now errors on the CI if you don't document all exported objects. You can also put them in a section called "internal" and then there is no error and the topics are left out, if you don't want to document them. See the pkgdown docs.

[github-actions]

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue