[Octave-bug-tracker] [bug #64933] Stat sometimes produces wrong timestamp

[Markus Mützel]

Follow-up Comment #7, bug #64933 (project octave):

I'm not sure which one is right. It could be that the following is happening:
- That powershell command sets the modification time with the *current* time
zone.
- The local time zone of the user changed by one hour (presumably from UTC+2
to UTC+1) between the date that they set and today. That means 12:00 UTC+1 is
11:00 UTC today, but 12:00 UTC+2 was 10:00 UTC back then.
- The mtime in the stat structure is taken since an EPOCH (and doesn't care
about time zones). `localtime` converts it to the user's *current* time zone.
So, the mtime appears to be one hour off (early).

If that is the case, stat(fid) might be wrong.

But it's probably also possible that something else is going wrong...


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64933>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/