@garlicbreadwolfs thanks for your feedback. I was aware that the solution is not perfect with both points you raised, how would you solve it? You are very welcome to describe it also in the upstream issue https://github.com/cryptomator/cryptomator/issues/1985
Search Criteria
Package Details: cryptomator 1.12.3-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) |
Last Packager: | SailReal |
Votes: | 79 |
Popularity: | 0.32 |
First Submitted: | 2016-04-03 17:36 (UTC) |
Last Updated: | 2024-02-27 15:44 (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 2 3 4 5 6 7 8 9 .. 17 Next › Last »
SailReal commented on 2022-10-10 11:42 (UTC)
purejava commented on 2022-10-10 11:21 (UTC)
@SailReal I am not sure, if the last change is needed. java-environment
is only provided by jdks, not jres and therefore should be fine. :)
<deleted-account> commented on 2022-10-10 11:20 (UTC)
To begin with, this problem occurs not only in Japanese but also in Chinese. And this is an upstream bug. You should participate in the upstream discussion and not show your lack of understanding of the CJK languages.
<deleted-account> commented on 2022-10-10 11:15 (UTC)
ttf-hanazono is not the only Japanese font. There are many other Japanese fonts available. Please understand the situation in which Japanese is placed.
<deleted-account> commented on 2022-10-10 11:13 (UTC)
Please remove ttf-hanazono from optdepends. You need some kind of ttf that supports Japanese, but it does not have to be hanazono.
ttf-hanazono is not the only Japanese font. There are many other Japanese fonts available. Please understand the situation in which Japanese is placed.
To begin with, this problem occurs not only in Japanese but also in Chinese. And this is an upstream bug. You should participate in the upstream discussion and not show your lack of understanding of the CJK languages.
Munzu commented on 2022-10-09 22:37 (UTC)
@SailReal Thanks for the quick patch!
SailReal commented on 2022-10-09 21:35 (UTC)
@Munzu makedepends
contains now directly jdk17-openjdk
which should fix this problem for other users in the future...thanks again for your feedback :)
SailReal commented on 2022-10-09 21:13 (UTC)
@Munzu ahhhh, well, I see, you did install a Java runtime environment (jre) and not a Java development kit (jdk), how would you know^^, but for compiling software, we need the jdk. Will change the pre check to verify that a jdk is installed (using javac -version
instead of java -version
) and check if we can better specify the Java dependency in general because months ago, Arch didn't have an Java version 17 in the official repositories but now it is https://archlinux.org/packages/extra/x86_64/jdk17-openjdk/ ... this will make it even more clear what to install.
Thanks for your feedback and will enhance it soon.
Munzu commented on 2022-10-09 20:13 (UTC) (edited on 2022-10-09 20:26 (UTC) by Munzu)
@SailReal Yeah it's weird. I've tried restarting and clearing the paru cache in ~/.cache/paru/clone/cryptomator
but no difference.
Actually, maybe I should have mentioned this, the same system upgrade I was running (that also resulted in the compilation error) installed jre-openjdk-headless (17.0.4.1.u1-2)
and jre-openjdk (17.0.4.1.u1-2)
according to the pacman log. It asked me something like whether I want to replace some Java thing with the other. If I remember correctly, the two options were the same name except one didn't have the 17
(?) in the name so I just picked the default option which had the more general name. Unfortunately, I don't remember the exact name.
Here's what I think are the relevant lines in my /var/log/pagman.log
:
[2022-10-09T10:03:14+0200] [ALPM] installed jre-openjdk-headless (18.0.2.1.u0-1)
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] Default Java environment is already set to 'java-17-openjdk'
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] See 'archlinux-java help' to change it
[2022-10-09T10:03:14+0200] [ALPM] installed jre-openjdk (18.0.2.1.u0-1)
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] Default Java environment is already set to 'java-17-openjdk'
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] See 'archlinux-java help' to change it
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] when you use a non-reparenting window manager,
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] set _JAVA_AWT_WM_NONREPARENTING=1 in /etc/profile.d/jre.sh
[2022-10-09T10:03:14+0200] [ALPM] installed jdk-openjdk (18.0.2.1.u0-1)
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] Default Java environment is already set to 'java-17-openjdk'
[2022-10-09T10:03:14+0200] [ALPM-SCRIPTLET] See 'archlinux-java help' to change it
When I do $ archlinux-java status
, I get the following output:
Available Java environments:
java-11-openjdk
java-17-openjdk (default)
java-18-openjdk
EDIT:
I had to do $ sudo archlinux-java set java-18-openjdk
, now the installation worked. Sorry about the bloated comment.
SailReal commented on 2022-10-09 19:49 (UTC)
@Munzu this is weird because 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
indicates that you are trying to compile it with Java version pre 17, but during compilation in a pre-check the build script checks the Java version too and would fail if it is not 17 or 18 with another message...what I don`t understand is why the Java binary thinks it is version 17 but fails during compilation because it is not 17?^^ ... does a restart make a difference?
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.