syncing issue about grive

[nestal]

This is a bug and need to be fixed. I will take a look.

Meanwhile, you can use the -f option to make grive thinks the remote is always newer.

[voyager123bg]

Thanks for your quick response...

One further thing I noticed there is no "--help" option in latest version
(9 jun 2012) and the only options grive suggested is "-a" if it is not
initialized in the current work directory.

Best Regards,
Nikolay

On Tue, Jun 12, 2012 at 5:18 PM, Nestal Wan <
[email protected]

wrote:

This is a bug and need to be fixed. I will take a look.

Meanwhile, you can use the -f option to make grive thinks the remote is
always newer.

---

Reply to this email directly or view it on GitHub:
#61 (comment)

[nestal]

Thanks for the report. I am able to reproduce this.

This is a blocker for v0.1.2. I will fix it before rolling out v0.1.2

[nestal]

It should be fixed. Please re-test.

The new --dry-run option also helps.

[nestal]

Any update?

[nestal]

Assume this is fixed as there's no further update.

Hi, I am still seeing this issue.
grive version 0.2.0 Jul 20 2012 13:27:42
From ubuntu repository 0.2.0-1+git20120720webupd8precise

Steps to reproduce:

1. From a Windows laptop copy a file (dated April 2012) into my Google Grive
2. Activate sync on the Windows laptop
3. Run grive on my local desktop

Observed results:
Reading local directories
Synchronizing folders
Reading remote server file list
Detecting changes from last sync
Synchronizing files (dry-run)
sync "./testfolder/testfile.txt" deleted in local. deleting remote
Finished!