Displaying 20 results from an estimated 1000 matches similar to: "Extra "Note" in CRAN submission"
2013 Sep 19
1
Vignette problem and CRAN policies
Hello, All:
The vignette with the sos package used "upquote.sty", required for R
Journal when it was published in 2009. Current CRAN policy disallows
"upquote.sty", and I've so far not found a way to pass "R CMD check"
with sos without upquote.sty.
I changed sos.Rnw per an email exchange with Prof. Ripley without
solving the problem; see below. The
2018 May 04
2
Debugging "SETLENGTH() cannot be applied to an ALTVEC object."?
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/
2018 Mar 05
2
Problem with Rd2.tex tduring compilation
Hello, I am receiving this message when uploading my R package to rdevel.
https://win-builder.r-project.org/incoming_pretest/180305_110240_Compositional_29/00check.log
Can anybody please help?
[[alternative HTML version deleted]]
2014 May 02
1
Authors@R: and Author field
Hi to all
Authors@R: c(person("fooa","foob", role = c("aut","cre"),
email = "fooa.foob@fooc.de"),
person("foo1","foo2", role = c("ctb"),
email = "foo1.foo2@foo3.de"))
Author: fooa foob, with contributions from foo1 foo2
using r CMD check --as-cran .. (R 3.1
2018 Mar 05
2
Σχετ: 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
2013 Oct 25
2
R CMD check problem with R 3.0.2
Using SUSE Linux, Windows 32 bit and Windows 64 bit R 3.0.2 , I am unable
to use R CMD check successfully. Here is the Windows 64 bit report:
Z:\R\source\effects>R CMD check pkg
* using log directory 'Z:/R/source/effects/pkg.Rcheck'
* using R version 3.0.2 (2013-09-25)
* using platform: x86_64-w64-mingw32 (64-bit)
* using session charset: ISO8859-1
* checking for file
2018 Sep 20
3
future time stamps warning
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
2018 Mar 05
0
Problem with Rd2.tex tduring compilation
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.
>
2013 Oct 15
1
discrepancy between r cmd check --as-cran and messages at submission
Dear r-devel list,
I've observed at both of my submissions that issues arise at submission
that were not pointed out by
R cmd check --as-cran
For example at my last submission:
You have
VignetteBuilder: knitr
but there is nothing looking like a vignette in your source package....
We also see:
* checking DESCRIPTION meta-information ... NOTE
Author field differs from that derived from
2018 Mar 05
0
Σχετ: Problem with Rd2.tex tduring compilation
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
2018 Sep 20
3
future time stamps warning
Time stamps are correct and my system time is correct.
I am now tried to use Sys.setFileTime() to update time stamps as proposed.
This does not help.
The windows and debian builds give different reports on the time stamp
issue.
https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.8_20180920_122655/Windows/00check.log
2020 Oct 22
2
vanilla session in R Gui or RStudio
[env: Windows, R 3.6.6]
When I start R from the R Gui icon or from RStudio, I get a large number of packages loaded via a namespace. Not entirely clear where these come from.
As a result, I often run into problems updating packages because something is already loaded. How can start a new gui session with minimal packages loaded?
> sessionInfo()
R version 3.6.3 (2020-02-29)
Platform:
2012 Dec 14
1
[HCL] Lyonn CTB-1200 supported by blazer_usb
Lyonn CTB-1200
root at frambuesa:~# upsc lyonn at localhost
battery.voltage: 27.20
battery.voltage.nominal: 24.0
beeper.status: enabled
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.4.3
driver.version.internal: 0.03
input.current.nominal: 5.0
input.frequency: 49.9
input.frequency.nominal: 50
input.voltage: 213.3
2020 Sep 08
1
failing automatic incoming check
Hello,
I got a notification regarding a failure to pass incoming checks
automatically after a CRAN submission. The details are given here:
https://win-builder.r-project.org/incoming_pretest/diveMove_1.5.0_20200908_191325/
The only visible issue is a NOTE from the macosx build, with the very
terse:
"No Protocol Specified"
My searches suggest this can be ignored, but it would be nice
2020 May 23
1
GCC warning
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
2020 Oct 22
0
vanilla session in R Gui or RStudio
Have you looked into your .Rprofile file? Loading packages is not something R normally does without your telling it to do so, but many people forget that they have done so.
On October 22, 2020 3:47:04 PM PDT, Michael L Friendly <friendly at yorku.ca> wrote:
>[env: Windows, R 3.6.6]
>
>When I start R from the R Gui icon or from RStudio, I get a large
>number of packages loaded
2020 Oct 23
3
vanilla session in R Gui or RStudio
As Jeff says, it might be that you have a ~/.Rprofile file with
instructions to load packages when R starts. It could also be that
you have a .RData file, which is saved if you answer yes to:
> Save workspace image? [y/n/c]: y
when you quit R. If this file exists, then R loads it and all the
objects you had when you saved it. If there are objects associated
with packages, then that will
2017 Sep 17
0
FW: CRAN check errors: drake 4.1.0 on r-devel-linux-x86_64-debian-clang
Hello,
The CRAN checks for the drake package (4.1.0) fail for r-devel-linux-x86_64-debian-clang. This happened right when crayon 1.3.4 was released, but I suspect the problem is not with crayon or drake, but with base R-devel. I cannot reproduce the error myself, but I have copied a minimal working example (MWE) below that should theoretically isolate the problem.
`find_namespaced_functions()`
2020 Oct 23
0
vanilla session in R Gui or RStudio
Can you be more specific about what conditions cause R to automatically load a package when a .RData file is loaded? My experience has actually been the opposite.
On October 22, 2020 6:13:11 PM PDT, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote:
>As Jeff says, it might be that you have a ~/.Rprofile file with
>instructions to load packages when R starts. It could also be
2018 Sep 20
0
future time stamps warning
On Thu, Sep 20, 2018 at 11:46 AM Leo Lahti <leo.lahti at iki.fi> wrote:
>
> Time stamps are correct and my system time is correct.
>
> I am now tried to use Sys.setFileTime() to update time stamps as proposed.
> This does not help.
>
> The windows and debian builds give different reports on the time stamp
> issue.
>