[R] faisalconjoint

[Berend Hasselman]

> On 18-02-2015, at 05:02, BRC <brc.khi at gmail.com> wrote:
> 
> I am developing a r package faisalconjoint, when i run R CMD check
> --as-cran faisalconjoint, got the following notes.
> 
> * using log directory
> 'D:/r-test-packages/faisalconjoint/faisalconjoint.Rcheck'
> * using R version 3.1.2 (2014-10-31)
> * using platform: i386-w64-mingw32 (32-bit)
> * using session charset: ISO8859-1
> * checking for file 'faisalconjoint/DESCRIPTION' ... OK
> * checking extension type ... Package
> * this is package 'faisalconjoint' version '1.15'
> * checking CRAN incoming feasibility ... NOTE
> Maintainer: 'Faisal Afzal Siddiqui <brc.khi at gmail.com>'
> New submission
> Package was archived on CRAN
> * checking package namespace information ... OK
> * checking package dependencies ... NOTE
>  No repository set, so cyclic dependency check skipped
> * checking if this is a source package ... OK
> * checking if there is a namespace ... OK
> * checking for executable files ... OK
> * checking for hidden files and directories ... OK
> * checking for portable file names ... OK
> * checking whether package 'faisalconjoint' can be installed ... OK
> * checking installed package size ... OK
> * checking package directory ... OK
> * checking DESCRIPTION meta-information ... OK
> * checking top-level files ... NOTE
> Non-standard file/directory found at top level:
>  'faisalconjoint-manual.pdf'
> * checking for left-over files ... OK
> * checking index information ... OK
> * checking package subdirectories ... OK
> * checking R files for non-ASCII characters ... OK
> * checking R files for syntax errors ... OK
> * checking whether the package can be loaded ... OK
> * checking whether the package can be loaded with stated dependencies ... OK
> * checking whether the package can be unloaded cleanly ... OK
> * checking whether the namespace can be loaded with stated dependencies ...
> OK
> * checking whether the namespace can be unloaded cleanly ... OK
> * checking loading without being on the library search path ... OK
> * checking dependencies in R code ... OK
> * checking S3 generic/method consistency ... OK
> * checking replacement functions ... OK
> * checking foreign function calls ... OK
> * checking R code for possible problems ... OK
> * checking Rd files ... OK
> * checking Rd metadata ... OK
> * checking Rd line widths ... OK
> * checking Rd cross-references ... OK
> * checking for missing documentation entries ... OK
> * checking for code/documentation mismatches ... OK
> * checking Rd \usage sections ... OK
> * checking Rd contents ... OK
> * checking for unstated dependencies in examples ... OK
> * checking contents of 'data' directory ... OK
> * checking data for non-ASCII characters ... OK
> * checking data for ASCII and uncompressed saves ... OK
> * checking examples ... OK
> * checking PDF version of manual ... OK
> * DONE
> NOTE: There were 3 notes.
> 
> 1. No repository set, so cyclic dependency check skipped

Google for :  “No repository set, so cyclic dependency check skipped“
and you will see this:

http://stackoverflow.com/questions/23164929/note-in-r-cran-check-no-repository-set-so-cyclic-dependency-check-skipped

> 2. Non-standard file/directory found at top level:
> 'faisalconjoint-manual.pdf’
> 

Obvious: remove file/directory or clean source directory perhaps?
And if you need file/directory then read the "Writing R Extensions” manual.

> please advise how I can remove these notes to upload the package.
> 

AFAIK you can ignore the note about the maintainer.

Berend

> I will be very thankful to you.
> 
> 	[[alternative HTML version deleted]]
> 
> ______________________________________________
> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.