Dear Dustin,
On 2020-08-27 8:26 p.m., Tracy, Josef wrote:
Hi John,
Duncan explained the cause of the problem, but i'm afraid I didn't
follow how one solves it. Did you manage to get a check without that note?
I didn't -- I just disregarded the note assuming that it would go away
when the time server was back up.
(I've cc'd the R-package-devel list so that others can see your question
and my response.)
Best,
John
Thanks You,
Dustin
Dustin Tracy
Postdoctoral Researcher
Economic Science Institute
Chapman University
www.DustinTracy.com <http://www.DustinTracy.com>
------------------------------------------------------------------------
*From:* R-package-devel <r-package-devel-boun...@r-project.org> on
behalf of John Fox <j...@mcmaster.ca>
*Sent:* Thursday, August 27, 2020 11:39 AM
*To:* Duncan Murdoch <murdoch.dun...@gmail.com>;
r-package-devel@r-project.org <r-package-devel@r-project.org>
*Subject:* Re: [R-pkg-devel] R CMD check "unable to verify current time"
External Message
[External Message]
Dear Duncan,
Thank you and the others who responded to my message.
John
On 2020-08-27 2:17 p.m., Duncan Murdoch wrote:
R tries to get the time from
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fworldtimeapi.org%2Fapi%2Ftimezone%2FUTC&data=02%7C01%7Ctracy%40chapman.edu%7Ce1a2215e59904aaee08708d84ab888d0%7C809929af2d2545bf9837089eb9cfbd01%7C1%7C0%7C637341504003489320&sdata=GHBn6K9Yl7qaRU6tYzAEzymO3751Uczj51xB9c17Zm4%3D&reserved=0
or
https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fworldclockapi.com%2Fapi%2Fjson%2Futc%2Fnow&data=02%7C01%7Ctracy%40chapman.edu%7Ce1a2215e59904aaee08708d84ab888d0%7C809929af2d2545bf9837089eb9cfbd01%7C1%7C0%7C637341504003489320&sdata=psttxEnhMO6MjLyEv%2BchRopHyhLvgCxgqLT0JDPQVys%3D&reserved=0
The first one doesn't accept UTC as a timezone; it appears to want
etc/UTC instead. The second one is offline.
Duncan Murdoch
If both of those fail, you'll get the message you saw.
On 27/08/2020 1:23 p.m., John Fox wrote:
Dear r-package-devel list members,
I got the following note when checking two different packages today
--as-cran, both under R 4.0.2 and under R-devel, on my Windows 10 and
macOS Catalina systems, and on several platforms on rhub:
* checking for future file timestamps ... NOTE
unable to verify current time
I'm writing to inquire about the note because no one else has mentioned
this problem recently, in case it's produced by something that I'm
doing. There is a discussion of a similar problem from 2019 at
<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fpipermail%2Fr-package-devel%2F2019q1%2F003577.html&data=02%7C01%7Ctracy%40chapman.edu%7Ce1a2215e59904aaee08708d84ab888d0%7C809929af2d2545bf9837089eb9cfbd01%7C1%7C0%7C637341504003489320&sdata=GWnhngNH3UypXzbCzQOOwVHa8q87slWBhEW6n4PthGQ%3D&reserved=0>.
Both packages that I was checking are close to CRAN releases and so I'd
like to know whether I can disregard the note.
Any help would be appreciated.
John
______________________________________________
R-package-devel@r-project.org mailing list
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fr-package-devel&data=02%7C01%7Ctracy%40chapman.edu%7Ce1a2215e59904aaee08708d84ab888d0%7C809929af2d2545bf9837089eb9cfbd01%7C1%7C0%7C637341504003489320&sdata=rMlgTGg8rp7hxPhaiADuBl4%2FWSqGgx4wbKLIPgPS9o8%3D&reserved=0
- NOTE: This email originated from outside Chapman’s network. Do not
click links or open attachments unless you recognize the sender and know
content is safe.
NOTE: This email originated from outside Chapman’s network. Do not click
links or open attachments unless you recognize the sender and know
content is safe.
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
