On 17 January 2024 at 09:42, Simon Urbanek wrote:
| that check always hangs for me (I don't think it likes NZ ;)), so I just use
|
| _R_CHECK_CRAN_INCOMING_REMOTE_=0 R CMD check --as-cran ...
You can also set it in Renviron files consulted just for checks:
$ grep INCOMING_= ~/.R/check.Renvir
Ralf,
that check always hangs for me (I don't think it likes NZ ;)), so I just use
_R_CHECK_CRAN_INCOMING_REMOTE_=0 R CMD check --as-cran ...
Cheers,
Simon
> On Jan 16, 2024, at 6:49 PM, Rolf Turner wrote:
>
>
> On Tue, 16 Jan 2024 16:24:59 +1100
> Hugh Parsonage wrote:
>
>>> Surely the s
В Tue, 16 Jan 2024 08:47:07 +
David Hugh-Jones пишет:
> If I understand correctly, the current procedure is that the client
> downloads every package name from CRAN, and then checks its name is
> unique.
This is not the only check that relies on utils::available.packages().
In particular, s
On 16.01.2024 06:49, Rolf Turner wrote:
On Tue, 16 Jan 2024 16:24:59 +1100
Hugh Parsonage wrote:
Surely the software just has to check
that there is web connection to a CRAN mirror.
Nope! The full code is in tools:::.check_package_CRAN_incoming (the
body of which filled up my entire co
If I understand correctly, the current procedure is that the client
downloads every package name from CRAN, and then checks its name is
unique. Wouldn’t
it be faster (for both parties) to check name uniqueness directly on the
server?
Writing: wyclif.substack.com
Book: www.wyclifsdust.com
On Tue
В Tue, 16 Jan 2024 05:49:01 +
Rolf Turner пишет:
> The problem is persistent/repeatable. I don't believe that there is
> any faulty connection.
One of the things done by R CMD check --as-cran at this point is
sending a HEAD request to every Web link mentioned in the package
documentation an
On Tue, 16 Jan 2024 16:24:59 +1100
Hugh Parsonage wrote:
> > Surely the software just has to check
> that there is web connection to a CRAN mirror.
>
> Nope! The full code is in tools:::.check_package_CRAN_incoming (the
> body of which filled up my entire console), but to name a few checks
>
> Surely the software just has to check
that there is web connection to a CRAN mirror.
Nope! The full code is in tools:::.check_package_CRAN_incoming (the
body of which filled up my entire console), but to name a few checks
it has to do: check that the name of the package is not the same as
any
This post essentially amounts to idle curiosity. I don't really expect
that anything can be done about the problem that I perceive.
When I check a package using --as-cran, the code spits out a line
checking CRAN incoming feasibility ...
and then disappears into a black hole for what seems
On Sat, 5 Oct 2019 16:52:16 -0500
"R. Mark Sharp" wrote:
> MIT + file LICENSE
> File 'LICENSE':
> Copyright 2017-2019 R. Mark Sharp
>
> Permission is hereby granted, <...>
Note that for packages licensed under MIT license, the LICENSE file
should only contain the lines:
>> YEAR:
Roy,
Thank you for your guidance and advice.
I ran usethis::use_cran_comments() shown below.
> usethis::use_cran_comments()
✔ Setting active project to
'/Users/msharp/Documents/Development/R/r_workspace/library/nprcmanager'
✔ Writing 'cran-comments.md'
✔ Adding '^cran-comments\\.md$' to '.Rbui
use this::use_cran_comments()
There is a place to put that it is a new submission
I would recommend also testing using:
devtools::check_win_release()
devtools::check_win_devel()
You should only have the one note that it is a new submission. When you
submit, you may or may not get a note tha
I getting ready to submit a package to CRAN for the first time. I have run
cran_prep <- check_for_cran() using the rhub package. I understand that as a
new package it will generate a NOTE. As a novice, I do not know what is to be
expected within that NOTE and want to make sure the NOTEs I have r
13 matches
Mail list logo
