Too many layers of complexity for me, can you take the package sources
and zat /or zip) them for me and send them? Then I'll take a look.
Best,
Uwe Ligges
On 12.06.2019 08:23, Rob Foxall wrote:
Thanks. I ran in R:
devtools::build("myPackage")
That gave me a warning:
NB: this package now d
Thanks so much for looking into this. You were right, my path that I
had been too lazy to update was pointing at an older installation of R
that I had been too lazy to uninstall.
On Wed, Jun 12, 2019 at 6:41 PM Uwe Ligges
wrote:
>
> So this is likely caused by your setup as I simply get
>
> $ R C
Hi all,
Not for the first time, my package has a bug that isn't found on rhub,
travis, appveyor, or my local machine, but is found on CRAN. This time it's
Windows-only, so I can't even download a Docker image and investigate that
way.
TBH I am not very enthused by having to treat CRAN servers as
On Wed, 12 Jun 2019 at 22:58, David Hugh-Jones wrote:
>
> Hi all,
>
> Not for the first time, my package has a bug that isn't found on rhub,
> travis, appveyor, or my local machine, but is found on CRAN. This time it's
> Windows-only, so I can't even download a Docker image and investigate that
>
On 12/06/2019 4:57 p.m., David Hugh-Jones wrote:
Hi all,
Not for the first time, my package has a bug that isn't found on rhub,
travis, appveyor, or my local machine, but is found on CRAN. This time it's
Windows-only, so I can't even download a Docker image and investigate that
way.
TBH I am no
Hi Duncan,
Of course I appreciate the value of a centralised repository, and I
acknowledge the hard work that goes into maintaining it. That does not mean
that it should be beyond criticism. I wrote out of frustration, but also
because I hope things could be better.
David
On Wed, 12 Jun 2019 a
