Closed mungojam closed 4 years ago
A lot of these issues stem from the shortcomings of install.packages, specifically, there is no way other than screen-scraping to detect the outcome of an install. I'm hoping to switch the backend to using the pkgdepends package, which will hopefully be a much more robust and flexible solution.
This may take a while though, pkgdepends is not yet on CRAN and I'm also pressed for spare cycles at the moment.
Unfortunately the current pkgcache/pkgdepends framework doesn't support local CRAN. Hopefully this will be addressed before pkgdepends leaves beta.
@mungojam can you give the v1.0 checkpoint a go? Unfortunately it doesn't support a local MRAN yet, but you can try it with the regular MRAN site.
Thanks for fixing, I don't really use R these days so I'd struggle to recreate. My old team also have to use an internal Cran so I imagine they'd need support for that first anyway
When running
we get this error:
It is happening in this bit of code:
https://github.com/RevolutionAnalytics/checkpoint/blob/233634f25764cec5a8e872d60e693f8045db88f0/R/checkpoint_log.R#L16-L23
And I believe it happens because the
install.packages
message is in a format that the interpreter isn't expecting.Here is what the message ends up looking like:
This leads to the byte count being a zero length character string:
which then fails when combined with the other columns:
The other columns are as follows:
It looks like the code tries to detect something similar but maybe just needs an extra check for the case where there are both binary and source packages:
https://github.com/RevolutionAnalytics/checkpoint/blob/233634f25764cec5a8e872d60e693f8045db88f0/R/checkpoint_log.R#L14