Package Details: google-drive-ocamlfuse 0.7.32-1

Git Clone URL: https://aur.archlinux.org/google-drive-ocamlfuse.git (read-only, click to copy)
Package Base: google-drive-ocamlfuse
Description: FUSE-based file system backed by Google Drive, written in OCaml
Upstream URL: https://astrada.github.io/google-drive-ocamlfuse/
Keywords: drive fuse google ocaml
Licenses: MIT
Submitter: mlq
Maintainer: pricechrispy
Last Packager: pricechrispy
Votes: 62
Popularity: 0.000015
First Submitted: 2013-10-14 21:44 (UTC)
Last Updated: 2024-03-25 01:51 (UTC)

Pinned Comments

pricechrispy commented on 2017-04-25 17:39 (UTC) (edited on 2022-10-16 06:40 (UTC) by pricechrispy)

Before you flag this package out-of-date:

According to the official project page: https://astrada.github.io/google-drive-ocamlfuse/

Find latest release versions here: https://launchpad.net/~alessandro-strada/+archive/ubuntu/ppa

The latest releases are not all tagged versions on GitHub.

For the latest development versions on git, try: https://aur.archlinux.org/packages/google-drive-ocamlfuse-git

OLD official project page: http://gdfuse.forge.ocamlcore.org/

OLD release versions here: https://forge.ocamlcore.org/frs/?group_id=305

Latest Comments

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

emild commented on 2023-07-01 22:57 (UTC) (edited on 2023-07-01 23:10 (UTC) by emild)

For some uploads (not large ones) I see in the log:

[226.130625] TID=0: BEGIN: Uploading file (id=154, path=/.shared/......................
[240.214013] TID=1: Flushing DB...done
[406.853707] TID=0: Error during request: Code: 65, Description: CURLE_SEND_FAIL_REWIND, ErrorBuffer: necessary data rewind wasn't possible
[406.853720] TID=0: Giving up

Then the file looks like it's uploaded in a file manager, but when looking in Google Drive, it's got 0 bytes. A massive pain because now I wonder if each file was uploaded or not.

This is with 0.7.30.

Edit: raised bug upstream - https://github.com/astrada/google-drive-ocamlfuse/issues/820

pricechrispy commented on 2023-03-02 06:00 (UTC)

@krvkir This package builds. The error you receive is from a dependency "camlidl". Currently this dependency has issues building: https://aur.archlinux.org/packages/camlidl

@vmartins The error you receive is from a dependency "ocaml-cryptokit". Please apply the patch mentioned in this comment https://aur.archlinux.org/packages/ocaml-cryptokit#comment-885368

vmartins commented on 2023-03-01 17:50 (UTC) (edited on 2023-03-01 17:50 (UTC) by vmartins) 

==> Starting package()...
dune: option '--libdir': the path must be absolute to avoid ambiguity
Usage: dune install [OPTION]… [PACKAGE]…
Try 'dune install --help' or 'dune --help' for more information.
==> ERROR: A failure occurred in package().

krvkir commented on 2022-12-06 11:22 (UTC) (edited on 2022-12-06 11:23 (UTC) by krvkir)

Couldn't build it today:

ranlib: ./libcamlidl.a: error reading comerror.o: file truncated
make[1]: *** [Makefile.unix:20: libcamlidl.a] Error 2
make[1]: Leaving directory '/home/krvkir/.cache/yay/camlidl/src/camlidl-camlidl109/runtime'
make: *** [Makefile:19: all] Error 2

Neither this package nor the -git one builds.

sunplan commented on 2022-05-11 06:28 (UTC)

It seems that /usr/doc should be /usr/share/doc.

sgt-hartman commented on 2022-02-03 19:18 (UTC)

@snakeroot

Thank's for reporting this. Unfortunatelly the error pointed by the issue is installation on Manjaro through Pamac, which seems to use AUR as a backend. I don't think this is an upstream issue.

snakeroot commented on 2022-02-03 18:49 (UTC)

@sgt-hartman / @dangpzanco

Note that this has been reported as an issue in upstream's GitHub:

https://github.com/astrada/google-drive-ocamlfuse/issues/750

sgt-hartman commented on 2022-01-25 08:08 (UTC) (edited on 2022-01-25 08:10 (UTC) by sgt-hartman)

I have the same issue as @dangpzanco:

==> Starting build()...
File "src/drive.ml", line 478, characters 15-31:
478 |     match file.File.resourceKey with "" -> None | _ as s -> Some s

Error: Unbound record field File.resourceKey
==> ERROR: A failure occurred in build().
    Aborting...

That's right each time this package is upgraded the process is not really as smooth as it should be, it breaks because of compiler version mismatches or something. But on the other hand, as a simple user, it really bother me to install specific programming languages tools only to install a package. Theses tools tend to pollute $HOME directory and you have to remember to look for updates by yourself. Maybe this package could be refactored to use theses tools "internally" during the build ?

dangpzanco commented on 2022-01-21 05:54 (UTC) (edited on 2022-01-21 06:12 (UTC) by dangpzanco)

I think @JayKobe6k's suggestion is the easiest way of installing and keeping this package updated. Here's what I did to install this:

Remove google-drive-ocamlfuse and its dependencies (this is necessary to have a clean install of ocamlbuild via opam) and install opam via pacman (this will also reinstall ocaml, see instructions here). Then you may run:

> opam init
> eval $(opam env)
> opam install google-drive-ocamlfuse

opam init creates a folder at ~/.opam, where it keeps the google-drive-ocamlfuse executable and other stuff. It will ask to be added to your ~/.zshrc or ~/.bashrc script. Seems to be really easy to use, kinda like cargo (Rust), npm (JavaScript) and conda (Python).

areaman commented on 2022-01-21 03:46 (UTC)

I received this message when I tried to update this to the latest version:

==> Starting build()... File "src/config.ml", line 1: Error: The files src/.google_drive_ocamlfuse.objs/byte/utils.cmi and /usr/lib/ocaml/curl/curl.cmi make inconsistent assumptions over interface Curl ==> ERROR: A failure occurred in build(). Aborting...

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