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.

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

@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!

@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.

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

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.

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

@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

The systemd files seem to end up in the wrong directory (see https://github.com/vitalif/grive2/issues/283). Running systemctl --user enable --now grive@$(systemd-escape google-drive).service (as it is specified in the README) results in Failed to enable unit: Unit file grive@google\x2ddrive.service does not exist. Is it possible to manually move them into the right directory?

For some reason it didn't work for me when i tried merely uninstalling grive, cleaning the cache, and reinstalling grive. Instead, I had to also remove all dependent packages (orphans) in addition to the preceding steps. Now it works.

@Crandel Sure but as outlined this mostly makes sense for binary packages that are managed together (bbswitch is in community) with the library that is being bumped.

I think hardcoding a specific library version is not a good idea because for one it blocks new users from installing the package for now good reason in the time it takes me to update the package and furthermore it would block system updates for all users of grive until the PKGBUILD is updated.