Re: [R-pkg-devel] What is the proper way to include README.Rmd generated png’s for package submission to CRAN?

Hi Sebastian, Many packages on CRAN have the problem yours exhibits and, as they update, will also need to address it. In mid-March Kurt Hornik emailed the associated maintainers to notify them that their package's README.html uses images that do not ship with the package. Here's the most impo

Re: [R-pkg-devel] What is the proper way to include README.Rmd generated png’s for package submission to CRAN?

I don't know if this is the proper way but if you host your package on github what you can do is add the image you want to be displayed in a 'inst' or 'docs' (in case you use pkgdown) folder push to github and then include a link to that image in README.md. This is how we do this in mapview h

[R-pkg-devel] What is the proper way to include README.Rmd generated png’s for package submission to CRAN?

Hi all, I’m stuck trying to figure out the appropriate way to include figures generated by a README.Rmd for package submission to CRAN. Any advice much appreciated. Here is the problem: - I generated an RMarkdown package README using `devtools::use_readme_rmd()`, leaving the chunk options intact

Re: [R-pkg-devel] Pretest failed - pandoc could not fetch local file

On 21/05/2017 6:14 PM, Dean Attali wrote: Thank you, you're right, I never realized the README on CRAN didn't show the images. Is there a way to force 'R CMD build' to include the images that are located in the vignettes directory? No, but you can include those files in some directory under in

Re: [R-pkg-devel] Pretest failed - pandoc could not fetch local file

Thank you, you're right, I never realized the README on CRAN didn't show the images. Is there a way to force 'R CMD build' to include the images that are located in the vignettes directory? --- Dean Attali President & CEO AttaliTech Ltd http://AttaliTech.com On 21 May 201

Re: [R-pkg-devel] Pretest failed - pandoc could not fetch local file

Please take the package tarball you submitted to CRAN and unpack it. It does *not* contain the files. Best, Uwe Ligges On 19.05.2017 20:18, Dean Attali wrote: I'm trying to submit an update to a package 'ddpcr' Here are the pretest logs: https://win-builder.r-project.org/incoming_pretest/17

Re: [R-pkg-devel] R force download of specific package versions in DESCRIPTION file

On 18/05/2017 10:34 AM, Martin Watts wrote: I have created a package (which I host on a local server) that I have set up to depend on exact versions of other packages, i.e my DESCRIPTION file looks like this: Package: myPackage Depends: R (>= 3.2.5) Imports: dplyr (== 0.5.0), lazyeva

[R-pkg-devel] R force download of specific package versions in DESCRIPTION file

I have created a package (which I host on a local server) that I have set up to depend on exact versions of other packages, i.e my DESCRIPTION file looks like this: Package: myPackage Depends: R (>= 3.2.5) Imports: dplyr (== 0.5.0), lazyeval (== 0.2.0), lubridate (== 1.6.0), ma

[R-pkg-devel] Pretest failed - pandoc could not fetch local file

I'm trying to submit an update to a package 'ddpcr' Here are the pretest logs: https://win-builder.r-project.org/incoming_pretest/170519_074459_ddpcr_18/00check.log I get a warning about pandoc not being able to find an image file. This file path exists and has not changed from the previous submi