Open dlakata opened 9 years ago
I've also run into this issue.
I would also like to see this. I was partially asking this in #287.
Hello @dlakata, welcome to drive and thank you for reporting this issue.
That's curious because I thought this issue has been fixed in https://github.com/odeke-em/drive/issues/262. Please run:
$ go get github.com/odeke-em/drive-gen && drive-gen
$ drive version
to give me the commit information. Thank you.
drive version: 0.2.7
Commit Hash: '9990f32e38b13e8461a049b2fefa16ff447f55f0'
Go Version: go1.3.3
OS: linux/amd64
BuildTime:
Thank you for this information. I'll try debugging it later when I jump back to programming. For now to avoid this issue blocking you, you could rename the clashing files drive rename <src> <dest>
or ignore-clashes(this option though might mean that your data will go to the first greedily matched dir).
You can overwrite with --ignore-name-clashes
Any idea on when you could look at this item?
Is passing --ignore-name-clashes not working for you?
It works but how am I supposed to know beforehand what clashes exist? My assumption would be that these should be listed in drive diff
without a -ignore-name-clashes flag
Hey folks, I was wondering if y'all could try this again.
Please get the latest from master as I've done some work in https://github.com/odeke-em/drive/pull/528.
I just had this issue where it reports clashes but doesn't list anything. Looking through what it was going to push, I saw a ton of stuff that I haven't touched in almost 2 years. Looking at that directory in the web browser, I saw that everything had been duplicated, recursively, for no reason. I deleted the whole directory through the web browser and then pushed it back up using drive.
Postponed to v0.3.7 to pave way for the integration of the new end to end encryption package.
I'm trying to set up drive, and
drive pull
is giving me a bunch of name clashes. I think this is helpful, but it's annoying that drive aborts when it finds clashes in a directory. After I resolve the clashes, I have to rerundrive pull
, which then finds more clashes in another directory and aborts again.Would it be possible for drive to list all the clashes? This could either be a command like
drive clashes
that lists all the current clashes, ordrive pull
could have an option to show all the clashes, without aborting.