search for: timestanps

I've now got scripts that correctly backup all my primary partitions to a second drive. The original problem was that I copied them over without a time stamp, so that the first rsync run found no timestamps and wanted to copy them all over again. So I used: 'rsync -r -t -v --size-only $SOURCE $TARGET' My question is this: do I need to continue to use --size-only, or has the

Dear developers, Upon CRAN submission I have bumped into "future file timestamps" warning that I can't solve. I have updated the package as usual, and all checks go through in my system. CRAN reports the following warning however. * checking for future file timestanps ... WARNING Files with future time stamps: DESCRIPTION NAMESPACE README.md The build log is at https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.7_20180920_004954/Debian/00check.log The package is at https://github.com/rOpenGov/eurostat/ I did not find guidance (search engin...

...Upon CRAN submission I have bumped into "future file timestamps" warning > > that I can't solve. I have updated the package as usual, and all checks > go > > through in my system. CRAN reports the following warning however. > > > > * checking for future file timestanps ... WARNING > > Files with future time stamps: > > DESCRIPTION > > NAMESPACE > > README.md > > > > The build log is at > > > https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.7_20180920_004954/Debian/00check.log > > > >...

...ve bumped into "future file timestamps" warning > > > that I can't solve. I have updated the package as usual, and all checks > > go > > > through in my system. CRAN reports the following warning however. > > > > > > * checking for future file timestanps ... WARNING > > > Files with future time stamps: > > > DESCRIPTION > > > NAMESPACE > > > README.md > > > > > > The build log is at > > > > > https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.7_20180920_00495...