@SailReal I get the following output:
$ java --version
openjdk 17.0.4.1 2022-08-12
OpenJDK Runtime Environment (build 17.0.4.1+1)
OpenJDK 64-Bit Server VM (build 17.0.4.1+1, mixed mode)
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) |
Last Packager: | SailReal |
Votes: | 79 |
Popularity: | 0.35 |
First Submitted: | 2016-04-03 17:36 (UTC) |
Last Updated: | 2024-02-27 15:44 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 17 Next › Last »
@SailReal I get the following output:
$ java --version
openjdk 17.0.4.1 2022-08-12
OpenJDK Runtime Environment (build 17.0.4.1+1)
OpenJDK 64-Bit Server VM (build 17.0.4.1+1, mixed mode)
@Munzu what is the output of java --version
?
I'm currently getting the following compile error:
[INFO] Compiling 300 source files to /home/tai/.cache/paru/clone/cryptomator/src/cryptomator-1.6.15/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.702 s
[INFO] Finished at: 2022-10-09T10:21:04+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project cryptomator: Fatal error compiling: error: release version 17 not supported -> [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: A failure occurred in build().
Aborting...
@purejava Thanks for the hint. Just applied your suggested changes :)
Java 18 is out. Building the package on a systen with Java 18 installed, it downloads the Java 17 makedependency, but the build nevertheless fails with:
==> Beginne prepare()...
You don't have a Java 17 JDK selected but the following installed on your system:
java-17-openjdk
Select a Java 17 JDK using "sudo archlinux-java set [name from the list above]"
If you switched to a JDK 17, please re-run the installation.
==> FEHLER: Ein Fehler geschah in prepare().
Breche ab...
This could be improved with makedepends=('java-environment>=17' 'maven')
and a modified error message. I changed the message for keepassxc-cryptomator
, maybe you want to take a look.
@SailReal ok i does it
@Fatum maybe it is a bug can you please create an issue containing all that information on https://github.com/cryptomator/cryptomator/issues/new?assignees=&labels=type%3Abug&template=bug.yml and containing all the information you found out during the tests. Thank you :)
Hello! I have manjaro KDE latest version. I updated cryptomator to version 1.6.9. Now when selecting the storage folder for 2 minutes the program and the system hangs.
12:23:20.703 [JavaFX Application Thread] INFO o.f.dbus.handlers.SignalHandler - Await signal org.kde.KWallet$walletAsyncOpened(/modules/kwalletd5) within 120 seconds.
12:25:20.706 [JavaFX Application Thread] WARN o.f.dbus.handlers.SignalHandler - java.util.concurrent.TimeoutException
This didn't happen on the previous version. Is there any way to fix it?
@SailReal Thank you - this one is working :-)
@agarbathi gpg --keyserver keys.gnupg.net --recv-keys 58117AFA1F85B3EEC154677D615D449FE6E6A235
should help if your default keyserver doesn't have the key included. Otherwise you can also retrieve it from our Cryptobot using curl -sSL https://github.com/cryptobot.gpg | gpg --import -
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.