Re: [R-pkg-devel] Encoding problem

2017-01-30 Thread Thierry Onkelinx
Dear David, Have you tried removing the exclamation mark in %!\VignetteEncoding{UTF-8}? I think it should be %\VignetteEncoding{UTF-8} Best regards, ir. Thierry Onkelinx Instituut voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team Biome

[R-pkg-devel] Description Meta Information Note

2017-01-30 Thread Cathy Lee Gierke
I'm getting a Note that I don't understandand I think it may be the cause of other errors later I have copied all of the output up to the error for context. The error line is at the end. It seems to say that I have not done a Build before doing the Check, but I did x-134-84-0-217:~

Re: [R-pkg-devel] Description Meta Information Note

2017-01-30 Thread Brian G. Peterson
On Mon, 2017-01-30 at 09:45 -0600, Cathy Lee Gierke wrote: >  building ‘CATkit_2.06.tar.gz’ R CMD build creates a tarball > x-134-84-0-217:CATkit user$ *R CMD check CATkit* but you are checknig the directory, not the tarball. do R CMD check CATkit_2.06.tar.gz instead. Regards, Brian _

[R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Cathy Lee Gierke
Yes, that seemed to get rid of the NOTEbut it doesn't seem to make much difference other than that. i.e., it seems to process the same using CATkit vs CATkit_2.06.tar.gz! Here is the main error that I am getting. I just upgraded to the latest R version, fyi. Everything was fine, a few minor

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Dirk Eddelbuettel
On 30 January 2017 at 10:39, Cathy Lee Gierke wrote: | Everything was fine, a few minor warnings...now this. Description and | namespace are proper. These pkgs should all be part of the R base, aren't | they? Anyone know why I should get these errors? Thanks! Just read what it says and do that

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Brian G. Peterson
The error you reference below is pretty clear, I think. You need to add imports for all the functions you're using from other packages.   See: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Speci fying-imports-and-exports Regards, Brian On Mon, 2017-01-30 at 10:39 -0600, Cathy Lee G

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Cathy Lee Gierke
That is the obvious solution, but it doesn't seem correct: I have pdf included in the description, and namespace files, yet it is being called out. Additionally, aren't most of these pkgs in the packages included by default? And up until yesterday, I didn't have any of these problems. I've been

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Brian G. Peterson
See the link in my email below.  It says: "Packages implicitly import the base namespace. Variables exported from other packages with namespaces need to be imported explicitly using the directives import and importFrom." Regards, Brian On Mon, 2017-01-30 at 11:04 -0600, Cathy Lee Gierke wrote: >

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Kasper Daniel Hansen
On Mon, Jan 30, 2017 at 12:04 PM, Cathy Lee Gierke wrote: > That is the obvious solution, but it doesn't seem correct: I have pdf > included in the description, and namespace files, yet it is being called > out. Additionally, aren't most of these pkgs in the packages included by > default? > N

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Kevin Ushey
Most importantly, this _is_ a recent-ish change in R CMD check. Previously, R CMD check did not warn about missing imports from 'base' R packages (that is, R packages distributed with R, having priority 'base'); now it correctly does. While packages with priority 'base' are loaded by default in mos

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Duncan Murdoch
On 30/01/2017 12:04 PM, Cathy Lee Gierke wrote: That is the obvious solution, but it doesn't seem correct: I have pdf included in the description, and namespace files, yet it is being called out. Additionally, aren't most of these pkgs in the packages included by default? And up until yesterda

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Cathy Lee Gierke
Thank you. That will be why I didn't see them previously. Helps my sanity ;-) Sent from my iPhone > On Jan 30, 2017, at 8:58 PM, Kevin Ushey wrote: > > Most importantly, this _is_ a recent-ish change in R CMD check. Previously, R > CMD check did not warn about missing imports from 'base' R pac

Re: [R-pkg-devel] Encoding problem

2017-01-30 Thread David Scott
Thanks Thierry, that indeed was the problem. I am not sure who to advise to correct the documentation in Writing R Extensions though because I was following the instructions there: "... the encoding may be declared using a comment like %!\VignetteEncoding{UTF-8} If the encoding is UTF-8, this

Re: [R-pkg-devel] no visible global function definition for ‘par’

2017-01-30 Thread Dirk Eddelbuettel
On 30 January 2017 at 09:58, Kevin Ushey wrote: | The correct thing to do is indeed import any functions from any R packages | you use, base or otherwise. The simplest fix, if you don't want to | selectively import such a large range of functions, is to simply add e.g. | | import(utils) |