@SailReal once again came and solved the issue (https://github.com/cryptomator/cryptomator/issues/1658): make sure to use zulu-16-bin
or amazon-corretto-16
. With jdk-adoptopenjdk
or aur/jdk
you will encounter problems when trying to lock the vault.
Search Criteria
Package Details: cryptomator 1.14.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cryptomator.git (read-only, click to copy) |
---|---|
Package Base: | cryptomator |
Description: | Multiplatform transparent client-side encryption of your files in the cloud. |
Upstream URL: | https://cryptomator.org/ |
Keywords: | cryptography encryption |
Licenses: | GPL3 |
Submitter: | Foxboron |
Maintainer: | ajgraves (overheadhunter, SailReal, as.skymatic) |
Last Packager: | as.skymatic |
Votes: | 81 |
Popularity: | 0.48 |
First Submitted: | 2016-04-03 17:36 (UTC) |
Last Updated: | 2024-11-19 11:41 (UTC) |
Dependencies (10)
- alsa-lib
- fuse3 (fuse3-gitAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libnet (libnet-gitAUR)
- libxrender
- libxtst
- maven (mvnvmAUR) (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
- keepassxc-cryptomatorAUR (optional) – Use KeePassXC to store vault passwords
- ttf-hanazono (optional) – Install this font when using Japanese system language
Required by (1)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 18 Next › Last »
cirlo commented on 2021-05-20 11:37 (UTC) (edited on 2021-05-20 11:37 (UTC) by cirlo)
cirlo commented on 2021-05-19 16:17 (UTC)
@SailReal thank you very much! Both for the fast reply and the issue you opened upstream
SailReal commented on 2021-05-19 16:14 (UTC)
@cirlo no but I can reproduce it, just created this issue: https://github.com/cryptomator/cryptomator/issues/1658
cirlo commented on 2021-05-19 15:38 (UTC)
Does it ever happen to you that, after unlocking, mounting and using, you can't lock the drive back?
Even if i try to force the locking, it throws org.cryptomator.common.vaults.LockNotCompletedException
Kreba commented on 2021-05-03 15:52 (UTC) (edited on 2021-05-03 15:58 (UTC) by Kreba)
$ archlinux-java status
Available Java environments:
java-16-adoptopenjdk
java-8-openjdk (default)
$ sudo archlinux-java set java-16-openjdk
...
'/usr/lib/jvm/java-16-openjdk' is not a valid Java environment path
$ sudo archlinux-java set java-16-adoptopenjdk
$ archlinux-java status
Available Java environments:
java-16-adoptopenjdk (default)
java-8-openjdk
Thanks!
KoaTravis commented on 2021-05-03 12:13 (UTC) (edited on 2021-05-03 12:15 (UTC) by KoaTravis)
@Kreba Try to set the active java installation using the archlinux-java script. List the available java environments with:
archlinux-java status
And set it with:
archlinux-java set java-16-openjdk
Kreba commented on 2021-05-03 11:44 (UTC) (edited on 2021-05-03 11:47 (UTC) by Kreba)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project commons: Fatal error compiling: invalid flag: --release -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :commons
insalled: jdk-adoptopenjdk 16.0.1.u9-1 jdk8-openjdk 8.u292-1 jre8-openjdk 8.u292-1 jre8-openjdk-headless 8.u292-1
SailReal commented on 2021-05-03 07:54 (UTC)
@Achilleus which Java package did you installed? It looks like it is just a runtime and not the development kit with a compiler. Just to mention two random packages which should work: https://aur.archlinux.org/packages/jdk/, https://aur.archlinux.org/packages/jdk-adoptopenjdk/
Achilleus commented on 2021-05-03 07:46 (UTC)
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project commons: Compilation failure [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK? [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :commons
Dwa30v commented on 2021-05-03 07:23 (UTC)
@sToRmInG - Thanks!
Pinned Comments
ajgraves commented on 2021-05-02 20:49 (UTC)
Everyone, with great thanks to @SailReal, this package now builds Cryptomator from source. If you wish to continue using the binary AppImage build, you need only to install
cryptomator-bin
.We made this change to better align with the desires of the community (you've asked a few times to make this a "build from source" package) as well as better align to the package naming convention within the AUR.