good morning, a long time ago I opened a post with this problem but since it was not the time change it was difficult to find the problem, today it was the time change to summer the clock was advanced 1 hour, the problem is that I copied some files in function of the time they were created, these are the parameters
If it is done at the same time and that is the problem with the automatic time change, the program does not adjust with the time change, is there a way to take the time from the system and not from the TZ?
Good afternoon, the timezone of Spain is +1, in winter it works well because the time does not change but in summer the clock is advanced 1 hour and this is when the problem starts, if I do not put any timezone by default it takes it as tz 0
the correct time would be 10:16:00
TZ +1
11:16:00
TZ+2
10:16:00 now it's ok because by advancing the clock 1 hour it thinks it's TZ2
TZ0 or without TZ
12:16:00
the file system is in c: and in this case it is a windows 10 professional but the same happens with windows 7, the program does not take the time of the computer as a reference, something very strange
Thank you
good afternoon, I will try this way, I use it in bath but I can try to modify it to extract only the time zone since I use the date for other things and the rclone format is different
Thanks a lot
Good afternoon, now I put the poweshell parameters that Ole Frost put and for the moment with that I can solve, as soon as I have a moment I will try the rclone beta to see if the problem is solved
good again, I tried the beta version removing the TZ and now it seems to work fine
rclone64.exe copyto "e:\backups" "e:\esync\Marc\13" --local-no-check-updated --no-traverse --max-age "2022-03-27T10:16:00"
2022/03/28 19:20:45 DEBUG : --max-age 1.3783095153564815d to 2022-03-27 10:16:00 +0200 CEST m=-119085.732895899
before it took by default the TZ 0
In any case, I will continue testing once the programming is finished
thank you very much to all
I agree, the code should be fixed to behave as described in the docs and the standard. It may brake a few scripts and silently fix some others. It however seems like the absolute local time options are seldomly used, otherwise we would have discovered this issue years ago. I therefore doubt we will see any issues/complaints.
I guess this cute little signature bug sneaked in during a long dark winter somewhere near Greenwich
Thanks for testing. I've merged this to master now which means it will be in the latest beta in 15-30 minutes and released in v1.59
I agree - thank you.
Ha! If I walk up the local hill on a very clear day I can see Greenwich! And I will admit that living in GMT for half the year does mean I've made that mistake before. However the cause of this particular problem was that I put the the test vectors for that bit of the code in UTC instead of localtime - duh!
Anyway, in rclone, times without timezones are always localtime is what I try to stick to.