No, I can't tell you whether the behaviour you saw was intentional or
not, I didn't write it. But the CRAN policy (which is the motivation
for many of the checks) says "Packages should not write in the user’s
home filespace (including clipboards), nor anywhere else on the file
system apart fro
Hi Duncan,
Thanks for the explanation. Using a temporary directory is what I’m
doing at the moment as a workaround.
What confused me was that `R CMD check` *already* works inside a new
directory (a set of different ones, in fact), and it doesn’t seem to
be documented anywhere that this is the int
On 14/04/2020 6:23 a.m., Konrad Rudolph wrote:
I have a package vignette that reproducibly fails the second time
round in `R CMD check`, in the “checking re-building of vignette
outputs” step.
I have uploaded a small reprex to GitHub [1]. But in a nutshell the
vignette contains a subfolder `foo`
Yes, should be fixed by tmorrow,
Uwe
On 08.04.2020 00:16, Martin Morgan wrote:
This is the same as
https://stat.ethz.ch/pipermail/r-package-devel/2020q1/005256.html
and due I believe to stale packages on the CRAN windows builder; the solution
is I believe on the CRAN side.
Martin Morgan
I have a package vignette that reproducibly fails the second time
round in `R CMD check`, in the “checking re-building of vignette
outputs” step.
I have uploaded a small reprex to GitHub [1]. But in a nutshell the
vignette contains a subfolder `foo`, and a file `foo/bar`. And the
`test.rmd` vignet
I just looked, you got a repsonse from Swetlana Herbrandt on Dec 16.
Will forward privately.
Best,
Uwe Ligges
On 10.04.2020 05:08, John Lawson wrote:
Ok, thanks.
On Thu, Apr 9, 2020 at 1:46 PM Duncan Murdoch
wrote:
On 09/04/2020 3:28 p.m., John Lawson wrote:
I submitted the Package AQL
