similar to: package encoding warning

When I am loading the RGrace package I am getting the following errormessage: Loading required package: RGtk2 Loading required package: grid Loading required package: cairoDevice Error in figure() : 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

Hi I have submitted a package (rioja) to CRAN. It checks OK for all R versions and OS's except r-release-macosx-ix86 where it fails when checking the examples. Specifically, it fails because R can't find the package vegan which is needed in a function. Here is the snippet from the check results: ### Begin snippet checking examples ... ERROR Running examples in 'rioja-Ex.R'

I mistakenly left a write in "/tmp" in the rockchalk package (version 1.8.109) that I uploaded last Friday. Kurt H wrote and asked me to fix today. While uploading a new one, I became aware of a problem I had not seen. The version I uploaded last Friday, 1.8.109, has OK status on all platforms except r-release-windows-ix86+x86_64. I get OK on oldrel-windows and also on devel-windows.

Hi all, 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

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

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

Hi All, quick question. How does one know which R versions r-release and r-oldrel correspond to? Is there a prefered way to determine this programmatically? So far I could only find messy ways, like parsing the HTML of the homepage, or (for r-release) checking the latest R-x-x-x tag in the SVN. The SVN is actually not bad, but how about r-oldrel? Is that always the previous release? Or the

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

My thanks to Dr. John Fox and Dr. Duncan Murdoch. But, I have upgraded all my R-3.4.3 libraries to R-3.5.0, and I have not backed-up copies of old version. So, I would give a try each to the solutions suggested by John Fox and Dengan Murdoch. With regards, Dr. A.K. Singh On Thu 26 Apr, 2018, 9:44 PM Duncan Murdoch, <murdoch.duncan at gmail.com> wrote: > On 26/04/2018 10:33 AM, Fox,

Hi, I was just looking at the "CRAN Daily Package Check Results" [http://cran.r-project.org/src/contrib/checkSummary.html], and realized there are 1000 packages on CRAN as of today (look at row 3 in the table below). Yet another quite extraordinary milestone in R history. Last updated on 2007-04-12 11:48:32 Results for installing and checking packages using the three current flavors

On 26/04/2018 1:54 PM, Akhilesh Singh wrote: > My thanks to Dr. John Fox and Dr. Duncan Murdoch. But, I have upgraded > all my R-3.4.3 libraries to R-3.5.0, and I have not backed-up copies of > old version. So, I would give a try each to the solutions suggested by > John Fox and Dengan Murdoch. Here is some unsolicited advice: I would strongly recommend that you make it a higher

>>>>> Paul Johnson <pauljohn32 at gmail.com> >>>>> on Mon, 20 Nov 2017 14:59:26 -0600 writes: > I mistakenly left a write in "/tmp" in the rockchalk package (version > 1.8.109) that I uploaded last Friday. Kurt H wrote and asked me to fix > today. > While uploading a new one, I became aware of a problem I had not seen.

http://bugzilla.mindrot.org/show_bug.cgi?id=804 Summary: Locale character encoding disobeyed on interactive session Product: Portable OpenSSH Version: 3.8p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: minor Priority: P4 Component: ssh AssignedTo: openssh-bugs at

On 26/04/2018 10:33 AM, Fox, John wrote: > Dear A.K. Singh, > > As you discovered, the data.table package has an error under R 3.5.0 that prevents CRAN from distributing a Windows binary for the package. The reason that you weren't able to install the package from source is apparently that you haven't installed the R package-building tools for Windows. See

You are right. I do take backups. But, this time I was too sure that nothing will go wrong. But, this was over-confidence. I need to take more care in future. Thanks anyway. With regards, Dr. A.K. Singh On Thu 26 Apr, 2018, 11:49 PM Duncan Murdoch, <murdoch.duncan at gmail.com> wrote: > On 26/04/2018 1:54 PM, Akhilesh Singh wrote: > > My thanks to Dr. John Fox and Dr. Duncan

Dear fellow developers, Is there an easy way to determine how big my packages (psych and psychTools) will be on various versions of CRAN? I have been running into the dread 'you are bigger than 5 MB" message for some installations of R on CRAN but not others. The particular problem seems to be some of the mac versions (specifically r-oldrel-macos-arm64 and r-release-macos-X64 ) When

Hi, Has any one know how to skip ix86 packages from installation in Centos kickstart? Most of our machines have 64bit Intel/AMD CPUs, and it make non-sense to still keep 32bit compatibility. Even worse of i*86 packages is, when upgrade we have to recompile both ix86 version and x86_64 version to get an automatic yum upgrade. I know we could use 'exclude' option to exclude i*86 packages

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

If you're installing packages to the default location in your home account and you didn't remove those library folders, you still have you R 3.4 package installs there, e.g. > dir(dirname(.libPaths()[1]), full.names = TRUE) [1] "/home/hb/R/x86_64-pc-linux-gnu-library/3.4" [2] "/home/hb/R/x86_64-pc-linux-gnu-library/3.5" [3]

You might find this discussion useful, too: https://github.com/Rdatatable/data.table/issues/2797 On 04/26/2018 11:01 PM, Henrik Bengtsson wrote: > If you're installing packages to the default location in your home > account and you didn't remove those library folders, you still have > you R 3.4 package installs there, e.g. > >> dir(dirname(.libPaths()[1]), full.names =