gsync Usage: #71

lvbaal opened this Issue Jul 21, 2014 · 10 comments


None yet

6 participants

lvbaal commented Jul 21, 2014

After setting up gsync on a Lunix/Debian NAS I encounter an initial problem using gsync command; every command I give gsync gives Usage error, as for example in:

Skoskapet:~/Leo/tmp$ gsync --authenticate
gsync [options]... ...

What can be wrong?

xsbr commented Jul 27, 2014

Did you install using "pip"? gsync version 0.1.14 (on PyPi) is not the same from GitHub and it doesn't support "authenticate" yet.

If you wanna use GitHub version (development) use this:

git clone
cd gsync
python install

Same problem here. Why is there a difference between the pip installation and the installation with (the do show the same version after installation)?

semeion commented Nov 29, 2014

Same problem here, i am using Arch Linux, and installing from AUR:

Why need install using python? AUR provide a supervised installation in which allows me to easily remove all later. Why the authenticate need be maked in that weird way?

semeion commented Nov 29, 2014

My mistake, i have authenticated using the way/syntax '$gsync drive:/// ~/Google\ Drive/' and it work.


I installed the developer version hoping it'd fix my no files only directories issue but it hasn't. How can I uninstall the developer version easily?


If I recall correctly, you can use the same commands you used to install it, but replace "install" with "uninstall".


python uninstall
says its not found, what I ended up doing is installing it through pip, then uninstalling it through pip, hope that removed everything


Try doing "make uninstall" in the git directory, as root. It looks like the Makefile supports this, and it should clean things up much more cleanly than removing it with another version of the installer would.


root@:~/gsync# make uninstall
make: *** No rule to make target ,', needed byuninstall_,'. Stop.


Did you initially install it as root, or as your user? (I'm not a developer, so I'm largely taking shots in the dark, here.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment