similar to: Submitting an updated package version to CRAN (Warning: non-ASCII characters)

On 21/05/2016 21:25, Luck Buttered wrote: > Dear all: > > I am updating the version of an R package I submitted last year on CRAN and > came across two questions that I would be grateful to seek any input about: > > 1) In the updated version of the package, I am adding a second example > dataset. This example dataset is a subset of a public database that > contains

Hello: I recently submitted a package to R using devtools:release(). I received no errors, warnings, or notes in R CMD check. However, I received two notes in devtools::release(): 1) checking CRAN incoming feasibility ... NOTE 2) checking package dependencies ... NOTE No repository set, so cyclic dependency check skipped After I submitted the package, I was told to fix two things, of which

Hello everybody, by the way, speaking about the r-cran-rcurl package in Ubuntu, the versions in trusty and vivid are linked by error to the "NSS" flavour of libcurl3 instead of the "OpenSSL flavour", which cause at least problems when using the CRAN devtools package. A bit more details are available in the Debian bug tracking system (https://bugs.debian.org/786473). I am not

Hi, I'm trying to submit my first package which depends on doParallel: Depends: R (>= 3.0), igraph, doParallel Running hadley devtools: devtools::check() and devtools::release() result in no problem (no ERROR nor NOTE on Linux, Mac and Windows). However, when in use the devtools::build_win() command, it results in the following note: * checking R code for possible problems ... NOTE

On 05/03/2015 6:16 PM, Brian G. Peterson wrote: > On Thu, 2015-03-05 at 18:03 -0500, Etienne Lord wrote: >> Hi, >> >> I'm trying to submit my first package which depends on doParallel: >> >> Depends: R (>= 3.0), igraph, doParallel > > add foreach to your Depends. That should resolve the error you're > seeing. Please don't do that. Use

Thanks Dirk. I'm looking at it now. At first glance your documentation brings up a good limitation of simply telling users to type "devtools::install_github()". Namely, what happens when the census bureau updates their shapefiles, and I subsequently decide to update the package? Or if I discover an error in the package and decide to update it? The choroplethr package could have a

I'm putting together an R package. I would like to show example code in the vignette, where example data files (included in the package) are used to generate an (example) output file. I read about using example data in Hadley Wickham's post ( http://r-pkgs.had.co.nz/data.html), and believe I should keep my example data as raw data, as it must be parsed to generate the output. So, I

I recently tried to submit a package to CRAN using the release function in the devtools package and got the response: > The policies asked you to use the webform: do so in future. I think that the relevant line in the policies are: > When submitting a package to CRAN you should use the submission form at > http://CRAN.R-project.org/submit.html (and not send an email). You will be sent

The CRAN submission process seems in need of a massive overhaul. Why has this process not been automated yet? ? Patrick Perry Assistant Professor NYU Stern School of Business

Hi, In support of reproducible research at my Institute, I seek an approach to re-creating the R environments in which an analysis has been conducted. By which I mean, the exact version of R and the exact version of all packages used in a particular R session. I am seeking comments/criticism of this as a goal, and of the following outline of an approach: === When all the steps to an workflow

Dear R Core and CRAN Team, I received a warning that the rdyncall package [1] will be archived and removed from the main CRAN distribution at 7th of September if I can not get rid of .Internal calls. > From: ripley at stats.ox.ac.uk (Prof Brian Ripley) > Subject: Use of .Internal in CRAN package rdyncall > Date: August 14, 2012 11:09:06 AM GMT+02:00 > To: dadler at uni-goettingen.de

I have just written a package called choroplethrZip <https://github.com/arilamstein/choroplethrZip> which contains a shapefile and metadata on US Zip codes. It is currently hosted on github, has a tagged version number (v1.0.0) and passes R CMD check as verified by Travis. My plan is to use this in the next version of my package choroplethr <https://github.com/arilamstein/choroplethr>.

I'm continuing this here in llvm-dev since the thread was started here, but, in hindsight, it may have been better in cfe-dev, because the problem seems to be related to clang. I turned on "verbose" mode in make (VERBOSE=1 TOOL_VERBOSE=1) and found that it is clang, not gcc, that is being used at this point in the make. Based on the command issued (particularly with the --sysroot

Just in case someone is having similar problems and/or following this thread, here's my final "solution" (at least, for now). In my bash build script, prior to configure, I set the C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to empty strings, and then set some other environment variables instead: export C_INCLUDE_PATH= export CPLUS_INCLUDE_PATH=

Hi all, I'm trying to understand how the search path and namespaces interact. For example, take the devtools package which suggests the testthat package. Here's what the search path looks like after I load each of those packages: > library(devtools) > search() [1] ".GlobalEnv" "package:devtools" "package:stats" [4]

I'm attempting to build a native build of clang from the 3.2 source distribution tarballs, but I ran into this build error that's got me really puzzled. My platform is Linux - 32-bit Ubuntu (12.04) running on a PC. Here's the (abbreviated) output from make: *************************************** ... make[3]: Entering directory

This question was posed on SO : https://stackoverflow.com/questions/58118495/passing-extra-argumenets-to-devtoolsbuild but there has been no useful reply. Something seems to have changed in the |devtools|package, so that the following commands, that used to run now give an error I can't decipher: |>Sys.setenv(R_GSCMD="C:/Program

Hello. I'm trying to adapt the package ?hexbin? to suit my needs. This is the first time I do this. I've read a bit through Hadley's ?R packages?, but now I'm pretty lost (from a workflow point of view). I am using RStudio and Hadley's devtools. So I forked the repo I want to adapt: https://github.com/grssnbchr/hexbin and cloned it using RStudio (I created a new project).

Hello. I'm trying to adapt the package ?hexbin? to suit my needs. This is the first time I do this. I've read a bit through Hadley's ?R packages?, but now I'm pretty lost (from a workflow point of view). I am using RStudio and Hadley's devtools. So I forked the repo I want to adapt: https://github.com/grssnbchr/hexbin and cloned it using RStudio (I created a new project).

Dear Community, I have an Rmarkdown vignette with optional child documents. Since all markdown files in the vingette folder are build when executing R CMD build I did place the child documents in /inst/ParametrizedReportChid/ so they are excluded from the build. I do reference them from the markdown file in the vignette folder by: ```{r referencingChildDocument} child_docs <-