"remove" does not work if some files have future modification dates

[JohanAR]

I'm running fclones on a large number of recovered files, and some of them have modification dates set in the future. This causes the remove command to issue a warning and skip the entire group. E.g.

[2024-05-09 12:26:24.833] fclones:  info: Started deduplicating
[2024-05-09 12:26:24.835] fclones: warn: File /mnt/storage/recovered/recup_dir.672/f1104357296.jpg was updated after 2024-05-09 12:21:38.782 +0200 (at 2046-01-07 07:30:51.000 +0100)
[2024-05-09 12:26:24.835] fclones: warn: File /mnt/storage/recovered/recup_dir.674/f1104745240.jpg was updated after 2024-05-09 12:21:38.782 +0200 (at 2046-01-07 07:30:51.000 +0100)
[2024-05-09 12:26:24.835] fclones: warn: Could not determine files to drop in group with hash ea68a9f1bb6b0c3553c228ec2dae5de0 and len 126225: Some files could be updated since the previous run of fclones

Would be nice if there was a flag to ignore this warning or similar.

[avioli]

This is simply another util - you can always grep them out - fclones ... | grep -v 'warn:' or fclones ... | grep -v 'at 20[3-9][0-9]'

[JohanAR]

Sorry I was unclear, it's not the warning message I want to get rid of, I want it to ignore the fact that the modification date is in the future and perform the operation anyway.

I worked around it by locating all files with incorrect modification dates and changing them. Would be more convenient if I could tell fclones to ignore future dates.