I am unable to reproduce a recent R CMD check failure on CRAN
concerning a package of mine: grattan.
This package Suggests: taxstats which is a large package hosted by an
Additional repository: https://hughparsonage.github.io/drat/
When I run this check locally, on travis, and on appveyor with
_R
>Additional repositories _with no_ packages:
> https://hughparsonage.github.io/drat/
Is it possible that the CRAN has a more stringent check and not only check that
there is a web link, But also that it is an R package repository?
This would explain the difference (but not if the lrepo is fine
It looks like the drat repo you linked to only has windows binaries for
3.2, which is probably too old for win builder? Just a guess.
On Mon, Feb 5, 2018 at 11:28 AM, Hugh Parsonage
wrote:
> I am unable to reproduce a recent R CMD check failure on CRAN
> concerning a package of mine: grattan.
>
1.
The repository is obviously *not* available for Windows as
https://hughparsonage.github.io/drat/bin/windows/contrib/3.5/PACKAGES
does not exist.
2.
> Since the failures only occur on Windows machines, and have only
> appeared recently, I have considered modifying the DESCRIPTION file to
> '
Thank you Uwe & Neal,
Following your suggestion, I tried inserting a binary version of the
package into the repository. I first tried inserting the package into
R 3.4; however, the note persists on winbuilder for R-release:
* using log directory 'd:/RCompile/CRANguest/R-release/grattan.Rcheck'
*