This is currently under inspection by the CRAN team. Apparently
img.shields.io have changed the cypher settings and pandoc fails with
the new settings. We may have to disable *.md processing for some time.
Best,
Uwe Ligges
On 25.05.2017 20:59, Emmanuel Blondel wrote:
Dear all,
I've just su
I have found Travis CI, which can check your package every time you push to
GitHub useful - you can set it up to build and check your package against the
current version of R and R-devel. See
http://juliasilge.com/blog/Beginners-Guide-to-Travis/ and
https://docs.travis-ci.com/user/langu
Dear all,
I've just submitted a new package named geometa, for which i received the
message below. Indeed i had sent in my submission some question mark about the
warning i obtain during R CMD check:
In case of R release and R devel, I got the following warning:
Conversion of 'README.md' faile
I also recommend reinstalling and making sure it works. I also
recommend making sure you actually run roxygen either via roxygenize()
or devtools::document() to make sure that your changes get written to
the NAMESPACE file. Your NAMESPACE on your github is a few months old
still.
-Dason Kurkiewic
On 25/05/2017 4:55 PM, Maity, Arnab K wrote:
?Thank you all for your kind replies. I made the necessary changes. Now in
order to make the changes available on CRAN, do I resubmit the package after
changing the version?
Yes, though I'd try installing the new one from the tarball on a
differen
?Thank you all for your kind replies. I made the necessary changes. Now in
order to make the changes available on CRAN, do I resubmit the package after
changing the version?
Arnab Kumar Maity
Department of Statistics
Texas A&M University
3143 TAMU, Room 401A
College Station, TX 77843
aku...@s
If you are using roxygen2 for documentation and want to export a function add
a line with
#' @export
to the .R file as part of the function documentation. Running
devtools::document() should then update the NAMESPACE
See http://r-pkgs.had.co.nz/namespace.html
On May 25, 2017, at 8:55 AM,
On 24/05/2017 11:59 PM, Maity, Arnab K wrote:
Dear R Package developers,
Apologies for cross posting.
I posted the following message on R help forum and got advised to post here.
I created a package on github. It is located at "arnabkrmaity/brlrmr". Then I
submitted this on CRAN and it is
Hi Arnab,
It will be something like this:
importFrom("utils", "read.table")
export(
fil
)
S3method(print,fil)
You will probably have to import some functions from the packages that
come with R. Then you list all the functions you want to export,
separated by commas. Finally you list any methods
Dear R Package developers,
Apologies for cross posting.
I posted the following message on R help forum and got advised to post here.
I created a package on github. It is located at "arnabkrmaity/brlrmr". Then I
submitted this on CRAN and it is now available on CRAN.
When I install this pack
Apologies for this double posting; I asked this on Stackoverflow, but
hasn't received much attention.
I have quite successfully implemented an R package with some Fortran
functions. Some of these functions needs to write to files, so naturally I
use the Fortran statement `write(unit, fmt) var`.
W
I don't think I can offer anything beyond the Valgrind FAQ at this point. I
kind of suspect that the other trace -- pointing to where the offending piece
of memory was allocated --would provide the better clue about the source of the
problem.
-pd
> On 25 May 2017, at 04:47 , Merlise Clyde, Ph
12 matches
Mail list logo
