skipping directory drive://xxxx

[jsavage]

This is a new install on Raspbian. I downloaded this foilder from github using git clone https://github.com/iwonbigbro/gsync.git cd gsync sudo easy_install --verbose gsync gsync drive://gsync ~/picam/gsync_files gsync ~/picam/gsync_files drive://gsync

have also tried

I have test101.png in googledrive gsync folder and test102.txt in picam/gsync_files folder I am expecting test102.txt to be copied fto google drive but instead, after a pause of 10 seconds or so I get the error message:
skipping directory drive://gsync

I get the same error if I specify the test file only as so: gsync drive://gsync ~/picam/gsync_files/test102.txt skipping directory drive://gsync

Presumably t have omitted something but this error message is not helpful enough,

[plecavalier]

That's because you need -r(recursive) to include directories and anything in them.

Thanks, Phil

On Wed, Aug 6, 2014 at 8:05 PM, James Savage notifications@github.com wrote:

This is a new install on Raspbian. I downloaded this foilder from github using git clone https://github.com/iwonbigbro/gsync.git cd gsync sudo easy_install --verbose gsync gsync drive://gsync ~/picam/gsync_files

I have test101.png in googledrive gsync folder and test102.txt in picam/gsync_files folder I am expecting test102.txt to be copied fto google drive but instead, after a pause of 10 seconds or so I get the error message:

skipping directory drive://gsync

I get the same error if I specify the test file only as so: gsync drive://gsync ~/picam/gsync_files/test102.txt skipping directory drive://gsync

— Reply to this email directly or view it on GitHub https://github.com/iwonbigbro/gsync/issues/74.

[jsavage]

Thanks Phil, I was not wanting subfolders to be synced so did not expect to use -r . Have made some progress but still not quite there yet. No errors but nothing is arriving and stats shown show nothing is being sent or received. See below I have one file in the root of what I want to sync: XXXX ~/picam/gsync_files $ ls -a . .. test102.txt Lets create a folder and a test file for that too XXXX ~/picam/gsync_files $ mkdir Testfolder XXXX ~/picam/gsync_files $ cd Testfolder/ XXXX ~/picam/gsync_files/Testfolder $ echo abcd > test104.txt XXXX ~/picam/gsync_files/Testfolder $ cd .. Now lets sync... XXXX ~/picam/gsync_files $ gsync -r -v ~/picam/gsync_files drive://gsync gsync_files/test102.txt gsync_files/Testfolder/ gsync_files/Testfolder/test104.txt sent 0 bytes received 0 bytes 0.00 bytes/sec Meanwhile in Google Drive the Testfolder turns up but no files from the root or within it. Is there some way I can see more detail on what it is doing?

[vinz486]

Hi, I have the same identical issue.

My suspect is that something goes wrong in RaspberryPi. May be due to ARM cpu?

[plecavalier]

I doubt it's the Pi at fault here. I had a similar issue about a mount ago on both my laptop and desktop. I deleting everything on Google's side and doing the first upload manually. After that, all new got sync'ed successfully and has been ever since. Never got to the bottom of it...

Thanks, Phil

On Thu, Aug 7, 2014 at 8:59 AM, Vincenzo Tarricone <notifications@github.com

wrote:

Hi, I have the same identical issue.

My suspect is that something goes wrong in RaspberryPi. May be due to ARM cpu?

— Reply to this email directly or view it on GitHub https://github.com/iwonbigbro/gsync/issues/74#issuecomment-51467617.

[jsavage]

By swiching on --debug i eventually found errors that are not being reported back to the screen.Trouble is that it is too risky to test safely against a google drive that has been in use for some time. it would be too easy to sudenly find other data damaged. I may come back to this but have just got something similar working with aws-cli. Seems just as flexible but not free in the long term. Thanks for confirming the issue though. On 7 Aug 2014 14:14, "Philippe LeCavalier" notifications@github.com wrote:

I doubt it's the Pi at fault here. I had a similar issue about a mount ago on both my laptop and desktop. I deleting everything on Google's side and doing the first upload manually. After that, all new got sync'ed successfully and has been ever since. Never got to the bottom of it...

Thanks, Phil

On Thu, Aug 7, 2014 at 8:59 AM, Vincenzo Tarricone < notifications@github.com

wrote:

Hi, I have the same identical issue.

My suspect is that something goes wrong in RaspberryPi. May be due to ARM cpu?

— Reply to this email directly or view it on GitHub https://github.com/iwonbigbro/gsync/issues/74#issuecomment-51467617.

— Reply to this email directly or view it on GitHub https://github.com/iwonbigbro/gsync/issues/74#issuecomment-51469240.

[oisalb]

A fix has been suggested in #66