Gdrive: What happened to the precompiled binaries?

Created on 29 Jul 2020 · 7Comments · Source: prasmussen/gdrive

I downloaded gdrive two days ago for my personal laptop and was impressed by its simplicity. When I logged in today to download the binary for a VM, suddenly I can't find the downloads anymore! What's going on?

Source

dtch1997

Most helpful comment

I use an encrypted refresh token that was generated quite a while ago, for authentication, but yes, I'm still able to deploy my Travis/Appveyor builds to my personal Google drive with a recently built gdrive binary.

Not sure what would happen if I needed to authenticate all over again, but it works for now (and I'm not looking to reinvent the wheel).

I used to download it directly from here for my continuous integration needs, but now I just build it for Mac & Windows myself and upload it where CI can get at it.

A note that the binaries were pulled because Google won't verify them might be in order. Otherwise... it just seems like they were pulled because the source is no longer being maintained.

dougmassay on 3 Aug 2020

👍2

All 7 comments

Putting a pretty serious damper on my Appveyor deployment strategy with these missing. Some detailed instructions on how to build for Windows would be greatly appreciated.

dougmassay on 29 Jul 2020

Turns out building is relatively simple, but "un"-releasing perfectly good binaries still seems like an odd thing to do, in my opinion.

dougmassay on 30 Jul 2020

I removed the binaries because I didn't think they were usable anymore. The app is not verified by google, so it's not possible to get the verification code for new installations. Are you saying it is working for you?

prasmussen on 3 Aug 2020

😕1

Not sure what would happen if I needed to authenticate all over again, but it works for now (and I'm not looking to reinvent the wheel).

I used to download it directly from here for my continuous integration needs, but now I just build it for Mac & Windows myself and upload it where CI can get at it.

A note that the binaries were pulled because Google won't verify them might be in order. Otherwise... it just seems like they were pulled because the source is no longer being maintained.

dougmassay on 3 Aug 2020

👍2

had the same issue, you can still find the binaries linked to some google drive in the 2.1 tagged branch readme: https://github.com/prasmussen/gdrive/tree/2.1.0

elm- on 4 Aug 2020

👍1

Just note that 2.1.0 is NOT last version (which is still named as 2.1.0), linux and windows.

You can try run help command and see if serviceAccout is there as option:

/gdrive help list
List files
gdrive [global] list [options]

global:
  -c, --config <configDir>             Application path, default: /root/.gdrive
  --refresh-token <refreshToken>       Oauth refresh token used to get access token (for advanced users)
  --access-token <accessToken>         Oauth access token, only recommended for short-lived requests because of short lifetime (for advanced users)
  --service-account <serviceAccount>   Oauth service account filename, used for server to server communication without user interaction (filename path is relative to config dir)

....
./gdrive version
gdrive: 2.1.0
Golang: go1.15.2
OS/Arch: linux/amd64

(at those link there are just 3 options for global, and serviceAccount is missing)

xsoft on 2 Oct 2020

I removed the binaries because I didn't think they were usable anymore. The app is not verified by google, so it's not possible to get the verification code for new installations. Are you saying it is working for you?

I'm perfectly able to still use gdrive with a token generated a while ago, sometime last year, so the binaries are definitely usable in such specific cases. That's why I'd also like to see them back up - regardless of whether they work or not anyway, it doesn't hurt anyone. If they ever were to completely cease working properly, people can still move to alternatives like rclone but gdrive is honestly simple enough and gets the job done.