Arch Linux User Repository

If you encounter errors similar to error [...] loading shared libraries, you most likely need to rebuilt the grive package. Usually no further action is needed except for forcing a rebuilt.

The error is due to grive having been built against an older version of the library mentioned in the error message. The library has likely since been updated by pacman and grive need to be made aware of this by rebuilding it.

For 0.5.1-1:

CMake Error in libgrive/CMakeLists.txt:
  Imported target "Boost::unit_test_framework" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in libgrive/CMakeLists.txt:
  Imported target "Boost::unit_test_framework" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in libgrive/CMakeLists.txt:
  Imported target "Boost::filesystem" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



CMake Error in libgrive/CMakeLists.txt:
  Imported target "Boost::filesystem" includes non-existent path

    "/include"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.



-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.
==> ERROR: A failure occurred in build().
    Aborting...
The build failed.

Tested and confirmed to work. I just missed that one needs to enable google drive for the API project, and generate the certifications for it on the project... Also when running "grive --id bla --secret blu -a" to get 1st access, one needs to enable access to grive2, and in order to do so, in the accessing web page, one needs to do the "unsafe" authorization on "advanced"...

Not quite fixable: https://github.com/vitalif/grive2/issues/287, but seems like there's a workaround by manually creating a concole APIs project on google for grive2. Look for @davama comments there. Perhaps one can create an alias for "grive --id bla --secret blu"... Haven't tested it yet, but others seem to have confirmed it works...

BTW, if the @davama on github is the same as the @davama in AUR that commented here, thanks a lot !!!

I have same @je-vv issue, how to fix it?

@davama, how did you install v 0.52-dev? there does not seem to be a AUR package for it

No change with latest master branch :-1:

grive -v
grive version 0.5.2-dev Nov 15 2019 15:25:07

Same as @jev-vv

updated grive to 0.5.1-1

had to remove .grive and .grive_state

ran grive -a and got the:

Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.

It is interesting that it says "grive2"...

Same thing here.

As I got oauth failure:

Failed to refresh auth token: HTTP 401, body: exception: /home/vasqueja/.cache/aurutils/snapshot/grive/src/grive2-0.5.1/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 0x559c9e093d7c grive gr::Exception::Exception()

<h1>1 0x559c9e0892ea grive gr::OAuth2::AuthFailed::AuthFailed()</h1> <h1>2 0x559c9e088f24 grive gr::OAuth2::Refresh()</h1> <h1>3 0x559c9e089115 grive gr::OAuth2::OAuth2(gr::http::Agent*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)</h1> <h1>4 0x559c9e03947b grive Main(int, char**)</h1> <h1>5 0x559c9e037369 grive main</h1> <h1>6 0x7fe96847a153 /usr/lib/libc.so.6 __libc_start_main</h1> <h1>7 0x559c9e037e9e grive _start</h1>

Then I tried removing ".grive", and "grive -a", and after logging in I got the message:

Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In.

Weird enough is that when attempting to login, the app showed up as grive2. Then I checked on google security, and grive was actually authorized. I'm not sure if the "grive2" app name is the issue...

I'm having issues connecting it to google, google says that the app has not been verified and that logins are disabled, is this normal?