-
Notifications
You must be signed in to change notification settings - Fork 53
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
rhub_check() fails in processing a vignette. #629
Comments
I am not sure how the prebuilt vignette is supposed to work, but this certainly needs latex for me when I run
|
There is some difference, somewhere, between your system and mine.
No complaints, no problem. And the tarball can be installed, again without problem. |
Because you have a complete LaTeX installation, and I don't. That's my point. |
Well, I'll have to find another approach. :-( |
Literally all I did was adding back the deleted workflow file, and apart from some minor check issues, it is working fine: https://github.com/gaborcsardi/kanova/actions/runs/10226059265 |
I need to to build a Windoze binary of a package that I am developing.
I tried to do this using rhub v2. First, I created a github repository for the package,
explicitly https://github.com/rolfTurner/kanova. Then I went to the local (cloned) directory for the package, started R, and executed
library(rhub)
rhub_check(platforms="windows")
After some time, failure was reported. The problem seems to be with
the vignette. I pre-compiled the vignette, doing
in the vignettes directory. This creates a file testStat.pdf in that directory. In "ordinary circumstances" (doing a local build), the build uses this pre-compiled file (i.e. testStat.pdf).
However when I use rhub_check(), the system seems not to use
testStat.pdf, tries to re-compile testStat.ltx and complains that
pdflatex is not available. See the screenshot:
Is there any way to either:
(a) get rhub_check() to use the pre-compiled file testStat.pdf, or
(b) make pdflatex available to rhub_check() ?
Thanks for any ideas.
The text was updated successfully, but these errors were encountered: