On Thu, 4 Mar 2021 12:09:51 +0100
Sebastian Meyer wrote:
> Am 04.03.21 um 10:24 schrieb Rolf Turner:
> > But this still leaves the question: Why the is
> > R CMD check telling me to use the flag --resave-data, when I *just
> > did that*???
>
> Yes, indeed! I've investigated further and
FYI, and in case others wonder or search for this later, the warnings:
Warning: invalid uid value replaced by that for user 'nobody'
Warning: invalid gid value replaced by that for user 'nobody'
are harmless and has nothing to do with your problem reported here.
It happens because on the system
I don't have any strong suggestions. Things I'd look for:
- is the .Rbuildignore filename spelled correctly? It was in your
message, but maybe there's something different in the actual file on
disk. Running file.exists(".Rbuildignore") should return TRUE if your
working directory is the
Dear Duncan and Jeff,
Yes, I see those files when tar xvf miclust_1.2.6.tar.gz.
As usual, I am both building and checking in a terminal (outside RStudio):
$ R CMD build miclust --resave-data
* checking for file ‘miclust/DESCRIPTION’ ... OK
* preparing ‘miclust’:
* checking DESCRIPTION
Don't run check against your development directory. Run it against the tar.gz
file.
On March 4, 2021 5:09:07 AM PST, Jose Barrera wrote:
>Dear all,
>
>devtools::check() gives me the following NOTE:
>
>* Non-standard files/directories found at top level:
> ‘README.Rmd’ ‘miclust.Rproj’
>
>I
On 04/03/2021 8:09 a.m., Jose Barrera wrote:
Dear all,
devtools::check() gives me the following NOTE:
* Non-standard files/directories found at top level:
‘README.Rmd’ ‘miclust.Rproj’
I get the same result with R CMD check --as-cran and R CMD check in a
terminal.
My .Rbuildignore
The Debian check log appends the check status of the current CRAN
version just for comparison.
[
Indeed, these old problems are sometimes mistaken to cause a rejection
and I think it would help if there were a few more empty lines between
the new and the old check results and if the first two
Hi,
I am trying to submit a revised version of a package to CRAN and for the second
time it does not pass the incoming checks. I can’t figure out why.
The new version is numbered 2.0.0, the previous one was 1.1.0.
- The Windows report gives me one note:
* checking CRAN incoming feasibility
Dear all,
devtools::check() gives me the following NOTE:
* Non-standard files/directories found at top level:
‘README.Rmd’ ‘miclust.Rproj’
I get the same result with R CMD check --as-cran and R CMD check in a
terminal.
My .Rbuildignore includes both ^.*\.Rproj$ and ^README\.Rmd$.
I
Am 04.03.21 um 10:24 schrieb Rolf Turner:
>
> On Thu, 4 Mar 2021 08:44:31 +0100
> Sebastian Meyer wrote:
>
>> Am 04.03.21 um 01:41 schrieb Rolf Turner:
>>>
>>> ... by using R CMD build --resave-data
>>>
>>> But I *did* use that flag with my build command!!! And yet "R CMD
>>> check" seems to
On Thu, 4 Mar 2021 08:44:31 +0100
Sebastian Meyer wrote:
> Am 04.03.21 um 01:41 schrieb Rolf Turner:
> >
> > ... by using R CMD build --resave-data
> >
> > But I *did* use that flag with my build command!!! And yet "R CMD
> > check" seems to think that I didn't!
>
> Just to be sure: Are
On Wed, 3 Mar 2021 22:25:59 -0800
Ott Toomet wrote:
> As I read the docs (a few months ago though), you are supposed to
> include the pdf and encouraged to include sources, but the process to
> get pdf from source may depend on your private
> libraries/data/software, and is not replicated on
On Thu, 4 Mar 2021 07:39:31 +0100
Göran Broström wrote:
> Hi Rolf,
>
> On 2021-03-04 03:51, Rolf Turner wrote:
> >
> > I am trying to create a vignette in a package (basically just using
> > LaTeX code; no R calculations or data are involved).
> >
> > The LaTeX code involves the use of the
On Wed, 3 Mar 2021 21:36:23 -0800
Henrik Bengtsson wrote:
> The R.rsp has a vignette engine for plain LaTeX sources. See
> https://cran.r-project.org/web/packages/R.rsp/vignettes/R_packages-LaTeX_vignettes.pdf
> for how. It's straightforward. Maybe that helps.
Indeed. It looks admirably
14 matches
Mail list logo
