On 26 August 2020 at 08:46, Dirk Eddelbuettel wrote:
| One way to ensure the last point is to have a file
|
| ~/.R/check.Renviron-Rdevel
|
| which I had (but where I had commented out 'incoming' as it can take a
| moment). Current values below, with thanks to Uwe for the reminder.
And I
Ok, Uwe was kind enough to take me to task off-list and I can now confirm
that I _can_ replicate the URL issue locally by ensuring all three of
- recent enough r-devel build (that was true, I may add that the
rocker/r-devel and rocker/drd containers I look after can help)
- built with
Pls try agaibn, if it fails again, pls let me know privately.
Best,
Uwe Ligges
On 26.08.2020 15:13, Nicholas Tierney wrote:
Hi Uwe,
OK thank you for that, good to know! I imagine it might be a bit tricky
to know when, but do you have an idea of when submissions might return
to normal? Or
Hi Uwe,
OK thank you for that, good to know! I imagine it might be a bit tricky to
know when, but do you have an idea of when submissions might return to
normal? Or should I be good to submit again soon?
Thanks again,
Nick
On Wed, 26 Aug 2020 at 23:06, Uwe Ligges
wrote:
> Friends, thias
Friends, thias looks like a hang in the CRAN incoming feasibility
checks, hence may well be some web related issue as it seems it ran into
the timeout there.
Best,
Uwe Ligges
On 26.08.2020 14:57, Nicholas Tierney wrote:
Hi Michael,
I do indeed have quite a few examples in the package, this
On 26 August 2020 at 14:34, Vincent van Hees wrote:
| Addressing the errors is not the problem. I want to be able to detect these
| problems when I do: R CMD check --as-cran.
You cannot :-/. I pointed that out to CRAN maintainers a few times myself.
| At the moment, I can only detect the
Hi Michael,
I do indeed have quite a few examples in the package, this hasn't been a
problem in the past, but I guess I could try reducing them down. Have you
had this problem before?
Cheers,
Nick
On Wed, 26 Aug 2020 at 22:49, Michael Dewey wrote:
> Dear Nicholas
>
> Do you in fact have many
Sorry, I was reading too fast. One possibility is your R version is wee bit
old. Try a more recently daily build.
I recently saw such errors when submitting to Win-Builder, but was fine locally
(per your situation).
Bryan
> On Aug 26, 2020, at 8:34 AM, Vincent van Hees
> wrote:
>
>
On Wed, Aug 26, 2020 at 7:43 AM Vincent van Hees
wrote:
>
> Addressing the errors is not the problem. I want to be able to detect these
> problems when I do: R CMD check --as-cran.
> At the moment, I can only detect the errors by submitting the package to
> CRAN, because only their package check
Dear Nicholas
Do you in fact have many examples in the package? Perhaps for some
mysterious reason they take longer there than when you check at home.
Michael
On 25/08/2020 14:54, Nicholas Tierney wrote:
Hi Everyone,
I have an error when submitting to Winbuilder for my R package, naniar
Addressing the errors is not the problem. I want to be able to detect these
problems when I do: R CMD check --as-cran.
At the moment, I can only detect the errors by submitting the package to
CRAN, because only their package check triggers these errors.
On Wed, 26 Aug 2020 at 14:30, Bryan Hanson
At the minimum you should look at the “moved to” URLs and change your links to
those (some are outright changes in URLs that were redirected and some are http
to https changes).
Bryan
> On Aug 26, 2020, at 8:22 AM, Vincent van Hees
> wrote:
>
> Hello,
> URL errors in my DESCRIPTION file and
Hello,
URL errors in my DESCRIPTION file and package vignette are not picked up
when I do R CMD check --as-cran or devtools::check(). I only know about
these errors because CRAN has rejected my package submission and instructed
me to fix the urls (example at end of this message).
I am trying to
13 matches
Mail list logo
