1.67 behaves correctly unless a directory flag, specifically --create-empty-srs-dirs, is included. then it goes after the entire destination file system again like 1.66. switching back to 1.65.2 fixes the issue and simply processes the destination with the --create-empty-srs-dirs flag. i will use 1.65.2 for now. thank you
hey @asdffdsa what do you mean with this? backwards compatibility with what?
@ncw if i may, i think syncing empty directories is the correct mode of being. since rclone is a "sync" utility, it should "sync" as accurately as possible. i think the people who don't want such precise accuracy can then use a flag to switch it off for their specific use case.
since rclone has sooooo many file systems/remotes it supports, it is reductionist to think that anybody using it will want certain elements of a sync skipped by default. just because a directory is empty at the time of a sync, will not always mean it's pointless. it could be a cache folder that will cause an application on the other end to stop working if the directory is missing. that's just one of millions of scenarios that could appear. in your position, i'm certain you can think of a ton more.
i don't exactly know what my issue on this topic here is, since 1.66 finds tens of thousands of directories that need their mod times updated, where 1.67 finds none of the such. unless certain default settings changed from 1.66 to 1.67. but millions of files would need to be resynced with their modtimes now included in rclone, i would just bite that bullet.
but that's all just my two cents worth 
That was my thinking, but the people spoke quite loudly about v1.66 so I changed it back to the old behaviour in v1.67 by default.
Rclone has thousands of users and we try not to make backwards incompatible changes - that is the price of success I'm afraid!
New Rclone user here. Thank you so much for that great work.
As I was browsing here to build up my rclone knowledge, I was quite surprised to find this thread. I mean, if I sync something, I would expect to have the destination as similar as possible to the source after. including empty directories. rsync would do it.
Looks like I have to add create-empty-src-dirs to my scripts as I can't risk scenarios like applications not running because they can't find their cache or log dir then in an environment that has been synced before.
So without wanting to scratch on old wounds or something like that 
I really believe the default should be including empty dirs.
ppl tend to voice themselves about basically any change they encounter 
but I was taken by surprise too. I did an update and all of a sudden rclone decides there are a few hundred thousand changes to sync. in my case, we had just moved to a new server and my file corruption antennas were extra ordinarily high.
maybe it would just need a better introduction. because I'm not sure how many people actually comb through the release notes in detail when a new version is released.
however, you're selling a product here, and the existing user base is obviously of paramount importance. thanks for the amazing product thus far
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.