Dear Joris,
indeed, the the data sets saved as R-files constituted the issue. As suggested
by you, saving them as *.rda helped.
Enormous thanks for your prompt and useful advice. The new version of the
R-package ddalpha (1.3.3, on CRAN now) causes no problems during the
byte-compilation phase.
If you are in a position to install the development version of git2r, that
is worth a shot.
devtools is calling git2r, which uses libgit2 (among other things), not the
system Git you are probably using when you "push to GitHub".
Your difficulty has a lot in common with this issue:
https://github.
I am trying to (re)submit my package to CRAN using devtools::release(), which I
have been doing for a couple of years without any serious glitches. I just
updated to R 3.5.0 and am using RStudio 1.1.447. I am wondering if this new
error I am getting is known to others: ERROR: Error in 'git2r_re
I wrongfully stated that CRAN added a line. The line was not added but
changed (and not in the SVN repo). A diff between both downloads is
available here:
https://gist.github.com/boegel/2ea28647f00ddd9b18f9b1a0ac6dd2b4
Cheers
Joris
On Mon, Apr 30, 2018 at 6:03 PM, Joris Meys wrote:
> In a disc
In a discussion of twitter it was pointed out that the checksums of
packages change after publication on CRAN. One example is the Matrix
package version 1.2-12, which was available on CRAN already on nov 17, 2017
but got a different checksum on nov 20, 2017. This caused issues in eg
easybuilders.
Dear pavlo,
fwiw, the binary of ddalpha 1.3.2 installs just fine on Windows 10. When
building from source, I get a whole lot of warnings about uninitialized
variables, comparisons between signed and unsigned integers. The
compilation of the source code doesn't have a large impact on the memory. I
