On 18.06.2018 16:38, Marius Hofert wrote:
On Sun, Jun 17, 2018 at 2:13 AM Uwe Ligges
wrote:
On 16.06.2018 21:46, Marius Hofert wrote:
Dear DevelopeRs,
Is there a recommended procedure for addressing "Additional issues" if
they appear on CRAN checks?
Say you have some C code in a packag
Hi,
I tried to understand how to check memory access of an R package with
C code; see
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Checking-memory-access
I'm about 90% sure I understood WRE Section 4.3.2 about valgrind. In essence:
1) When configuring R before make, use the confi
On Sun, Jun 17, 2018 at 2:13 AM Uwe Ligges
wrote:
>
>
>
> On 16.06.2018 21:46, Marius Hofert wrote:
> > Dear DevelopeRs,
> >
> > Is there a recommended procedure for addressing "Additional issues" if
> > they appear on CRAN checks?
> >
> > Say you have some C code in a package which checks fine (S
Dear Simon Urbanek,
Since a few weeks I am getting a CRAN-check error under OSX for the package
"spp" (https://cran.r-project.org/web/checks/check_results_spp.html):
"Package required but not available: ‘Rsamtools’
Rsamtools is available on Bioconductor and the error shows up only on MAC. Is
it
Perhaps ask Simon Urbanek, the CRAN Mac maintainer, what is going on here.
Best,
Uwe Ligges
On 18.06.2018 11:33, Carmen M. Livi wrote:
Hi all,
I have a question regarding the CRAN checks for package spp:
https://cran.r-project.org/web/checks/check_results_spp.html
We didn't update or chan
Hi all,
I have a question regarding the CRAN checks for package spp:
https://cran.r-project.org/web/checks/check_results_spp.html
We didn't update or change anything in the package, but since a few
weeks the CRAN check for OSX gives an error saying that a dependency is
not available:
Packag
