On 20 March 2023 at 21:25, Guido Kraemer wrote:
| Thanks for the pointers! I think I fixed it. Here is what I did [1]. To
| be honest, I am not sure what was wrong before, but I followed [2],
| especially the code box at the very end of the section. I wonder if this
| was always wrong or if th
Thanks for the pointers! I think I fixed it. Here is what I did [1]. To
be honest, I am not sure what was wrong before, but I followed [2],
especially the code box at the very end of the section. I wonder if this
was always wrong or if the R internals changed at some point.
[1]
https://githu
On Mon, 20 Mar 2023 19:32:03 +
"Ruff, Sergej" wrote:
> but I thought Notes will also cause rejection when submitting a
> package to CRAN. Won´t that be a problem?
True, a NOTE during an automatic check may cause a rejection, but you
won't get this NOTE there. Automatic CRAN pre-tests are don
thanks,
but I thought Notes will also cause rejection when submitting a package to
CRAN. Won´t that be a problem?
My package isn´t new, so it will most likely only be checked by CRAN´s
automatic system.
Von: Ivan Krylov
Gesendet: Montag, 20. März 2023 12:55:5
On 20 March 2023 at 12:43, Duncan Murdoch wrote:
| It appears that you have some uses of .Call() where you are passing a
| character variable as the first argument, instead of registering the
| entry point and passing the variable containing the registration
| information.
Correct. And to mak
I found three such calls in a quick search. The first is here:
https://github.com/gdkrmr/coRanking/blob/3656bc0cd3032a650be8c8783414a1e62e419437/R/coranking_internals.R#L20
Duncan Murdoch
On 20/03/2023 12:43 p.m., Duncan Murdoch wrote:
It appears that you have some uses of .Call() where you a
It appears that you have some uses of .Call() where you are passing a
character variable as the first argument, instead of registering the
entry point and passing the variable containing the registration
information.
From your second link, it looks like Rcpp has some special way to
handle ent
I am the maintainer of coRanking and got a message about an error, the
error can be found here [1]. I can reproduce the error on my own machine
with the latest R-devel but don't quite understand what the error means
and how I can fix it. A search leads to an issue in Rcpp [2] where the
charac
В Mon, 20 Mar 2023 08:38:41 +
"Ruff, Sergej" пишет:
> When Limma is üre-installed, I get the following Note:
>
>
> "Package suggested but not available for checking: 'limma'".
>
>
> Seems like the functions isnt installing limma.
>
> Is there something I am missing?
No, this is exactly
I implemented a function to check if limma is available as suggested by Berry
and Tiago.
It works fine when limma is pre-installed.
When Limma is not pre-installed, I get the following Note:
"Package suggested but not available for checking: 'limma'".
Seems like the functions isn't installing l
I implemented Berrys function.
I works fine when limma is pre-installed.
When Limma is üre-installed, I get the following Note:
"Package suggested but not available for checking: 'limma'".
Seems like the functions isnt installing limma.
Is there something I am missing? I added BiocManager a
11 matches
Mail list logo