Thank you again for your responses Rodrigo Tobar. I'm happy to call this a
solution. I've got some testing to do but I'm hoping to get this sent back
to CRAN soon.
Thank you for your help!
Brian
On Tue, Aug 11, 2020 at 11:28 PM Rodrigo Tobar wrote:
> Hi Brian,
>
> On
stall it locally so the R checks can proceed without the warning
> (or set _R_CHECK_BASHISMS_ to FALSE to skip that particular check, again
> locally), but that shouldn't be a problem in CRAN, as it should be
> installed there already.
>
> Cheers,
>
> Rodrigo
>
>
Hi R-pkg-devel,
My package
https://github.com/knausb/vcfR
has been archived on CRAN because I was asked by CRAN to address issues
that I was unable to address before the deadline I was given. The issue I'm
struggling with is that when I use
```
R CMD check --as-cran vcfR_1.12.0.tar.gz
```
I ge
ddress).
>
> On 7/22/20 7:05 PM, brian knaus wrote:
> > Hello R-pkg-devel,
> >
> > Our package vcfR,
> >
> > https://github.com/knausb/vcfR
> >
> > has been removed from CRAN because they asked me to make changes that I
> > have not been a
here I receive mail from various mailing
lists I've signed up for. For example, mail I receive from "R-pkg-devel"
comes to this address. So I feel that this is confusion on the side of
CRAN. Does anyone see a reason for *why* this may be consider
gt;
> > The question is why you don't always get that warning.
>
> Because there was a bug in R that the warnings was not produced for a
> long time, and this is now fixed in recent verisons of R-devel. Hence ou
> only get it here.
>
> Best,
> Uwe Ligges
>
>
&g
Does anyone know the current status of r-hub? My package (
https://github.com/knausb/vcfR) is throwing warnings on R-devel (
https://cran.r-project.org/web/checks/check_results_vcfR.html) and CRAN has
asked me to fix it. Tried r-hub but it failed.
https://builder.r-hub.io/status/vcfR_1.9.0.9000.ta
I was tracking down problems with my package yesterday that were specific
to r-devel and I had trouble reproducing the errors. I believe the issue is
that the rhub and the docker/rocker r-devel were not using the most recent
version of r-devel. My solution was to add r-devel to my travis ci.
https