this is not a bug report, more a question about how pyftpsync works.
What is the intended behaviour of pyftpsync on the first run (no meta data file yet stored in sync folders) and a file on remote and local side does not match in modification timestamp and size?
I would expect that pyftpsync detects a conflict and asks the user how to resolve this. However, when I tested various scenarios, it seems that the younger file wins and it is being copied without confirmation to the other side?
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.
Hi,
this is not a bug report, more a question about how pyftpsync works.
What is the intended behaviour of pyftpsync on the first run (no meta data file yet stored in sync folders) and a file on remote and local side does not match in modification timestamp and size? I would expect that pyftpsync detects a conflict and asks the user how to resolve this. However, when I tested various scenarios, it seems that the younger file wins and it is being copied without confirmation to the other side?