Re: [R-pkg-devel] CRAN error with current version

[Sebastian Meyer]

The reason that your package does not pass the incoming checks is

> * checking CRAN incoming feasibility ... NOTE
> Maintainer: ‘Cristian Quiroz-Moreno ’
> 
> Uses the superseded package: ‘snow’

You would need to explain to CRAN why you need to use "snow" rather than
base R's "parallel" package. But I guess you should actually replace
"snow" by "parallel" in your package.

Cheers,

Sebastian


Am 24.03.20 um 17:50 schrieb Daniel Quiroz Moreno:
> Dear community,
> 
> I have an issue with the current version of my package. The current CRAN
> version is 1.1.0 when it was submitted, I had no warnings. These days I
> fixed an issue and I would like to submit a minor version 1.1-1. I have no
> errors or warnings in the local check.
> 
> Even though, when I submit to CRAN, it does not pass the automatic check.
> The mail does not show any error or warning for the newest version (1.1-1)
> but it points to a warning for the current version (1.1.0). I have
> corrected this warning in the newest version but it does not pass the CRAN
> check.
> 
> Please, can you help me how to fix this? I mean, how to avoid the current
> CRAN version warnings, instead of the newest version?
> 
> If you would like to see the logs, I paste the mail.
> 
> 
> package RGCxGC_1.1-1.tar.gz does not pass the incoming checks
> automatically, please see the following pre-tests:
> Windows: <
> https://win-builder.r-project.org/incoming_pretest/RGCxGC_1.1-1_20200320_181616/Windows/00check.log
>>
> Status: 2 NOTEs
> Debian: <
> https://win-builder.r-project.org/incoming_pretest/RGCxGC_1.1-1_20200320_181616/Debian/00check.log
>>
> Status: 1 NOTE
> 
> Last released version's CRAN status: WARN: 2, NOTE: 6, OK: 5
> See: 
> 
> Last released version's additional issues:
>   donttest 
> 
> CRAN Web: 
> 
> Please fix all problems and resubmit a fixed version via the webform.
> If you are not sure how to fix the problems shown, please ask for help on
> the R-package-devel mailing list:
> 
> If you are fairly certain the rejection is a false positive, please
> reply-all to this message and explain.
> 
> More details are given in the directory:
> <
> https://win-builder.r-project.org/incoming_pretest/RGCxGC_1.1-1_20200320_181616/
>>
> The files will be removed after roughly 7 days.
> 
> No strong reverse dependencies to be checked.
>

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

[R-pkg-devel] CRAN error with current version

[Daniel Quiroz Moreno]

Dear community,

I have an issue with the current version of my package. The current CRAN
version is 1.1.0 when it was submitted, I had no warnings. These days I
fixed an issue and I would like to submit a minor version 1.1-1. I have no
errors or warnings in the local check.

Even though, when I submit to CRAN, it does not pass the automatic check.
The mail does not show any error or warning for the newest version (1.1-1)
but it points to a warning for the current version (1.1.0). I have
corrected this warning in the newest version but it does not pass the CRAN
check.

Please, can you help me how to fix this? I mean, how to avoid the current
CRAN version warnings, instead of the newest version?

If you would like to see the logs, I paste the mail.


package RGCxGC_1.1-1.tar.gz does not pass the incoming checks
automatically, please see the following pre-tests:
Windows: <
https://win-builder.r-project.org/incoming_pretest/RGCxGC_1.1-1_20200320_181616/Windows/00check.log
>
Status: 2 NOTEs
Debian: <
https://win-builder.r-project.org/incoming_pretest/RGCxGC_1.1-1_20200320_181616/Debian/00check.log
>
Status: 1 NOTE

Last released version's CRAN status: WARN: 2, NOTE: 6, OK: 5
See: 

Last released version's additional issues:
  donttest 

CRAN Web: 

Please fix all problems and resubmit a fixed version via the webform.
If you are not sure how to fix the problems shown, please ask for help on
the R-package-devel mailing list:

If you are fairly certain the rejection is a false positive, please
reply-all to this message and explain.

More details are given in the directory:
<
https://win-builder.r-project.org/incoming_pretest/RGCxGC_1.1-1_20200320_181616/
>
The files will be removed after roughly 7 days.

No strong reverse dependencies to be checked.

-- 
Gracias por su tiempo.


Estudiante* Ing*. Biotecnología
Universidad *IKIAM*
Tena - Ecuador

[[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Re: [R-pkg-devel] use of getNativeSymbolInfo

[Tomas Kalibera]

On 2/9/20 5:14 PM, Benjamin Tyner wrote:

Hello,

Using package nlme as an example, where there is a registered routine 
fit_gnls:


> library(nlme)
> getDLLRegisteredRoutines("nlme")$.C$fit_gnls
$name
[1] "fit_gnls"

$address

attr(,"class")
[1] "RegisteredNativeSymbol"

$dll
DLL name: nlme
Filename: /home/btyner/R-77784/lib/R/library/nlme/libs/nlme.so
Dynamic lookup: FALSE

$numParameters
[1] 10

attr(,"class")
[1] "CRoutine" "NativeSymbolInfo"

However when I tried this,

> getNativeSymbolInfo(name = "fit_gnls", PACKAGE = "nlme")

it says:

Error in FUN(X[[i]], ...) : no such symbol fit_gnls in package nlme

so I am wondering what I'm doing wrong...


This is because it is not allowed by the package: nlme calls 
R_forceSymbols(,TRUE) in its init function.


Tomas



Regards,
Ben

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel