Package Details: cryptomator-cli 0.6.2-1

Git Clone URL: https://aur.archlinux.org/cryptomator-cli.git (read-only, click to copy)
Package Base: cryptomator-cli
Description: CLI Multiplatform transparent client-side encryption of your files in the cloud.
Upstream URL: https://cryptomator.org/
Keywords: cryptography encryption
Licenses: GPL3
Submitter: SailReal
Maintainer: SailReal
Last Packager: SailReal
Votes: 1
Popularity: 0.130811
First Submitted: 2024-11-27 16:11 (UTC)
Last Updated: 2025-04-11 12:45 (UTC)

Latest Comments

kahi commented on 2025-04-19 12:08 (UTC)

Hi ! Thanks for maintaining this package.

Since the latest cryptomator-bin update fixed an incompatibility between fuse3 3.16 and cryptomator-cli 0.6.1, I have tried today to update cryptomator-cli to 0.6.2 and fuse3 to 3.17.

However the latest version of this PKGBUILD does not allow me to build cryptomator-cli anymore. Here are some relevant lines from the output :

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/cryptomator/cli/CryptomatorCli has been compiled by a more recent version of the Java Runtime (class file version 68.0), this version of the Java Runtime only recognizes class file versions up to 55.0
    [WARNING] The requested profile "linux" could not be activated because it does not exist.
    [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.5.0:exec (generate-autocompletion-script) on project cli: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
    ==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: cryptomator-cli-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
 cryptomator-cli - exit status 4

I've tried the previous PKGBUILD by only modifying the downloaded cryptomator-cli binary and its hash, to no avail. There seems to be a Java / Maven issue but I'm not very familiar with them.

I've also tried cryptomator-cli's binary release, which works on my system. However I've decided to stay with 0.6.1 using this package's previous PKGBUILD for now.

If you have any idea how to fix this or if I can provide more information, I'd appreciate it. Thanks again !