similar to: R CMD check warning about boot ?

Hi, can I claim the warning that occurs (at R CMD check --as-cran) when I use 'library(ggplot2)' in executed vignette code as SPURIOUS (as mentioned in the CRAN policies at section 'Submission') and (since it is the only warning/error) get my package submission accepted? Has anybody experience with that? Otherwise, is there a workaround to evaluate this code (and calls to

I often get warnings like the following when running R CMD check [...] * checking for code/documentation mismatches ... OK * checking tests ... make: *** Warning: File `Makevars' has modification time in the future (2001-11-13 12:54:37.381546042 > 2001-11-13 12:54:37.314975985) [...] I am ready to believe that this is not a bug (i.e., that the timing on my various machines and file

We're seeing many warnings like this: Warning: S3 method 'print.check_code_usage_in_package' was declared in NAMESPACE but not found But the package's NAMESPACE does not contain such a declaration. Seeing this in many Bioconductor packages when running R CMD check on Windows with R-devel built 1 Sept. Below is a snip of the output from R CMD check. Any ideas of what this

This looks like a buglet: > install.packages("lme4", depend=TRUE, lib="~/Rlibrary/") --- Please select a CRAN mirror for use in this session --- [...snip...] ** preparing package for lazy loading Error: package 'Matrix' 0.999375-4 was found, but >= 0.999375.11 is required by 'lme4' Execution halted ERROR: lazy loading failed for package 'lme4' **

In > R.version.string [1] "R Under development (unstable) (2011-12-15 r57901)" PkgA promotes 'unique' to a generic and exports that DESCRIPTION: Imports: methods R/f.R: setGeneric("unique") NAMESPACE: export(unique) and PkgB creates and exports a method on unique DESCRIPTION Imports: methods, PkgA R/f.R: setClass("B",

I'm testing a FC5 machine for use in a student lab. R 2.3.1 is installed and seems to work fine. There is one peculiarity - the logins are authenticating to a server, and a "verbose" flag is set somewhere, leading to lots of spurious messages like this request done: ld 0xa227598 msgid 1 which may be confusing R. However, R CMD check seems to fail for packages with no

Hi, When running R CMD check I'm getting a number of errors that I don't quite follow and don't know where to start looking for an answer, any hints appreciated. R CMD check trunk * checking for working latex ... OK * using log directory '/Users/ivisser/Documents/projects/ depmixProject/depmixNew/rforge/depmix/trunk.Rcheck' * using R version 2.6.2 (2008-02-08) * checking

Not too hard to fix, the following buglet (new in 1.3.0), but I'm about to leave for one week (of vacation).. Here is an example (for Linux) : lynne{sfs}214> cd /tmp lynne{sfs}215> mkdir blue lynne{sfs}216> cd blue /tmp/blue lynne{sfs}217> echo 'data(package = "mva")'|R-1.3.0 --vanilla R : Copyright 2001, The R Development Core Team Version 1.3.0

I'm having a very hard time making R CMD check produce a clean check on examples because of the timings inserted into examples by R CMD check. I am getting a difference on every example output caused by timing information being inserted by 'R CMD check'. The current 'Writing R Extensions' manual[1] states on p. 14: If directory tests has a subdirectory Examples

As you may recall, a Debian user complained last year about how R is out of line with respect to the filesystem standards (where, in essence, architecture independent files should be in /usr/share, not /usr/lib). While I more or less just told him to get lost, I think it was mostly BDR who actually added support for this over the summer -- so a public Thanks! first. As of a few weeks ago, I now

hello, everybody, I create a package by myself named "var" on Linux system. I attach a C code which uses "R_ext/Lapack.h" in directory "src". But when I carry out " R CMD check var", it shows > wxt0124() Error in .C("wxt1221", PACKAGE = "var") : C function name not in DLL for package var Execution halted Could you tell me what is

Dear List, I have a problem building an R package using R 1.7.1 that I cannot resolve myself. R CMD check tells me that functions I documented properly in Rd-files are not documented and gives a TeX error at the end, altough the Rd files check is OK. I have three fucntions, one gets through without complaining, the other two don't. All the docu for the example data is also OK. I went through

Can anyone with Heimdal KrbV verify this? -------------- next part -------------- An embedded message was scrubbed... From: Dag-Erling Smorgrav <des at ofug.org> Subject: Kerberos buglet in OpenSSH-3.3p1 Date: 25 Jun 2002 14:52:10 +0200 Size: 1291 Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20020626/347e123e/attachment.mht

Conrad, Small buglet with the 0.9.1 liboggz release (go dude!) http://thaumas.net/~giles/xiph/elphel/clips/elphel_00017.ogg causes a float exception in oggzinfo when it tries to calculate the bitrate. It fails to measure the duration and tries to divide by zero. :) There may well be something wrong with the file, although oggz-validate doesn't complain. Also, the configure script

Hi, I have a function knit_expand() and its source/Rd are below: https://github.com/yihui/knitr/blob/master/R/template.R#L43-L44 https://github.com/yihui/knitr/blob/master/man/knit_expand.Rd When I run R CMD check on the package I get this warning (with both R 2.15.2 and R-devel): * checking for code/documentation mismatches ... WARNING Codoc mismatches from documentation object

I'm trying to R CMD check a package, and I'm getting the 'checking S3 generic/method consistency' warning. I have written a function 'gamma.dist' which is _not_ an S3 method, but happens to collide with the 'gamma' function from the R::base namespace. Is there a way of telling CMD check that the name is intentional and is not meant to be an S3 method? My function

# HG changeset patch # User George Dunlap <george.dunlap@eu.citrix.com> # Date 1345022863 -3600 # Node ID 0982bad392e4f96fb39a025d6528c33be32c6c04 # Parent dc56a9defa30312a46cfb6ddb578e64cfbc6bc8b xl: Suppress spurious warning message for cpupool-list libxl_cpupool_list() enumerates the cpupools by "probing": calling cpupool_info, starting at 0 and stopping when it gets an error.

I'm resending this after a decent interval of 20 days -- any opinions? Should I file it as a bug report? Is it my mistake? cheers Ben Bolker -------- Original Message -------- Subject: buglet (?) in de.restore() Date: Tue, 21 Aug 2007 13:29:33 -0400 From: Ben Bolker <bolker at zoo.ufl.edu> To: r-devel at r-project.org If one calls data.entry() with a matrix: A =

I have been checking my package coda with the current R-devel using "R CMD check". As usual, this has uncovered a large number of errors and inconsistencies in my documentation, for which I am very grateful. The only problem I have is with code/documentation mismatches when I have written a method for a generic function, e.g. * checking for code/documentation mismatches ... WARNING

Hi the list, I build a package. They was a mistake in it, but R CMD check did not find it. Is that normal ? Here is what Kurt gets (which is right, I did this mistake): --- 8< ---------------- * checking for code/documentation mismatches ... WARNING S4 class codoc mismatches from documentation object 'LongData-class': Slots for class 'LongData' Code: id other time traj