@zwastik
Ah, I see. I though you wanted to voice problems concerning the grive binary itself in your last comment.
Please file a bug report upstream or even submit a patch. All distributions will benefit from this getting fixed.
| Git Clone URL: | https://aur.archlinux.org/grive-git.git (read-only, click to copy) |
|---|---|
| Package Base: | grive-git |
| Description: | An open source Linux client for Google Drive with support for the new Drive REST API and partial sync |
| Upstream URL: | https://github.com/vitalif/grive2 |
| Keywords: | drive git Google share sync |
| Licenses: | GPL2 |
| Conflicts: | grive |
| Provides: | grive |
| Submitter: | ilpianista |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 78 |
| Popularity: | 0.000000 |
| First Submitted: | 2012-04-29 15:20 (UTC) |
| Last Updated: | 2023-01-23 14:25 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 11 Next › Last »
@zwastik
Ah, I see. I though you wanted to voice problems concerning the grive binary itself in your last comment.
Please file a bug report upstream or even submit a patch. All distributions will benefit from this getting fixed.
Now it does build successfully but service files have /usr/libexec path in them. Editing them solves the problem
@zwastik
Sorry, but I can't reproduce your error. Can you please recompile grive-git and try again? If the error persists, please file a bug report at https://github.com/vitalif/grive2 .
grive-changes@Drive.service: Failed at step EXEC spawning /usr/libexec/grive/grive-sync.sh: No such file
It is looking in /usr/libexec but archlinux uses /usr/lib
request failed due to auth token expired: 401 (body: ). refreshing token exception: /home/oiu7/.cache/pikaur/build/grive-git/src/grive-git/libgrive/src/json/JsonParser.cc(165): Throw in function void gr::JsonParser ::Parse(const char, std::size_t) Dynamic exception type: boost::wrapexcept<gr::JsonParser::Error> [gr::expt::BacktraceTag] = #0 0x555581c3d07a grive gr::Exception::Exception()
gr::DataStream*, gr::http::Header const&)
_cxx11::basic_string<char, std::char_traits\<char>, std::allocator\<char> > const&, gr::SeekStream, gr::DataStream, gr::http::Header const&, unsigned long long)
google getting uglier....
@jkendall solution in here https://github.com/vitalif/grive2/issues/287 gives the error below:
Failed to refresh auth token: HTTP 400, body: exception: /home/ozgur/.cache/yay/grive-git/src/grive-git/libgrive/src/protocol/OAuth2.cc(111): Throw in function void gr::OAuth2::Refresh() Dynamic exception type: boost::wrapexcept<gr::OAuth2::AuthFailed> [gr::expt::BacktraceTag*] = #0 0x563a4e0f868a grive gr::Exception::Exception()
I am unable to connect to my google account. I run grive -a and follow the link, but then I see: "Sign in with Google temporarily disabled for this app This app has not yet been verified by Google in order to use Google Sign in."
Is this happening for everyone else?
Maybe the more up to date package 'grive' (rather than 'grive-git') fixes the problem but I cannot install it due to an error during build.
Any ideas?
EDIT: I found the solution here: https://github.com/vitalif/grive2/issues/287
@tjc Last Friday, I had the same runtime error. I fixed it by using the workaround dikei posted, where a line is changed in PKGBUILD. Hopefully that works for you as well. cmake -DCMAKE_BUILD_TYPE=Release \ to cmake -DBoost_DIR=/usr/lib/cmake/Boost-1.71.0 \ https://pastebin.com/HFem07Qj
sorry, which comment (timezones are different). I am not getting the build error vlas commented about; I am getting a runtime error.
@tjc See dikei's comment below with timestamp 2019-10-19 01:21 for a workaround.
Pinned Comments
edh commented on 2022-09-20 20:45 (UTC)
This package has a bad record of not building. However, I am reluctant to patch a git-package because any changes would most likely break with any new upstream commit. Please try to get the build fixed upstream or switch to the grive package.