You can assume that CRAN packages are available within a day for on
demand checks and even at once for CRAN incoming checks on winbuilder.
Nevertheless, I have no idea where the problem comes from given the
standard test mechanisms are not use and hence output does not show what
the actual test was.
Best,
Uwe Ligges
On 13.06.2019 06:59, David Hugh-Jones wrote:
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
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 at 23:26, Duncan Murdoch <murdoch.duncan at gmail.com>
wrote:
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
Windows-only, so I can't even download a Docker image and investigate
way.
TBH I am not very enthused by having to treat CRAN servers as "ground
truth", when there seems no way to reliably reproduce their
figure out what versions of packages are used, etc. Am I missing
Is another world possible?
Nothing is forcing you to release your package on CRAN. The only
advantage to doing so is that they maintain high standards, which means
people trust them.
Just put your package on Github, and anyone can use it, no matter how
bad it is.
Duncan Murdoch
and it seems to relate to the openxlsx package, which is on 4.1.0.1
May 28 - presumably long enough for the latest version to be available
win-builder. Any ideas would be welcome....
David
[[alternative HTML version deleted]]