"internal error in pkgdepends"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the reported pak::pkg_install("nationalparkservice/NPSdataverse") command and follow the error path through select_next_task(state). Check how the four listed packages remain waiting to install. Done means the dependency installation no longer stops with the internal pkgdepends error.
Written by the indexing model from the issue text.
Description
Hello,
upon trying to use pak::pkg_install I got this error message, which state to report the error here:
pak::pkg_install("nationalparkservice/NPSdataverse")
#> ℹ Loading metadata database
#> ✔ Loading metadata database ... done
#>
#>
#> → Will install 4 packages.
#> → Will download 4 packages with unknown size.
#> + DPchecker 1.0.0 [bld][cmp][dl] (GitHub: 395992f)
#> + EMLeditor 0.1.6 [bld][cmp][dl] (GitHub: 9a59ee3)
#> + NPSdataverse 0.1.0 [bld][cmp][dl] (GitHub: 4ef90b5)
#> + NPSutils 1.0.0 [bld][cmp][dl] (GitHub: 4fb0bb3)
#> ℹ Getting 4 pkgs with unknown sizes
#> ✔ Cached copy of NPSdataverse 0.1.0 (source) is the latest build
#> ✔ Cached copy of DPchecker 1.0.0 (source) is the latest build
#> ✔ Cached copy of EMLeditor 0.1.6 (source) is the latest build
#> ✔ Cached copy of NPSutils 1.0.0 (source) is the latest build
#> Error: ! error in pak subprocess
#> Caused by error in `select_next_task(state)`:
#> ! Cannot select new package installation task.
#> ℹ 4 packages still waiting to install: NPSdataverse, DPchecker, EMLeditor, and
#> NPSutils.
#> ℹ This is an internal error in pkgdepends, please report an issue at
#> <https://github.com/r-lib/pkgdepends/issues>.
- Dominant language
- C
- Stars
- 135
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from r-lib/pkgdepends
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 4 comments ·
-
Allow trailing slash(es) in urls?Possibly taken @BjarkeHautop claimed this 101 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
r-lib/pkgdepends#477 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
r-lib/pkgdepends#486 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
r-lib/pkgdepends#484 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
r-lib/pkgdepends#483 · 1 comment ·
All issues in r-lib/pkgdepends
Similar issues
-
area/docs
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Clodmony/starship-coop#72 ·
Maintainers usually reply within 1 day
-
ospf6d: heap-use-after-free in seqnumber_mismatch()/bad_lsreq() when a neighbor is deleted with events pendingPossibly taken @lichenlang89 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 2 days
-
5700模组网络优先级问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
luainkernel/lunatik#2372 ·
Maintainers usually reply within 1 day