setup-r-dependencies@v2 fails

[ShixiangWang]

The error is (https://github.com/ShixiangWang/gcap/actions/runs/7622389111/job/20760357040):

 ℹ Creating lockfile '.github/pkg.lock'

  ✔ Updated metadata database: 6.07 MB in 10 files.

  ℹ Creating lockfile '.github/pkg.lock'
  ℹ Updating metadata database
  ✔ Updating metadata database ... done

  ℹ Creating lockfile '.github/pkg.lock'
  ✖ Creating lockfile '.github/pkg.lock' [7.8s]

  Error: 
  ! error in pak subprocess
  Caused by error: 
  ! Could not solve package dependencies:
  * deps::.: ! pkgdepends resolution error for deps::..
  Caused by error: 
  ! Invalid pluralization directive: `?`
  * local::.: ! pkgdepends resolution error for local::..
  Caused by error: 
  ! Invalid pluralization directive: `?`
  * any::sessioninfo: dependency conflict
  * any::pkgdown: dependency conflict
  ---
  Backtrace:
  1. pak::lockfile_create(c(deps, extra_deps), lockfile = ".github/pkg.lock", …
  2. pak:::remote(function(...) { …
  3. err$throw(res$error)
  ---
  Subprocess backtrace:
  1. base::withCallingHandlers(cli_message = function(msg) { …
  2. get("lockfile_create_internal", asNamespace("pak"))(...)
  3. prop$stop_for_solution_error()
  4. private$plan$stop_for_solve_error()
  5. pkgdepends:::pkgplan_stop_for_solve_error(self, private)
  6. base::throw(new_error("Could not solve package dependencies:\n", msg, …
  7. | base::signalCondition(cond)
  8. global (function (e) …
  Execution halted
  Error: Process completed with exit code 1.

It's hard for me to understand the error and I don't know how to fix such a case.

Does it relate to the DESCRIPTION file setting?

Best,

Shixiang

[gaborcsardi]

https://github.com/ShixiangWang/gcap/blob/f335753c532ab30bce5238082e420e25cdabd68f/DESCRIPTION#L47

bitbucket:: remotes are not supported, but you can probably try a git:: remote instead.

[ShixiangWang]

@gaborcsardi Thank you, I will make a modification :)

[github-actions[bot]]

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