Without code we are guessing. A bug is possible but I will make another guess
suggestion.
Delete all binary files created by devtools during compilation in your package
directory.
devtools::load_all() is so fast partly because it recompiles the C/Fortran
files only when necessary
but sometimes
Dear Georgi,
Thanks for the suggestion, but that does not work either.
I can send the code if that would help. But note that the code was
working fine until I installed a new R-devel version. But perhaps there
is an update in how the routines should be registered. I am doing it
like this:
#inclu
After installing a new version of R the OP may have to rebuild (and retest)
packages like pkgload that define functions by grabbing functions from the
base package and modifying them, as in pkgload/R/namespace-env.r:
onload_assign("makeNamespace",
eval(
modify_lang(
extract_lang(body(l
The problem was resolved by installing again a new version of devtools.
However, this new version gives other problems: devtools::check() says
the DESCRIPTION file is missing a License field, but there IS a license
field in this file.
On 7-11-2018 16:59, William Dunlap wrote:
> After installing
Also note that William's suggestion is documented at the bottom of the
"Generic Functions and Methods" section of Writing R Extensions.
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Generic-functions-and-methods
"... as a package can take over a function in the base package and
make
I am considering a CRAN release of a new package and was using R-winbuilder as
a check. The check was successful with all but the "old-release" version (see
https://win-builder.r-project.org/UhyHnNyn4Ukz/00check.log). The two errors
both appear to be related to tests using testhtat::expect_outpu
Does it happen consistently? If it's only happened once, could be a
transient glitch in package dependencies. I'd try re-testing, as a
start. Alternatively, if you're willing to add an R >= 3.5.1 dependency
to your package, presumably CRAN won't mind if it fails tests on
old-release ...
O
My package had this issue and still got accepted. I think it is a known
transient glitch. Just mention it when you submit.
On Wed, 7 Nov 2018 at 22:05, Ben Bolker wrote:
>
> Does it happen consistently? If it's only happened once, could be a
> transient glitch in package dependencies. I'd tr
Ben ... I tried two more times today and still the same issue. Perhaps it is
transient on a different time scale than what I have tested. I was hoping to
not raise the R dependency level, but had thought about that as well. Thank you
for your thoughts.
David ... thank you for the experience and
I think this error has to do with the binary version of stringi for
Windows oldrel being out-of-date in CRAN (version 1.1.7 while source is
at 1.2.4). The current version of stringi under Windows gives a
compilation note, so the binary is not available in CRAN. This causes
difficulties even wit
10 matches
Mail list logo
