Thank you for the clarification!
Search Criteria
Package Details: grive 0.5.3-3
Package Actions
| 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.123006 |
| First Submitted: | 2012-04-29 22:26 (UTC) |
| Last Updated: | 2024-09-14 09:14 (UTC) |
Dependencies (12)
- boost-libs
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- expat (expat-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- json-c (json-c-gitAUR)
- libgcrypt
- yajl (yajl-gitAUR)
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR) (make)
- binutils (optional) – backtrace and libiberty
- cppunit (optional) – unit tests
- inotify-tools (inotify-tools-gitAUR) (optional) – scheduled syncs and syncs on file change events
Required by (0)
Sources (4)
Felixoid commented on 2018-09-21 14:58 (UTC)
edh commented on 2018-09-20 03:30 (UTC)
@Felixoid As stated in the commit message, I update the pkgrel whenever boost-lib is updated. I might have gotten a little bit to cautious with doing so but in the past grive broke on several occasions when being build with an older version.
Felixoid commented on 2018-09-19 08:20 (UTC)
Hello. Why do you randomly update package release?
lybin commented on 2018-08-09 12:11 (UTC)
==> Checking for packaging issues... ==> WARNING: Package contains reference to $srcdir usr/bin/grive
simonszu commented on 2018-06-27 05:23 (UTC)
@edh I have switched to grive-git. This worked.
edh commented on 2018-06-25 18:07 (UTC)
@simonszu Just rebuilding the package should be sufficient.
simonszu commented on 2018-06-25 17:49 (UTC)
grive: error while loading shared libraries: libjson-c.so.3: cannot open shared object file: No such file or directory
Problem is: this grive package has json-c as a dependency, but according to https://www.archlinux.org/packages/core/x86_64/json-c/files/ the header files are now called libjson-c.so.4. Is this something you can fix, edh? Or should i file a bug in grive upstream?
edh commented on 2018-01-08 20:10 (UTC) (edited on 2018-01-08 20:11 (UTC) by edh)
@beliy
It is not my decision to make whether to tag a new release or not. This is purely a choice of the upstream developer with which I will not interfere. Feel free to use the git version (grive-git) if you do not want to track the current release but the master of the git repository instead.
bko commented on 2018-01-08 19:20 (UTC)
please replace source to https://github.com/vitalif/grive2/archive/master.zip, because https://github.com/vitalif/grive2/archive/v0.5.0.tar.gz is very old
r08 commented on 2017-12-13 00:33 (UTC)
Such a nice little tool. Such a tragedy that it depends on boost-libs....
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
pacmanand grive need to be made aware of this by rebuilding it.