In case you still care, see
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16726
which even our very human spam detector hasn't decided to label as spam (yet).
-pd
> On 08 Feb 2016, at 18:34 , frede...@ofb.net wrote:
>
> Ah, thank you for that explanation. I somehow didn't catch that my
Hi All,
One thing that I've encountered with R CMD check is that if your package
uses some functions from a base package, then the corresponding NAMESPACE
imports do not seem to be automatically suggested. It might possibly an
issue with how one's system is configured, but say, with the --as-cran
We all love R CMD check. :) In my opinion it would be even better if
it had options to
- Run all checks, even if one fails with an error. I realize this
sometimes might not make sense (e.g. if there is no DESCRIPTION file),
but often does.
- Run all examples even if an example fails. I think it w
On 25.02.2016 11:31, Mikko Korpela wrote:
> On 23.02.2016 14:06, Mikko Korpela wrote:
>> On 23.02.2016 11:37, Martin Maechler wrote:
nospam@altfeld-im de
on Mon, 22 Feb 2016 18:45:59 +0100 writes:
>>>
>>> > Dear R developers
>>> > I think I have found a bug that can b
Aim for 3.3.1 then? It's not like we have hordes of people demanding to have
this fixed right here and now, or do we?
(A practical problem is that the version control dynamics dictate that at this
stage, commits to r-devel _will_ end up in 3.3.0 on April 14, unless backed out
and then inserted
On 23.02.2016 14:06, Mikko Korpela wrote:
> On 23.02.2016 11:37, Martin Maechler wrote:
>>> nospam@altfeld-im de
>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes:
>>
>> > Dear R developers
>> > I think I have found a bug that can be reproduced with two lines of
>> code
>> > a
