search for: nosvn

Dear R developers, I recently observed a NOTE on several MaxOS X package checks: sh: line 1: gs: command not found !!! Error: Closing Ghostscript (exit status: 127)! /usr/bin/texi2dvi: thumbpdf exited with bad status, quitting. See for details: http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/simecol-00check.html or http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/fxregime-00check.html Does anybody know what's wrong here? Thanks a lot Thomas Petzoldt -- Thomas Petzoldt Technische Universitaet Dresden Institut fuer Hydrobiologie...

Hello, The package cts on CRAN generated a note on some systems. For instance: checking compiled code ... NOTE File ?/home/ripley/R/Lib32/cts/libs/cts.so?: Found ?abort?, possibly from ?abort? (C) which can be found from the link http://www.r-project.org/nosvn/R.check/r-patched-solaris-sparc/cts-00check.html But the package uses Fortran subroutines only without any C subroutines. In addition, it appears that no stop statement was used in the Fortran subroutines. See the following check results: http://www.r-project.org/nosvn/R.check/r-devel-linux-x86...

...ason? I would guess that > > CRAN > > requires only the _current_ source, not _every_ source. > > > Well, it seems to me that for the OSX Mavericks platform 0.5-2 is the > current version. Because the latest version failed to build on Mavericks: http://www.r-project.org/nosvn/R.check/r-release-osx-x86_64-mavericks/Rglpk-00install.html Possibly because a system requirement is not installed. Dan > > Gabor > > [[alternative HTML version deleted]] > > ______________________________________________ > R-devel at r-project.org mailing list > htt...

Hi all. I've recently uploaded a package (bnlearn) to CRAN. It builds fine on both Linux (32 and 64 bit) and Windows, but fails on MacOSX ix86 because of C90 vs C99 issues: http://www.r-project.org/nosvn/R.check/r-patched-macosx-ix86/bnlearn-00install.html Since I've no MacOSX machine at hand, I would like to ask you: why is C99 not the default for gcc on MacOSX ix86? Is it safe to force gcc to use C99 with either -std=c99 o -std=gnu99? Thanks in advance. -- Marco Scutari...

...incorrectly duplicates the last line unless it ends with a newline. I don't see this in R 3.2.2 RC (2015-08-13 r69049). It seems to have started fairily recently; I spotted this yesterday after starting to get errors in my R.utils check that use capture.output(), cf. https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/R.utils-00check.html Examples: > x <- "a" > cat(x) a> > capture.output(cat(x)) [1] "a" "a" > x <- "a\n" > cat(x) a > capture.output(cat(x)) [1] "a" > x <- "a\nb&quot...

...For the R package bujar, the warnings below were generated on CRAN's Windows systems. The package uses some Fortran subroutines. I would appreciate any advice to eliminate the warnings. By the way, similar warnings were generated to some unrelated R packages as well: https://www.r-project.org/nosvn/R.check/r-oldrel-windows-ix86+x86_64/imputeTS-00check.html. Thanks in advance. Zhu Wang https://www.r-project.org/nosvn/R.check/r-devel-windows-ix86+x86_64/bujar-00check.html * installing *source* package 'bujar' ... ** package 'bujar' successfully unpacked and MD5 sums checked...

I am getting the following on CRAN windows and winbuilder https://www.r-project.org/nosvn/R.check/r-devel-windows-ix86+x86_64/penaltyLearning-00check.html Apparently there is an error in re-building vignettes, but I do not have any idea what it is, because all that is listed is three dots (...). Is this a bug in R CMD check? If not, the only solution I can think of is removing the vig...

...could not find function "gladeXMLNew" Error : .onLoad failed in 'loadNamespace' for 'RGrace' Error: package/namespace load failed for 'RGrace' I am running R 2.7.1 on Ubuntu 8.04 Hardy Heron I found only one reference for this prob here: http://www.r-project.org/nosvn/R.check/r-oldrel-macosx-ix86/RGrace-00check.txt Is it a bug or a system specific problem? Has it any workaround? regards and thx in advance tomas

Hi, I am using caretNWS on a RHEL x86_64 system and I am getting an error message that is nearly identical to the one occuring in http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/caretNWS-00check.txt Error in socketConnection(serverHost, port = port, open = "a+b", blocking = TRUE) : unable to open connection Calls: system.time ... .local -> tryCatch -> tryCatchList -> socketConnection In addition: Warning message: In soc...

Hi, I'd like to run R-devel in a sid system that has the corresponding R packages installed (most of them). I'd be using this primarily for testing how packages that I maintain would build and check there. I know this is available via http://www.r-project.org/nosvn/R.check, but in some cases I need more control. I thought I'd have R-devel trunk live in /usr/local/src/R-devel, and then run it like: R_LIBS_USER=/usr/local/lib/R-devel/site-library /usr/local/src/R-devel/bin/R so that I can have packages built with R-devel in a different directory from tho...

