This is more likely an issue with the win-builder server than an issue with
3.3.3, as I uploaded a prior version of my package that previously (in
January) had a clean check and it returned the same NOTE. I believe this
error stems from GitHub discontinuing support on Feb 22nd for the
cryptographic
Sorry, I forgot: We don't switch until _release_ of 3.5.0, four weeks further
down the line. Still, it doesn't seem worth it making much of a fuss about
3.3.3.
-pd
> On 24 Mar 2018, at 10:10 , peter dalgaard wrote:
>
> Given that R-oldrelease will become 3.4.4 when we branch for 3.5.0 on Mond
Given that R-oldrelease will become 3.4.4 when we branch for 3.5.0 on Monday,
perhaps you could just wait it out?
-pd
> On 23 Mar 2018, at 17:59 , Tyler wrote:
>
> I am getting a NOTE only on R-oldrelease when checking my package on
> win-builder:
>
> * checking CRAN incoming feasibility ...
I am getting a NOTE only on R-oldrelease when checking my package on
win-builder:
* checking CRAN incoming feasibility ... NOTE
Maintainer: 'Tyler Morgan-Wall '
Found the following (possibly) invalid URLs:
URL: http://github.com/tylermorganwall/skpr
From: DESCRIPTION
Status: Error
M
