-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grive does not work #310
Comments
Grive is using an API for Drive that was deprecated in 2012 and finally turned off today. It looks like they stopped maintaining this project and haven't migrated it to the supported API since there are earlier tickets on this issue tracker asking about the API deprecation that went unanswered. |
you might find https://github.com/astrada/google-drive-ocamlfuse a useful replacement ... I am |
Same problem for me, and I guess everyone. I will look at the ocamlfuse one. |
check out a python alternative: https://github.com/iwonbigbro/gsync |
I've chosen to use https://github.com/odeke-em/drive |
Are the maintainers still around (is there a chance it could be ported to a new API)? |
After 2 days of browsing the issue I found now why. Colinkeenan is this woks like grive? Thanks guys for your guidance, |
@Cilke After installing, initializing, and getting through the first run, "drive push" works essentially the same as grive. It has many other functions though, and you will need to read the documentation to at least get the directory initialized: https://github.com/odeke-em/drive#drive |
I was told by the author of a grive fork that corrects this issue where to find it .. and it appears to work fine (not that I've checked the diff - all I can say of the source is that certain compile issues in the original are also corrected, so recent maintenance work has definitely been done and configure and compile now goes very smoothly under gcc 4.9 on debian stable):
|
@pbreuer thanks for this great news! I will give a try right now. Have a safe weekend! Cheers! |
@colinkeenan Thanks for your guidance too! |
I have been using Grive for long time. It worked perfectly. But today it says:
Reading local directories
Synchronizing folders
exception: /build/buildd/grive-0.2.0/libgrive/src/http/CurlAgent.cc(149): Throw in function long int gr::http::CurlAgent::ExecCurl(const string&, gr::http::Receivable*, const gr::http::Header&)
Dynamic exception type: N5boost16exception_detail10clone_implIN2gr4http5ErrorEEE
std::exception::what: std::exception
[PN2gr4expt6MsgTagE] =
[PN2gr4http11CurlCodeTagE] = 0
[PN2gr4http15HttpResponseTagE] = 400
[PN2gr4http6UrlTagE] = https://docs.google.com/feeds/default/private/full/-/folder?max-results=50&showroot=true
[PN2gr4http9HeaderTagE] = Authorization: Bearer ya29.WwGWXdYnw_iNWNJeXTO4sZHnmEzwqFFoqJN1HjHPzyMki2xvcGPIOG8ADE6XvsHHE9X48pw_UTSKDA
GData-Version: 3.0
What does it mean? What should I do in order to repair it?
Thank you very much.
The text was updated successfully, but these errors were encountered: