Package Details: pcloud-drive 1.14.8-1

Git Clone URL: https://aur.archlinux.org/pcloud-drive.git (read-only, click to copy)
Package Base: pcloud-drive
Description: pCloud drive. Electron edition.
Upstream URL: https://www.pcloud.com/
Licenses: custom
Replaces: pcloud, pcloud-git
Submitter: plague-doctor
Maintainer: rew1red
Last Packager: rew1red
Votes: 83
Popularity: 0.49
First Submitted: 2017-04-27 21:39 (UTC)
Last Updated: 2024-11-20 15:39 (UTC)

Required by (0)

Sources (2)

Pinned Comments

Zenzio commented on 2022-08-13 06:44 (UTC) (edited on 2022-08-13 06:45 (UTC) by Zenzio)

@cirlo I contacted their support when I had trouble running pCloud in Sway with GDK_BACKEND=wayland (without ",x11"). Their response was: "Unfortunately, we are having troubles updating the app to the latest electron versions because of inside security libraries that we are using. Our devs know about this issue and electron version update is already planed."

Latest Comments

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

shack commented on 2020-08-29 23:05 (UTC)

It appears that this package requires the fuse2 package.

$ pcloud                                                                                     
/opt/pcloud/resources/app/node_modules/backtrace-node/lib/backtraceClient.js:265                  
            throw e;                                                                              
            ^                                                                                     

Error: ENOENT: no such file or directory, open 'libfuse.so.2'                                     
    at Object.fs.openSync (fs.js:577:3)                                                           
    at Object.module.(anonymous function) [as openSync] (ELECTRON_ASAR.js:166:20) 
...

j0hannes commented on 2020-08-19 07:56 (UTC)

If you use grep on JSON output you rely on that API pretty printing it's output. If that changes at some point in time and compact JSON is delivered, the output would still be valid, but the PKGBUILD would fail. So it's certainly better to parse the output with jq or use another tool that understands JSON.

rew1red commented on 2020-08-18 23:50 (UTC)

I've attempted to remove jq as a build dependency since it seems to be the source of some reported trouble. Hopefully that helps some folks out.

tosziro commented on 2020-08-18 18:09 (UTC)

broken, cant update

rew1red commented on 2020-08-18 17:50 (UTC)

@fredlins This package does use the official appimage published by pCloud.

<deleted-account> commented on 2020-08-17 17:28 (UTC)

Why u not put oficial appimage? because your pkgbuild is broken

rew1red commented on 2020-08-17 15:21 (UTC) (edited on 2020-08-18 17:52 (UTC) by rew1red)

@fredlins I can't tell from your comment if your installation s failing to import GPG keys or failing to install jq. I'm assuming it's the former.

You might want to try each of these steps independently to see if there is a more localized issue.

gpg --keyserver keys.gnupg.net --recv-keys A8F7858263C1E39480B731DCEAD4F103068DF8E5

jq is available in the community repository, so you should be able to install it with pacman (or yay based on what I'm seeing in your comment).

<deleted-account> commented on 2020-08-17 15:10 (UTC)

You are distribute broken aur package

See:

==> Remove make dependencies after install? [y/N] y :: Downloaded PKGBUILD (1/1): pcloud-drive 1 pcloud-drive (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> N :: (1/1) Parsing SRCINFO: pcloud-drive

:: PGP keys need importing: -> A8F7858263C1E39480B731DCEAD4F103068DF8E5, required by: pcloud-drive ==> Import? [Y/n] Y :: Importing keys with gpg... gpg: keyserver receive failed: No name error: target not found: oniguruma error: target not found: jq  fredlins  ~  

rew1red commented on 2020-08-04 23:35 (UTC) (edited on 2020-08-12 15:43 (UTC) by rew1red)

@plague-doctor how would you feel about a direct-appimage install? It'd let us leverage AppImage for the packaging tool that it is and avoid having to make changes if the underlying AppImage ever changed.

I'm proposing this.

rew1red commented on 2020-07-28 15:49 (UTC)

You'd be rolling the dice on whether or not it would work on a retry, but it won't hurt to have.