Hello, All: The CRAN checks for the "fda" package includes one error: The error most likely occurred in ... file.copy2 ... Error: unprotect_ptr: pointer not found Execution halted (http://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian/fda-00check.html) The help page for "file.copy2" includes "\examples" with everything wrapped in "\dontrun". I'm unable to replicate this error. I'm about to submit a new version of the fda package to CRA...

Dear developeRs, Compilation of the latest version (0.9-5) of my actuar package fails with r-release MacOS_X ix86 on CRAN; see http://www.R-project.org/nosvn/R.check/r-release-macosx-ix86/actuar-00check.html All errors come from accented letters in comments in latin-1 encoded files (except hierarc.R which is in UTF-8, my bad). Encoding is declared as latin-1 in DESCRIPTION. The package checks and compiles fine on Windows, Linux and, ironically,...

Dear R developers, we have currently a 'mysterious' test problem with one package that successfully passed the tests on all platforms, with the only exception of Solaris x86 where obviously one of our help examples breaks the CRAN test. As we don't own such a machine I want to ask about a possibility to run a few tests on such a system: r-patched-solaris-x86 An even more recent

...age can only contain pathnames of length <= 100 characters (restriction in the tar file format), and mine are longer than that, e.g. aroma.affymetrix/inst/testScripts/system/chipTypes/Mapping50K_Hind240,Xba240/test20080730,100K,BPN,alleleSpecific.R [115 chars]. See also http://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora/aroma.affymetrix-00check.html . One strategy is to create a local tar file referring to files system/chipTypes/Mapping50K_Hind240,Xba240/test20080730,100K,BPN,alleleSpecific.R and then untar it to aroma.affymetrix/inst/testScripts/ during installation. I want to...

...M To: 'G?bor Cs?rdi' <csardi.gabor at gmail.com>; 'ligges at statistik.tu-dortmund.de' <ligges at statistik.tu-dortmund.de> Subject: RE: [EXTERNAL] Re: CRAN submission crayon 1.3.4 Gabor and Uwe, Thank you for promptly notifying me. I saw the https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/drake-00check.html, and I could not reproduce it either. I tried: ? Ubuntu 17.04 with gcc (though drake has no complied code) ? a fresh copy of 64-bit R-devel r73293 (2017-09-16) ? the latest version of all required packages, including crayon 1.3.4 ? `R C...

...version that RcppArmadillo). It seems now working with almost all CRAN targets, but a problem remains with fedora (clang & gcc) devel. Our issue is that the rhub docker is not well sync with the CRAN fedora-clang-devel config: - failing on CRAN (without clear reason): https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/rlibkriging-00check.html - passing on rhub: https://builder.r-hub.io/status/rlibkriging_0.7-3.tar.gz-20f7dc7562726497af7c678ab41f4dea So we cannot investigate and fix the problem. Note that we did quite strange things with the fedora platforms: include ex...

...: > dput(z$a) structure("foo", .Names = "b") I know that there were some recent improvements to 'deparse' (c73120, 73144). Among the failures on my package on R-devel on CRAN, a test run on version as old as r73150 does manifest this bug (https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-gcc/httptest-00check.html), so the timing does suggest that those changes could be related. Neal > sessionInfo() R Under development (unstable) (2017-09-07 r73219) Platform: x86_64-apple-darwin15.6.0 (64-bit) Running under: macOS Sierra 10.12.6 Matrix prod...

...quite afraid this is a dumb question, so sorry in advance) I am trying to install the package rimage to R version 2.8.1 with Ubuntu Intrepid. When I type "sudo R CMD INSTALL" I get the following error message (pasted below). I know the same problem appears here (http://www.r-project.org/nosvn/R.check/r-patched-linux-ix86/rimage-00install.html) but I do not know what its appearance there means. Thanks in advance for any help! Abbe g++ -I/usr/share/R/include -g -O2 -fpic -g -O2 -c matrix.cpp -o matrix.o /usr/include/c++/4.3/bits/stl_vector.h: In member function ?void std::vecto...

Hello, the compilation of the GUTS package on CRAN for Mac produces the following error messages: http://www.r-project.org/nosvn/R.check/r-release-macosx-ix86/GUTS-00install.html I guess it is some namespace collision, but I can not reproduce it on my machine, it compiles fine here. What is the cause and which setup do I need to reproduce the errors? R: version platform i386-apple-darwin9.8.0 arch i386 os...

...madillo). > It seems now working with almost all CRAN targets, but a problem remains with fedora (clang & gcc) devel. > > Our issue is that the rhub docker is not well sync with the CRAN fedora-clang-devel config: > - failing on CRAN (without clear reason): https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/rlibkriging-00check.html I see? 2 candidates for? reasons of failing on CRAN: ?1. test time is 30 min while 15 min are allowed; ?2. your code try to get 30 threads while CRAN limits them to 2; Try to make your tests shorter ( < 15 min) on 2 threads. M...