I confirm with the new snapshot build (6.90.0.24--2018-03-30(d3aa7e90e7/a)
packages download and compile correctly and seconds->date &
file-or-directory-modify-seconds work as expected now.
Thank you for fixing the problem so quickly!
Greg
--
You received this message because you are
The time set by it is correct (current)
On Thursday, March 29, 2018 at 1:55:19 PM UTC+2, Matthew Flatt wrote:
>
> How about a direct use of `file-or-directory-modify-seconds`? Does
>
> (file-or-directory-modify-seconds "test-file" (current-seconds))
>
> on an existing "test-file" set the
How about a direct use of `file-or-directory-modify-seconds`? Does
(file-or-directory-modify-seconds "test-file" (current-seconds))
on an existing "test-file" set the timestamp on "test-file" to the
current time?
At Thu, 29 Mar 2018 04:38:23 -0700 (PDT), Greg Trzeciak wrote:
> You are right -
You are right - sample cached file I tried has a timestamp of 12:50 while
unpacked files frome cached are all with timestamp 13:50
On Thursday, March 29, 2018 at 1:29:11 PM UTC+2, Matthew Flatt wrote:
>
> At Thu, 29 Mar 2018 04:09:00 -0700 (PDT), Greg Trzeciak wrote:
> > Here are some tests
At Thu, 29 Mar 2018 04:09:00 -0700 (PDT), Greg Trzeciak wrote:
> Here are some tests and observations
> * The problem doesn't appear outside of raco pkg (ie: git clone uses
> correct dates, writing files from racket - also correct)
> * cache file for downloaded content is correctly timestamped
>
This is a continuation of the previous
thread: https://groups.google.com/forum/#!topic/racket-users/kYk-x5Zn5EE
the title of this one is more appropriate to the problem.
On my Windows 10 machine all packages are downloaded and the files are
timestamped +1h or +2h into the future (in
6 matches
Mail list logo
