-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uppercase/Lowercase conflict with Box and option to rename. #54
Comments
Same conflict when running rclone and rclonesync on Windows. The issue is understood. I'll leave it open as a possible future enhancement. I'm curious how rclone itself handles this conflict. |
+1 to bump this enhancement request. I regularly sync Linux to Box. Linux paths are case sensitive, but Box is not. Case conflicts have caused me issues many times, when lsl file errors cause all future syncs to fail. If I run rclonesync in a scheduled cron job, it can be a long time before I notice the problem, by which time conflicts between local and remote directories have snowballed. |
Thanks for the bump. Unfortunately I'm holding off on non-critical work on rclonesync since the rclone team is incorporating rclonesync into the rclone proper as a new |
I was attempting to put a copy of all my Google Photo's onto Box so I can free the space on google which is getting full from email. I copied all the google photos down to my pc. In that directory were 2 files named "Smile.jpg" and "smile.jpg". On both Google Photo's and my local linux machine they are differentiated by the uppercase first letter on one. Uploading to box however causes a duplicate file conflict. Renaming it locally is easy enough but I ended up having to DELETE them from Google Photo's just to get the reoccuring sequence to stop (I should have stopped the every 30 minute syncs).
All that being said I wondered if a"rename on conflict" parm could be considered so it would modify the 2nd one slightly so both files got uploaded.
The text was updated successfully, but these errors were encountered: