Thanks Dirk. IMO the package is in good shape otherwise. I'll wait hear
from the CRAN maintainers.
S
On Wed, Apr 4, 2018 at 2:53 PM, Dirk Eddelbuettel wrote:
>
> On 4 April 2018 at 14:15, Steven Scott wrote:
> | These appear to be caused by an ill formed std::set or std::function in
> the
> |
On 4 April 2018 at 14:15, Steven Scott wrote:
| These appear to be caused by an ill formed std::set or std::function in the
| STL implementation of the host machine. If I'm reading that wrong someone
| please let me know.
AFAICT it needs C++11 explicitly set which that machine (with a new clang-
I've been trying to update the Boom package to the next version, and it
hasn't been going so well. Hoping someone can help me figure out what next
steps I should take.
I got the attached mail from auto-check. From what I can tell the new
version of Boom (0.8.0) has two issues. Some long path na
I recently submitted a new version (v0.8.19) of my FSA package to CRAN. It was
rejected at the pre-test level because of problems with automatic checks. There
were three links for me to see what these problems were.
The first link from CRAN was to a win-builder check log
(https://win-builder.r-
