Package Details: grive 0.5.3-3

Git Clone URL: https://aur.archlinux.org/grive.git (read-only, click to copy)
Package Base: grive
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 Google grive2 sync vitalif
Licenses: GPL2
Submitter: mrbit
Maintainer: edh
Last Packager: edh
Votes: 282
Popularity: 0.44
First Submitted: 2012-04-29 22:26 (UTC)
Last Updated: 2024-09-14 09:14 (UTC)

Dependencies (12)

Required by (0)

Sources (4)

Pinned Comments

edh commented on 2023-10-11 23:00 (UTC)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 30 Next › Last »

jasper1378 commented on 2023-01-23 13:38 (UTC)

@PillTime try temporarily downgrading boost-libs to 1.80.0.

PillTime commented on 2023-01-23 13:33 (UTC) (edited on 2023-01-23 13:36 (UTC) by PillTime)

'grive' fails to run due to 'boost-libs' version: grive: error while loading shared libraries: libboost_filesystem.so.1.80.0: cannot open shared object file: No such file or directory.

EDIT: rebuilding the package fixes it.

jasper1378 commented on 2022-09-21 12:31 (UTC)

Thank you @edh!

edh commented on 2022-09-21 07:41 (UTC)

@jasper1378 Thanks. I added your patch to the package.

jasper1378 commented on 2022-09-21 00:25 (UTC)

@edh here's a pull request I just created upstream that should fix the issue: https://github.com/vitalif/grive2/pull/371. Thanks for your help!

jasper1378 commented on 2022-09-20 20:53 (UTC)

@edh Sounds good, I'll look into making a patch that you can apply to the package. If that gentoo bug that I linked is correct however, it may not actually be a problem with grive.

edh commented on 2022-09-20 20:43 (UTC)

@jasper1378 I am happy to backport fixes to make the build work again if you can reference a patch.

jasper1378 commented on 2022-09-19 21:13 (UTC) (edited on 2022-09-20 13:57 (UTC) by jasper1378)

EDIT: Seems like there's an issue upstream referencing this: https://github.com/vitalif/grive2/issues/370

EDIT: Like the upstream issue mentioned, downgrading grep to 3.7 resolves the issue.

EDIT: Seems like it might actually a bug in libgcrypt-config. Take a look a this gentoo bug report: https://bugs.gentoo.org/868384

I'm getting the following error(s) when trying to build the latest version:


CMake Warning:
  Value of grive_LIB_DEPENDS contained a newline; truncating


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  fgrep: warning: fgrep is obsolescent" which has leading or trailing
  whitespace.  This is now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  -lgcrypt -lgpg-error" which has leading or trailing whitespace.  This is
  now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  fgrep: warning: fgrep is obsolescent" which has leading or trailing
  whitespace.  This is now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  -lgcrypt -lgpg-error" which has leading or trailing whitespace.  This is
  now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  fgrep: warning: fgrep is obsolescent" which has leading or trailing
  whitespace.  This is now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  -lgcrypt -lgpg-error" which has leading or trailing whitespace.  This is
  now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  fgrep: warning: fgrep is obsolescent" which has leading or trailing
  whitespace.  This is now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  -lgcrypt -lgpg-error" which has leading or trailing whitespace.  This is
  now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  fgrep: warning: fgrep is obsolescent" which has leading or trailing
  whitespace.  This is now an error according to policy CMP0004.


CMake Error at libgrive/CMakeLists.txt:74 (add_library):
  Target "grive" links to item " using grep -F

  -lgcrypt -lgpg-error" which has leading or trailing whitespace.  This is
  now an error according to policy CMP0004.

growleg commented on 2022-08-27 11:05 (UTC)

@edh Oh true, thanks a lot for your help. grave-changes@.timer doesn't exist though but grive-timer@.timer does. :-)

edh commented on 2022-08-26 09:15 (UTC)

@growleg The README is outdated. The service files are installed correctly however they are named grive-changes@.{service,timer}.

P.S. in the issue that you referenced the service files are enabled via systemctl --user start grive-changes@$(systemd-escape google-drive).service and not via grive@... :P