Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pak can not resolve correct package version, only tries the latest. #668

Closed
gongyh opened this issue Jul 30, 2024 · 2 comments
Closed

pak can not resolve correct package version, only tries the latest. #668

gongyh opened this issue Jul 30, 2024 · 2 comments

Comments

@gongyh
Copy link

gongyh commented Jul 30, 2024

Error:
! error in pak subprocess
Caused by error:
! Could not solve package dependencies:

  • deps::.: Can't install dependency rstatix
  • rstatix: Can't install dependency car
  • car: Can't install dependency pbkrtest (>= 0.4-4)
  • pbkrtest: Needs R >= 4.2.0
  • rcmdcheck: dependency conflict
  • any::sessioninfo: dependency conflict

The latest version of pbkrtest (version 0.5.3) needs R 4.2.0, but not versions between 0.4-4 and 0.5.2.

more details: https://github.com/gongyh/RamanD2O/actions/runs/10154082037/job/28078611827

@gaborcsardi
Copy link
Member

This is not a pak issue, this is how CRAN works. They typically only include the latest versions of packages in their package metadata, so that's what we work with: https://cran.r-project.org/src/contrib/PACKAGES

@HeveraletLaidCenx
Copy link

HeveraletLaidCenx commented Nov 25, 2024

@gongyh Hi, I just encountered a similar situation...

I wrote a simple tool to implement a R package dependencies tree parsing and installation including outdated version checking.

I'm not sure if it's good enough, but it works for me.

If anyone encounters such a scenario, you might consider giving it a try XD.

demo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants