Thanks to Ott and others, I now have separate GitHub
repositories, one for each of the packages combined in the Ecdat R-Forge
project. In case it might help others in the future, I will summarize
here key things I did to make this transition:
1. I first copied the "Ecfun"
Hi, Danny et al.:
Thanks. I found ".Rbuildignore" on my local copy that was,
however, not tracked by git. I added that, then committed and pushed
the change.
Obviously, I'm new to travis and am still learning how to read
and understand what it's saying -- especially on how to
Hi Spencer,
To get rid of the .travis.yml note add a .Rbuildignore file with this line:
^\.travis\.yml$
This will exclude the file from the build.
The build is failing because of a warning. As noted in the log, Travis is
treating a warning as an error:
Found warnings, treating as errors
It's a
Luke, thanks for considering the issue. I would like to
try to separate the problem into two parts, as I _think_
your comments address primarily part 2 below:
1. How can we avoid significant and possibly crippling
stalls on error with these non-standard calls.
2. What is the best way to view
Hello:
Suggestions for whomever maintains "R CMD":
1. Can you change it so it doesn't complain about the
presence of ".travis.yml", at least on GitHub?
2. What do you suggest people do to find error messages in
the output? I ask, because I'm getting "build
This is probably best viewed in the context of other issue with
displaying calls, such as issues arising from calls constructed in
non-standard evaluation contexts. Might be good to move to a wishlist
item in bugzilla.
Best,
luke
On Sat, 13 Jul 2019, brodie gaslam via R-devel wrote:
> When larg
