[R-pkg-devel] Another CRAN-only bug
d@v|dhughjone@ @end|ng |rom gm@||@com
Thu Jun 13 06:59:52 CEST 2019
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.
On Wed, 12 Jun 2019 at 23:26, Duncan Murdoch <murdoch.duncan using gmail.com>
> 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
> > Anyway, the error is at:
> > and it seems to relate to the openxlsx package, which is on 184.108.40.206 since
> > May 28 - presumably long enough for the latest version to be available on
> > win-builder. Any ideas would be welcome....
> > David
> > [[alternative HTML version deleted]]
> > ______________________________________________
> > R-package-devel using r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/r-package-devel
Sent from Gmail Mobile
[[alternative HTML version deleted]]
More information about the R-package-devel