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 - 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 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 > > > * package folders are correctly timestamped > > > * files inside of those folders have timestamp +1h or sometimes +2h into > > > the future > > > > Thanks for working to narrow this down! > > > > It sounds like the problem might be related to the ".tgz" unpacker. If > > you use `file/untgz` to unpack the cache file for download content, > > does that produce the wrong timestamp on unpacked files? > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
