[R-pkg-devel] What checks are required before uploading a package to CRAN?
My R package checks on my windows computer with no errors, warnings or notes. Next I used the win-builder upload page to check the package. I uploaded the tar.gz file on R-release. I read the 00check.log file and the only Note stated was that I was the developer. I understood that I needed to upload the file to both R-release and R-devel before I could upload it to the cran.r-project.org/submit.html page. I tried to upload the file to the R-devel, but I got the following message. ERROR: Access to the path 'C:\Inetpub\ftproot\R-devel\daewr_1.2-9.tar.gz' is denied. (perhaps you uploaded already and the file has not been processed yet?) It has been 4 days since I uploaded the file to R-release, and I get automatic emails every other day from Uwe Ligges telling me my package has been checked and built. What checks are required before uploading the package tar.gz file to the cran.r-project.org/submit.html page? John Lawson __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] R Package AQLSchemes
I published the R Package AQLSChemes on CRAN in May 2022. The book "An Introduction to Acceptance Sampling and SPC with R" was published after that, and included examples of the use of AQLSChemes package. Since then, I have retired and was not aware that the AQLSChemes package was removed from CRAN. When I try to run code from the book that requires the AQLSChemes package, I get the message that the package doesn't exist. My question is, How can I find out why the package AQLSChemes was removed from CRAN, and what do I need to do to restore it to CRAN? Sincerely John Lawson lawsonjsl7...@gmail.com [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] WARNING Files in the 'vignettes' directory but no files in 'inst/doc':
My AQLSchemes package has a pdf vignette created with Rmarkdown. I tried to add a vignette to my daewr package in exactly the same way, by setting the Description file like the AQLSchemes package Description file with the statements Suggests: R.rsp VignetteBuilder: R.rsp. In both packages I put the vignette .Rmd file and output .pdf file in the vignettes directory, and the inst directory is empty When I run the check on the AQLSchemes on my local machine, I see the messages - preparing 'AQLSchemes': v checking DESCRIPTION meta-information ... - installing the package to build vignettes ... > checking sizes of PDF files under 'inst/doc' ... NOTE Unable to find GhostScript executable to run checks on size reduction 0 errors v | 0 warnings v | 1 note x and the package builds correctly with the vignette However, when I run the check on daewr I see the messages - preparing 'daewr': (665ms) v checking DESCRIPTION meta-information ... - checking for LF line-endings in source and make files and shell scripts (894ms) - checking for empty or unneeded directories Removed empty directory 'daewr/inst' ... > checking files in 'vignettes' ... WARNING Files in the 'vignettes' directory but no files in 'inst/doc': 'ModelRobust.Rmd', 'ModelRobust.pdf' 0 errors v | 1 warning x | 0 notes v Error: R CMD check found WARNINGs Execution halted The two packages are set up in the same way. Any insight as to why one builds with the vignette but the other does not, would be greatly appreciated. Sincerely John Lawson [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] manual inspection of new packages
Ok, thanks.
On Thu, Apr 9, 2020 at 1:46 PM Duncan Murdoch
wrote:
> On 09/04/2020 3:28 p.m., John Lawson wrote:
> > I submitted the Package AQLSchemes on Dec 9, 2019. I corrected the errors
> > noted in the manual inspection and resubmitted it on Jan 9. I got the
> > message that it passed the automatic checks and was awaiting manual
> > inspection. I have not heard anything since. Do I need to resubmitt the
> > package? Or how can I find out if this package is still in the queue for
> > manual inspection?
> >
>
> As the CRAN policy document says under Submission, you can see the queue
> by looking at ftp://cran.r-project.org/incoming/. The foghorn package
> makes this really easy: you run foghorn::cran_incoming("AQLSchemes") to
> see where your package is sitting. It doesn't appear to be there at all.
>
> Next time, I'd follow up if you go a week without hearing a reply;
> waiting 3 months seems a bit long.
>
> Duncan Murdoch
>
[[alternative HTML version deleted]]
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] manual inspection of new packages
I submitted the Package AQLSchemes on Dec 9, 2019. I corrected the errors noted in the manual inspection and resubmitted it on Jan 9. I got the message that it passed the automatic checks and was awaiting manual inspection. I have not heard anything since. Do I need to resubmitt the package? Or how can I find out if this package is still in the queue for manual inspection? Thank you John Lawson [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] package daewr does not pass incoming checks automatically
The package daewr contains the data sets and functions shown in the book "Design and Analysis of Experiments with R" published by CRC press. It has been on CRAN since the book was first published in 2015. Recently I included a new function, but have not been able to include the modified package on CRAN. I get the message from Debian: * DONE Status: 1 WARNING, 1 NOTE Current CRAN status: WARN: 1, OK: 12 See: <https://CRAN.R-project.org/web/checks/check_results_daewr.html> Version: 1.1-8 Check: package dependencies, Result: WARNING Requires orphaned package: ‘BsMD’ See: <https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/daewr-00check.html> I do not get this warning from the Windows: Although the package BsMD is orphaned, it is still available on CRAN and all examples in the book that use functions in daewr that call functions from BsMD work as they always have. The new function I have added does not require BsMD. Is there any way I can upload my modified package to CRAN so that the new function is available? Any help would be greatly appreciated. John Lawson [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Help on Windows CRAN Check
I see this error on windows CRAN Check
--- failure: the condition has length > 1 ---
--- srcref ---
:
--- package (from environment) ---
daewr
--- call from context ---
ihstep(y, x, m, c)
--- call from argument ---
if (t1 == "I" & t2 == "(") {
iquad = TRUE
}
t1 and t2 are both characters of length 1, therefore I assume they are
scalars. The check on my own computer or R forge gives no errors. When
I change if(t1 == "I" & t2 =="(") {iquad=TRUE} to
if(t1 == "I" && t2 =="(") {iquad=TRUE}
I get the following error when I try the check on my own computer
--- FAILURE REPORT --
--- failure: length > 1 in coercion to logical ---
--- srcref ---
:
--- package (from environment) ---
daewr
--- call from context ---
ihstep(y, x, m, c)
--- call from argument ---
t1 == "I" && t2 == "("
--- R stacktrace ---
where 1: ihstep(y, x, m, c)
where 2: eval(expr, pf)
where 3: eval(expr, pf)
where 4: withVisible(eval(expr, pf))
where 5: evalVis(expr)
where 6: capture.output(res <- ihstep(y, x, m, c))
where 7: withCallingHandlers(expr, warning = function(w)
invokeRestart("muffleWarning"))
I am not sure what this means. Using one &, I am able to check and
build the package on my computer or R forge but not on CRAN. When
using two && I can't check and build on my own computer. Any advice on
what to do would be greatly appreciated.
John Lawson
[[alternative HTML version deleted]]
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] Help on Windows CRAN Check
I see this error on the CRAN Check report
> ### ** Examples
>
> #Definitive Screening Design
> library(daewr)
> set.seed(1234)
> x <- DefScreen(m=5,c=0)
> colnames(x) <- paste("x",1:5,sep="")
> x$y <- 3*x$x1 + 2*x$x2 + 2*x$x4*x$x5 + x$x3^2 + 2*x$x1^2 + rnorm(nrow(x),0,1)
> (z <- HierAFS(x$y,x[,-6],m=5,c=0,step=4,nm1=FALSE ))
--- FAILURE REPORT --
--- failure: the condition has length > 1 ---
--- srcref ---
:
--- package (from environment) ---
daewr
--- call from context ---
ihstep(y, x, m, c)
--- call from argument ---
if (t1 == "I" & t2 == "(") {
iquad = TRUE
}
--- R stacktrace ---
where 1: ihstep(y, x, m, c)
where 2: eval(expr, pf)
where 3: eval(expr, pf)
where 4: withVisible(eval(expr, pf))
where 5: evalVis(expr)
where 6: capture.output(res <- ihstep(y, x, m, c))
where 7: withCallingHandlers(expr, warning = function(w)
invokeRestart("muffleWarning"))
where 8: suppressWarnings(invisible(capture.output(res <- ihstep(y, x,
m, c
where 9: HierAFS(x$y, x[, -6], m = 5, c = 0, step = 4, nm1 = FALSE)
--- value of length: 3 type: logical ---
[1] FALSE FALSE FALSE
--- function from context ---
function (y, des, m, c)
{
lin <- colnames(des)
values <- c("A", "B", "C", "D", "E", "F", "G", "H", "I",
"J", "K", "L", "M", "N", "O", "P", "Q", "R", "S", "T",
"U", "V", "W", "X", "Y", "Z")
repl <- c("I(A^2)", "I(B^2)", "I(C^2)", "I(D^2)", "I(E^2)",
"I(F^2)", "I(G^2)", "I(H^2)", "I(I^2)", "I(J^2)", "I(K^2)",
"I(L^2)", "I(M^2)", "I(N^2)", "I(O^2)", "I(P^2)", "I(Q^2)",
"I(R^2)", "I(S^2)", "I(T^2)", "I(U^2)", "I(V^2)", "I(W^2)",
"I(X^2)", "I(Y^2)", "I(Z^2)")
repl.tab <- cbind(values, repl)
if (m == 0) {
quad <- character()
}
else {
indx <- rep(0, m)
for (i in 1:m) {
indx[i] <- match(lin[i], repl.tab[, 1], nomatch = 0)
}
quad <- rep("A", m)
for (i in 1:m) {
quad[i] <- lin[i]
}
quad[indx != 0] <- repl.tab[indx, 2]
quad <- paste(quad, collapse = "+")
}
dat <- data.frame(y = y, des)
lm1 <- lm(y ~ (.)^2, data = dat)
mm <- model.matrix(lm1)
fact <- colnames(mm)
fact <- fact[-1]
fact <- paste(fact, collapse = "+")
mod <- paste(c(fact, quad), collapse = "+")
lm2 <- lm(reformulate(termlabels = mod, response = "y"),
data = dat)
mm <- model.matrix(lm2)
mm <- mm[, 2:ncol(mm)]
trm <- firstm(y, mm)
d1 <- data.frame(y = y, mm[, trm])
t1 <- substr(trm, 1, 1)
t2 <- substr(trm, 2, 2)
t3 <- substr(trm, 3, 3)
iquad = FALSE
if (t1 == "I" & t2 == "(") {
iquad = TRUE
}
hmt <- trm
if (t2 == "") {
nms <- names(d1)
nms[2] <- hmt
names(d1) <- nms
}
m1 <- lm(y ~ (.), data = d1)
result <- summary(m1)
print(result)
return(trm)
}
--- function search by body ---
Function ihstep in namespace daewr has this body.
--- END OF FAILURE REPORT --
Fatal error: the condition has length > 1
However on my own computer or on Rforge
I see this:
* checking examples ... OK
* DONE
Status: OK
-- R CMD check results daewr 1.1-9
Duration: 1m 1.8s
0 errors v | 0 warnings v | 0 notes v
R CMD check succeeded
I am not sure what the error is or how to correct it. Any help would
be greatly appreciated,
John Lawson
[[alternative HTML version deleted]]
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
