Touching files not working when writing to NAS

[JxxIT]

Describe the bug
When using --touch some files don't get their date changed.

To Reproduce
Export any image to a nas, and see that it didn't touch the file

Expected behavior
The file date changed

Screenshots

Desktop (please complete the following information):

• OS: macOS 15.2.0, arm64
• osxphotos version 0.69.2

Additional context
#1819

[oPromessa]

@RhetTbull Would it make sense to report that os.utime on Python 3.12 (and 3.13 as I tested it also) on MacOS 15.3.2 with NAS Synology 7.2.2 does not work properly?

• I will report it with Synology in case it's their issue.
• I can also try with Apple

[RhetTbull]

@oPromessa perhaps but it's not clear to me where the problem lies. With Python? (doubtful as it uses the system utime), with macOS? or with Synology? Is it an intermittent failure? (Works sometimes but not others)? If so, osxphotos could work around this by testing the result and retrying until it "sticks". This would of course slow down the export quite a bit so would have to be an option.

[JxxIT]

I think I may found a fix, I'll investigate.

[JxxIT]

I fixed it!!! PR coming soon!

[oPromessa]

That's superb. I've made a simple "os.utime" update .py to test out and it does have a different behaviour from "osxphotos".

• osxphotos os.utime does perform the change (as confirmed via stat on the command line) but after a minute or so, the date is set to the current date -- This was the behaviour I had when osxphotos was touching files with a date prior to Unix epoch: since then fixed by Synology like a year or so ago!
• my small .py test program is able to apply os.utime and the change "sticks"-- which is really strange as it is using the same os.utime function. The same python 3.12.9 and the same import os module!

Only difference I see is that osxphotos creates the file and applies os.utime immediately after, and my .py test is applying os.utime on the file already created (a few minutes before) by osxphotos.

Curious how you fixed it 😄

[JxxIT]

My PR fixes it for new exports, but is there a command that only touches the already exported files? Or a way to do this in python? I don't really want to export my whole library again :)

Edit: found it

[RhetTbull]

@all-contributors please add @JxxIT for bug, code

[allcontributors]

@RhetTbull

@JxxIT already contributed before to bug, code