Package Details: grive 0.5.3-2

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: 286
Popularity: 0.001399
First Submitted: 2012-04-29 22:26 (UTC)
Last Updated: 2023-01-23 14:24 (UTC)

Dependencies (12)

Required by (0)

Sources (3)

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 .. 29 Next › Last »

Crandel commented on 2022-06-19 11:46 (UTC)

@edh The problem was solved by removing cache directory. BTW, a lot of packages have minor updates when their dependencies was updated. For example bbswitch at the moment has version 0.8-513 which means it was updated 513 times without any changes in it sources. You can specify exact boost version and update grive PKGBUILD file every time boost will be updated

edh commented on 2022-06-18 14:27 (UTC)

@Pound_Hash Then you could have just asked that... Anyways, the important part of the comment is the "rebuild" part. The "problem" with packages in the AUR is that they link against whatever was installed when building the package and rebuilds are not coordinated between the AUR and Arch repos. In this case, back when you first built grive, it was linked against libboost_filesystem.so.1.78. At some point after that boost was updated and now grive links against the wrong version. You can fix this simply by rebuilding the package.

Because nothing about the PKGBUILD changes, I feel reluctant to update it. Hence, I used the word "local" to denote that the problem is solely on your end.

Pound_Hash commented on 2022-06-18 14:17 (UTC)

The problem is I don't understand what building locally means. I doubt this is the same as building manually. If not, what's the difference? Aren't all my builds done locally? I only ever use my own machine, never a remote one.

edh commented on 2022-06-17 20:54 (UTC)

@Pound_Hash Please read the comment that is literally right below yours! In the future it would make sense to do that before posting a new comment ;)

edh commented on 2022-06-15 14:39 (UTC)

@Crandel Please rebuild locally.

Crandel commented on 2022-06-15 11:03 (UTC)

Please update bin file to use boost 1.79

grive: error while loading shared libraries: libboost_filesystem.so.1.78.0: cannot open shared object file: No such file or directory

jasper1378 commented on 2022-06-03 21:13 (UTC)

@edh Thank you so much!

edh commented on 2022-06-03 20:25 (UTC)

Thanks for the comment. I fixed the checksum and am also now patching the source to compile again.

jasper1378 commented on 2022-06-03 13:16 (UTC) (edited on 2022-06-03 13:18 (UTC) by jasper1378) 

==> Validating source files with sha512sums...    
grive-0.5.1.tar.gz ... Passed
binutils_compilation.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!
-> error making: grive

When trying to install the latest version.

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