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

pkgdown GitHub workflow fails because curl 404 error for lme4 and rlang #13

Closed
egouldo opened this issue Nov 6, 2023 · 5 comments
Closed
Assignees
Labels
bug an unexpected problem or unintended behavior documentation

Comments

@egouldo
Copy link
Owner

egouldo commented Nov 6, 2023

See rstudio/renv#96

@egouldo egouldo added bug an unexpected problem or unintended behavior documentation labels Nov 6, 2023
@egouldo egouldo added this to the publication milestone Nov 6, 2023
@egouldo egouldo self-assigned this Nov 6, 2023
egouldo added a commit that referenced this issue Nov 6, 2023
@egouldo egouldo changed the title pkgdown GitHub workflow fails because curl 404 error for lme4 and clang pkgdown GitHub workflow fails because curl 404 error for lme4 and rlang Nov 6, 2023
@egouldo
Copy link
Owner Author

egouldo commented Nov 6, 2023

OK can confirm that incorrect URL is recorded in the lock file for these packages!

Likely because I'm using homebrew-installed R, as per tagged issue in description.

renv::upgrade() didn't seem to fix it. So perhaps I'll try reinstall these packages and see if the URLs are fixed, or otherwise I'll manually override them in the lock file by hand.

ap <- available.packages(type = "source")
ap[c("rlang", "lme4"), c("Package", "Version", "Repository")]
#>       Package Version    Repository                            
#> rlang "rlang" "1.1.2"    "https://cran.rstudio.com/src/contrib"
#> lme4  "lme4"  "1.1-35.1" "https://cran.rstudio.com/src/contrib"

Created on 2023-11-06 with reprex v2.0.2

@egouldo
Copy link
Owner Author

egouldo commented Nov 6, 2023

Potentially also related to rstudio/renv#1717

@egouldo
Copy link
Owner Author

egouldo commented Nov 6, 2023

Using the GitHub installation was a successful workaround for this issue and the packages were able to be downloaded and installed in the GitHub pkgdown run.

However, now the run is cracking it over igraph:: 6211c09

I'm going to try the same approach for this package, and for any package thereafter that won't install.

@egouldo
Copy link
Owner Author

egouldo commented Nov 6, 2023

dang... can't install igraph with dev tools locally because compilation is failing.

https://stackoverflow.com/questions/68248503/failing-to-install-igraph-package-in-r suggests installing binary rather than from source

@egouldo
Copy link
Owner Author

egouldo commented Nov 6, 2023

Using binary igraph won't work because actually the issue is that required libraries are missing. This is a known issue on ubuntu machines, which the GitHub action is using for the pkgdown build:

suggested solution:

sudo apt-get install -y libcurl4-openssl-dev libxml2-dev libssl-dev

Not quite sure where to run this. I think I need to run it in the GH workflow script before any of the R gh actions.

igraph/rigraph#209 (comment) shows how to set this up in GHA. But, it seems strange that the header install comes after the dependency installation, I can't imagine this is going to work. Also, the binary might need libglpk40, not the dev versions...

- name: igraph-deps
  run: sudo apt-get install -y libglpk40`

egouldo added a commit that referenced this issue Nov 6, 2023
#13 install libglpk40 to fix igraph install error
@egouldo egouldo closed this as completed Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior documentation
Projects
None yet
Development

No branches or pull requests

1 participant