Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Here is sample messge from the log:
03/21/14 07:10:36 : counterpart of file Serif\PagePlus\xxxxxxxxxxxxxxxx.abc
does not exist in src folder, delete file.
But the file DOES exist in source folder. Why isn't the program reading it/
I should add that one of the destination folders is inside of another
destination folder. This shouldn't create a conflict if each pair is treated
separately, but I did figure it was worth mentioning.
And I should mention that when I right-click on the tray icon, and select "sync
now" then the folders are not working properly
Before it was both pair destination folders. But now it is only 1 pair that is
deleting/resyncing everything. I have no idea why.
Original comment by yourbest...@gmail.com
on 21 Mar 2014 at 12:34
I tried the older version and got the same error.
I then tried to use two separate folders as the destination folder for each
pair
\DropBox\subfolder\Pair1
\DropBox\subfolder\Pair2
This gives me zero re-writing bug :).
before I used
\DropBox\Pair1
\DropBox\Pair1\[folder]\Pair2
The bug STILL EXISTS in being able to organize my folders how I want. I may
only want to sync specific folders at specific subfolders. I shouldn't have to
create a separate folder. The sync algorithim should be smart enough to sync
such that I can re-use destination folder and subfolders within a destination
folder of a different pair.
I upgraded back to 1.1.5 . The workaround of using separate folders for each
destination pair AND making sure not to place a destination within a folder of
an existing pair seems to work for now. Thanks for giving us an easy method to
encrypt our files for backup easily.
PS: how does cryptsync store the password for each pair on the local computer
cryptsync is installed on?
Original comment by yourbest...@gmail.com
on 21 Mar 2014 at 4:27
I think this could be used to solve the problem:
https://github.com/secomba/base4k/tree/master/cs
Base4k was recently open sourced by the authors of Boxcryptor. It encodes
filenames tersely by making use of unicode. As a result, it shortens filenames
significantly, so that if you then encrypt them, you are still likely to be
under the 260 char limit.
I don't have time to try it, but hopefully you will find it helpful.
Original comment by cflow...@gmail.com
on 2 Feb 2015 at 4:22
Oh, sorry -- I liked to the C# version of Base4K, but they have provided CPP
and other languages as well.
Original comment by cflow...@gmail.com
on 2 Feb 2015 at 4:23
Sorry again! (It is late and my eyeballs are tired).
I meant to post this under the "filenames too long after being encrypted" issue.
Original comment by cflow...@gmail.com
on 2 Feb 2015 at 4:24
Original issue reported on code.google.com by
yourbest...@gmail.com
on 21 Mar 2014 at 12:07