similar to: Problem with Rd2.tex tduring compilation

Hi and thanks for the prompt reply. I cannot say I understood or know what to do. Can you please tell me which is this mailing list? ???? 2:15 ?.?. ???????, 5 ??????? 2018, ?/? Michael Dewey <lists at dewey.myzen.co.uk> ??????: The error is that one of your documentation files is failing. Try compiling each one separately with R CMD Rd2pdf yourfilenamehere.Rd and see what

https://stat.ethz.ch/mailman/listinfo/r-package-devel On 05/03/2018 13:46, michael tsagris wrote: > Hi and thanks for the prompt reply. I cannot say I understood or know > what to do. > Can you please tell me which is this mailing list? > > > > ???? 2:15 ?.?. ???????, 5 ??????? 2018, ?/? Michael Dewey > <lists at dewey.myzen.co.uk> ??????: > > > The

The error is that one of your documentation files is failing. Try compiling each one separately with R CMD Rd2pdf yourfilenamehere.Rd and see what happens. There is a list especially for package developers which might be better in future. Michael On 05/03/2018 10:51, michael tsagris via R-help wrote: > Hello, I am receiving this message when uploading my R package to rdevel. >

Dear List, I ran into the following two problems while using the package 'roxygen': QUESTION 1 I split the relevant R-Code for my package into the following scripts: classes.R (S4), functions.R ('standard' functions), generics.R (S4), methods.R (S4). Function package.skeleton() generates Rd-files for all class defs, function defs etc. in dir 'pkg/man'. So far, so good.

Hi all, I wish to push a new version of a package (heatmaply). I sent it to winbuild with no issues but after submitting it to CRAN I got an update that it breaks on Debian, see: package heatmaply_0.15.0.tar.gz does not pass the incoming checks automatically, please see the following pre-tests: Windows: <https://win-builder.r-project.org/incoming_pretest/

Tom, On 30 May 2018 at 11:34, Tom Callaway wrote: | On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: | > I noticed it with a local, not-public package -- but it appears to apply with | > any source package. I replicated with pkgKitten straight off CRAN and after | > checking that it has a six page manual there. | | I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I

Hello,?I?am experiencing some difficult time with my R package. Every time I compilei it a hidden file, desktop.ini, is?being created. I am using C++ behind, linkking to Rcpp. The file is generated even when I compile it with?Linux, and in many different computers. Does anybody have any advice or ideas? [[alternative HTML version deleted]]

On 23/05/2020 07:38, Simon Urbanek wrote: > Adrian, > > newer compilers are better at finding bugs - you may want to read the full trace of the error, it tells you that you likely have a memory overflow when using strncpy() in your package. You should check whether it is right. Unfortunately we can?t help you more specifically, because I don't see any link to what you submitted so

On 29 May 2018 at 16:37, R P Herrold wrote: | On Tue, 29 May 2018, Dirk Eddelbuettel wrote: | | > On a CentOS 7 machine, I am at a loss with respect to an inability to run a | > full R CMD check as anything involving tex files ends in tears. | | Hi, Dirk | | Have fun at the upcoming conference at UIC | | I seem to have 56 font packages installed under CentOS 7 | locally, but then I work

Make a reproducible example [1][2][3], because it doesn't happen for me. Then post your example at [4] or [5], because this is the wrong list for this question. You may find that the act of browsing the directory using a GUI is what creates that file rather than the compilation itself. [1] http://stackoverflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example [2]

Dear developers, Upon CRAN submission I have bumped into "future file timestamps" warning that I can't solve. I have updated the package as usual, and all checks go through in my system. CRAN reports the following warning however. * checking for future file timestanps ... WARNING Files with future time stamps: DESCRIPTION NAMESPACE README.md The build log is at

When I run R CMD check on the survival package I invariably get a note: ... * checking for file ?survival/DESCRIPTION? ... OK * this is package ?survival? version ?3.2-6? * checking CRAN incoming feasibility ... NOTE Maintainer: ?Terry M Therneau <therneau.terry at mayo.edu>? ... This is sufficient for the auto-check process to return the following failure message: Dear maintainer,

On the local machine the command R11 CMD Rd2pdf survfit.Rd works fine. R12 CMD Rd2pdf survfit.Rd fails with the message below. Converting Rd files to LaTeX ... survfit.Rd Creating pdf output from LaTeX ... Error in texi2dvi("Rd2.tex", pdf = (out_ext == "pdf"), quiet = FALSE, : Running 'texi2dvi' on 'Rd2.tex' failed. Messages: sh: texi2dvi: command not

Thank you Michael, Curves for each level of the factor sounds very interesting, Do you have a suggestion how to plot them? Thank you! Alina *Alina Vodonos Zilberg* On Thu, Aug 10, 2017 at 7:39 AM, Michael Dewey <lists at dewey.myzen.co.uk> wrote: > Dear Alina > > If I understand you correctly you cannot just have a single predicted > curve but one for each level of your

Hi, SAS transport files created with the xport engine in SAS can be read using read.xport. However, the xport engine only works with SAS version 6, and consequently long variable names are not allowed... Can anyone tell me how to get SAS data (ver 8) into R (easily)? Thanks in advance S?ren H?jsgaard sorenh at agrsci.dk http://www.jbs.agrsci.dk/~sorenh

On a CentOS 7 machine, I am at a loss with respect to an inability to run a full R CMD check as anything involving tex files ends in tears. We followed the README at CRAN and installed a large number of tex-live packages on this machine. But when a manual is created, we end up with what follows below. Here, I chopped some of the error messages, the key seems to be 'Insufficient extension

R Community, I often am in need of viewing the reference manuals of packages and do not have Internet access. I have used the code: path <- find.package('tm') system(paste(shQuote(file.path(R.home("bin"), "R")),"CMD", "Rd2pdf",shQuote(path))) someone kindly provided from this help list to generate the manuals from the latex files. This

Dear Prof.Thank you for your kind response. I have only used: install.packages("tidyverse") install.packages("meta") install.packages("metafor") library(tidyverse) library(meta) library(metafor)and then,forest.meta(hidemeta, layout="RevMan5", xlab="Proportion", comb.r=T, comb.f=F, xlim = c(0,1), fontsize=10, digits=3)Unfortunately I am not

> The command Rd2pdf was rather useful for opening a package's manual > when you don't have access to the Internet (by using latex to pdf > conversion). However the way the function seems to operate changed at > version 2.14 of R. The noted changes listed on CRAN for this function > are as follows (which doesn't seem like it would affect my usage as > below): >

Note though that this has been put on hold on stats.stackexchange.com as off-topic. On 23/06/2017 19:33, Bert Gunter wrote: > Probably the wrong list. R-help is concerned with R programming, not > statistics methodology questions, although the intersection can be > nonempty. > > I suggest you post on stats.stackexchange.com instead, which *is* > concerned with statistics