Re: [R-pkg-devel] DLL vctrs not found in winbuilder test

2021-02-18 Thread Uwe Ligges
On 18.02.2021 22:16, Daeyoung Lim wrote: Hello, I'm testing my package on winbuilder (devel) but somehow it's firing this error message even though my package doesn't use vctrs package. I see that vctrs is suggested by rmarkdown which is included as suggested in my package (metapack) for vign

Re: [R-pkg-devel] How to manage using different packages if available (suggests - imports)

2021-02-18 Thread Knut Krueger
Am 18.02.21 um 16:52 schrieb Duncan Murdoch: you can suppress them using by having environment variable _R_CHECK_FORCE_SUGGESTS_ set to "FALSE".  If you are worried about a CRAN submission, explain to them in your submission message why they can't have all your suggested packages. Yes this i

[R-pkg-devel] DLL vctrs not found in winbuilder test

2021-02-18 Thread Daeyoung Lim
Hello, I'm testing my package on winbuilder (devel) but somehow it's firing this error message even though my package doesn't use vctrs package. I see that vctrs is suggested by rmarkdown which is included as suggested in my package (metapack) for vignette. I didn't have this issue until yesterday

[R-pkg-devel] How to manage using different packages if available (suggests - imports)

2021-02-18 Thread Knut Krueger
The following problem: there are three packages foo1, foo2 and foo3 to use with the update of a package. The availability depends on the configuration of the host system. f.e java version If I write in the Description ... Suggests: foo1, foo2, foo3 inside of functions if have: functio

Re: [R-pkg-devel] How to R CMD build / check using LTO

2021-02-18 Thread Bill Dunlap
Hi Paul, I think that changing the Fortran logicals to integers is the easiest way to fix this up. In the old days (1990's and maybe later), there were Fortran compilers that did not map .TRUE. to 1 and .FALSE. to 0, but I suspect that R's .Fortran does not cater to them. I avoid Fortran logical

Re: [R-pkg-devel] How to manage using different packages if available (suggests - imports)

2021-02-18 Thread Duncan Murdoch
I don't see your tests for the presence of the package you're using, but if you have those set up properly, the messages you get about some of your suggested packages not being available aren't going to matter, and you can suppress them using by having environment variable _R_CHECK_FORCE_SUGGES

Re: [R-pkg-devel] FW: [CRAN-pretest-archived] CRAN submission RIBMDB 1.0.0

2021-02-18 Thread Ivan Krylov
On Thu, 18 Feb 2021 02:37:22 + Binit Kumar wrote: > 1. Windows: As I can see in the logs of the machine: > > platform = windows , arch = x64 , R_Version = R Under development > (unstable) (2021-02-16 r80015) We might need the help of someone else more knowledgeable of Windows package

Re: [R-pkg-devel] Cannot reproduce CRAN error (Solaris i386)

2021-02-18 Thread Gábor Csárdi
Actually, I can reproduce it if I use the Oracle Studio compilers. You can also reproduce it on R-hub like this: rhub::check("metapack_0.1.0.tar.gz", platform = "solaris-x86-patched-ods") I suggest you fix the valgrind issues first, because they might be causing this crash as well. You can also

Re: [R-pkg-devel] Cannot reproduce CRAN error (Solaris i386)

2021-02-18 Thread Gábor Csárdi
FWIW this code does not give me any warnings or errors on Solaris and R 4.0.4 and the current CRAN version of metapack. Gabor On Thu, Feb 18, 2021 at 1:54 AM Daeyoung Lim wrote: > > Hello, > > I have a package on CRAN called 'metapack' and received a message from > Professor Ripley that the erro