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.

Sign up for GitHub

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

Jump to bottom

triggering CRAN warnings when pandoc too old or not available #2165

Closed
1 of 3 tasks
achubaty opened this issue Jun 10, 2021 · 2 comments
Closed
1 of 3 tasks

triggering CRAN warnings when pandoc too old or not available #2165

achubaty opened this issue Jun 10, 2021 · 2 comments

Comments

@achubaty
Copy link

achubaty commented Jun 10, 2021 •
edited
Loading

I've recently received a little push back from CRAN on rmarkdown warnings on r-patched-solaris-x86 and r-oldrel-macos-x86_64 produced during CRAN checks on my package SpaDES.core.

## r-patched-solaris-x86
    --- re-building ‘i-introduction.Rmd’ using rmarkdown
    Warning in engine$weave(file, quiet = quiet, encoding = enc) :
     Pandoc (>= 1.12.3) not available. Falling back to R Markdown v1.
    --- finished re-building ‘i-introduction.Rmd’

## r-oldrel-macos-x86_64
    --- re-building ‘i-introduction.Rmd’ using rmarkdown
    Warning in engine$weave(file, quiet = quiet, encoding = enc) :
     Pandoc (>= 1.12.3) and/or pandoc-citeproc not available. Falling back to R Markdown v1.
    --- finished re-building ‘i-introduction.Rmd’

They have accepted ("for now") my package submission, because I pointed out that many CRAN packages show the same pandoc warnings (e.g., sf, idmodelr, and matlib, and many others).

I doubt CRAN will be installing the latest pandoc on the affected systems, but perhaps they might.
I'd rather not stop using rmarkdown to build vignettes, so I'm filing this issue here in hopes there is a solution I (and other package maintainers) are missing.
Is it easy enough to change the current warnings into messages?

Thank you!

Checklist

When filing a bug report, please check the boxes below to confirm that you have provided us with the information we need. Have you:

  • formatted your issue so it is easier for us to read?

  • [] included a minimal, self-contained, and reproducible example? See links to CRAN check results above.

  • [] pasted the output from xfun::session_info('rmarkdown') in your issue? N/A - this is a CRAN machine issue

  • upgraded all your packages to their latest versions (including your versions of R, the RStudio IDE, and relevant R packages)? N/A - this is a CRAN machine issue

  • installed and tested your bug with the development version of the rmarkdown package using remotes::install_github("rstudio/rmarkdown")? N/A - this is a CRAN machine issue
@yihui
Copy link
Member

yihui commented Jun 10, 2021

I doubt CRAN will be installing the latest pandoc on the affected systems, but perhaps they might.

The answer is likely to be "No" for Solaris, unfortunately. For macOS, I remember one CRAN maintainer had trouble with installing Pandoc on a certain version of macOS, but I forgot what exactly the problem was.

Is it easy enough to change the current warnings into messages?

It is, and I will do that (in knitr).

Thanks for the report!

clrpackages pushed a commit to clearlinux-pkgs/R-knitr that referenced this issue Sep 14, 2021
@fenrus75 @clrpackages
R-knitr: Autospec creation for update from version 1.33 to version 1.34
1d94ca4 
Andrew Heiss (1):
      fix #2038: add ability to pass arguments to dvisvgm through engine.opts (#2039)

Christophe Dervieux (3):
      fix #1993: ignore some values of `fig.keep` (e.g., fig.keep = 'last') when there is only one figure in a chunk (#1996)
      Throw an error if inline result cannot be coerced to character (#2007)
      `include_*`

David C Hall (1):
      Use `conditionMessage()` to render conditions (#2016)

Jamie Lentin (1):
      utils-vignettes: Don't disable vtangle if .Rout.save exists (#2018)

Kenneth Blake Vernon (1):
      fix #1935: make collapse and strip.white = TRUE independent (#2011)

Will Landau (1):
      Add a new targets engine (#2031)

Yihui Xie (19):
      start the next version
      stop() early on CI servers if Pandoc is not found before building R Markdown vignettes: yihui/knitr#1864 (comment)
      use the chunk option engine.opts$classoption to customize the class options of `standalone` for the tikz engine: yihui/knitr#1985 (comment)
      close #1992 (originally reported at #492): allow customizing the tilde symbol ~ with the package option latex.tilde
      add the attribute data=external="1" to <iframe> generated by include_url() so that Pandoc won't base64 encode the URL: https://stackoverflow.com/q/67477667/559676
      close #1997: remove the duplicate \format{} on the help page ?opts_chunk
      use a dedicated env var to decide whether to check DESCRIPTION: yihui/knitr#1864 (comment)
      fix rstudio/rmarkdown#2165: emit a message instead of a warning when building rmarkdown vignettes without pandoc
      remove the code that was for backward compatibility with a very old version of knitr
      remove is_abs_path from knitr, which is no longer used in bookdown >= v0.22 (rstudio/bookdown@0098721)
      signal an error when buiding rmarkdown vignettes but Pandoc is not available, unless the vignette is build during R CMD check (in which case a message is emitted instead)
      specify the package name in \link[]
      `write_bib()` only uses the first URL if multiple are found in a package (#2028)
      close #1864: move markdown to Suggests (#2020)
      no longer test the declaration of dependency on markdown in DESCRIPTION or throw an error (#1864)
      update URLs
      do not throw an error in R CMD check when checking a package on CRAN but rmarkdown/markdown/Pandoc is not available (#1864)
      respect the env var R_CRANDALF: yihui/crandalf@d5949e5
      CRAN release v1.34

christophe dervieux (1):
      re-document. Trailing whitespace are removed in code now.

knokknok (1):
      cache.globals = FALSE means detecting all variables in a code chunk (#1898)
@github-actions
Copy link

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yihui @achubaty