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
cryptographically weak TLS 1.0 & 1.1 protocols and only supporting
connections with the TLS 1.2 protocol.

https://githubengineering.com/crypto-removal-notice/

This could probably be fixed with upgrading/updating the SSL software on
the win-builder server (to whatever version the 3.4.4 and 3.5.0 servers
have).

On Sat, Mar 24, 2018 at 5:21 AM, peter dalgaard <pda...@gmail.com> wrote:

> 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 <pda...@gmail.com> wrote:
> >
> > 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 <tyle...@gmail.com> wrote:
> >>
> >> 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 <tyle...@gmail.com>'
> >>
> >> Found the following (possibly) invalid URLs:
> >> URL: http://github.com/tylermorganwall/skpr
> >>   From: DESCRIPTION
> >>   Status: Error
> >>   Message: libcurl error code 35
> >>      error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert
> >> protocol version
> >> URL: http://github.com/tylermorganwall/skpr/issues
> >>   From: DESCRIPTION
> >>   Status: Error
> >>   Message: libcurl error code 35
> >>      error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert
> >> protocol version
> >>
> >> I checked the version of the package currently on the CRAN that passed
> >> without any libcurl errors or NOTEs back in January, and it too
> displayed
> >> this NOTE, which again only occurred on R-oldrelease. Is there a way to
> >> prevent this or should I just mention this NOTE in my CRAN submission
> >> comment?
> >>
> >> Tyler
> >>
> >>      [[alternative HTML version deleted]]
> >>
> >> ______________________________________________
> >> R-package-devel@r-project.org mailing list
> >> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >
> > --
> > Peter Dalgaard, Professor,
> > Center for Statistics, Copenhagen Business School
> > Solbjerg Plads 3, 2000 Frederiksberg, Denmark
> > Phone: (+45)38153501
> > Office: A 4.23
> > Email: pd....@cbs.dk  Priv: pda...@gmail.com
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> Peter Dalgaard, Professor,
> Center for Statistics, Copenhagen Business School
> Solbjerg Plads 3, 2000 Frederiksberg, Denmark
> Phone: (+45)38153501
> Office: A 4.23
> Email: pd....@cbs.dk  Priv: pda...@gmail.com
>
>
>
>
>
>
>
>
>
>

        [[alternative HTML version deleted]]

______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel

Reply via email to