Arch Linux User Repository

Your JDK 8 is set as default and therefore the error. For bisq-1.6.4 to be compiled you need to set your Java to another default as per https://wiki.archlinux.org/title/Java#Change_default_Java_environment. Try JDK 15.

I'm trying to upgrade Bisq from 1.6.2-1 to 1.6.4-1, but the build is failing. Here is what I believe to be the relevant logs:

> Task :assets:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':assets:compileJava'.
> Could not target platform: 'Java SE 10' using tool chain: 'JDK 8 (1.8)'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1s
17 actionable tasks: 2 executed, 15 up-to-date
==> ERROR: A failure occurred in build().
    Aborting...

I don't have gradle installed, is that a requirement? Or maybe I have a versioning problem with java or jdk. Here is what I have installed:

$ pacman -Q | grep -E 'java|jdk|gradle'
java-environment-common 3-3
java-runtime-common 3-3
java11-openjfx 11.0.10.u1-1
jdk-openjdk 15.0.2.u7-1
jdk10-openjdk 10.0.2.u13-2
jdk11-openjdk 11.0.11.u9-1
jdk8-openjdk 8.u292-1
jre-openjdk 15.0.2.u7-1
jre-openjdk-headless 15.0.2.u7-1
jre10-openjdk 10.0.2.u13-2
jre10-openjdk-headless 10.0.2.u13-2
jre11-openjdk 11.0.11.u9-1
jre11-openjdk-headless 11.0.11.u9-1
jre8-openjdk 8.u292-1
jre8-openjdk-headless 8.u292-1

I poked around at help.gradle.org, but really have no idea what I'm reading. Any help is appreciated.

That's right. Go to the releases page and you will see the same hash for the GPG key. 29CDFD3B which belongs to Christoph Atteneder.

https://github.com/bisq-network/bisq/releases

If you use 29CDFD3B, as suggested on Github and here, then you know you are installing the binary created from the original creator.

Question is, is this person trusted?

Well that is on you to decide. :) the prettygoodprivacy (PGP) system is designed to build trust networks and give you guidance on whether to trust the key of someone or not. It is a tool that attempts to help to come over a pretty much unsolvable problem.

In this case, https://github.com/bisq-network/bisq/releases, which is the place where Bisq is built, gives you a whole lot of information on how it is built, how it is installed and how you can verify that you got the correct software package. There you can also find the key files of the guy who packaged and released bisq (and he did so for years now).

Does this fix defeat the purpose of having keys in the first place?

Well, you do no longer need to trust me, the packager, to supply the correct checksums. And you can be rather certain that it still is the same guy that releases bisq, until key stuff starts acting up again. So at least you can be certain that nobody suddenly hijacked the AUR and feeds you malicious software.

:)

just spent an hour banging my head off my monitor trying to get this installed. Haven't used linux in years and from what I remember, with arch, nothing ever just works. Forgot that till now. Installed manjaro and after it's first update it breaks and terminal wont run. Of course. Fixed it. Anyway. I digress.

Key problem. Spent an hour figuring out how to manually do keys and shit only to see here that the uploader/packager posted a fix. Pasted in what he posted and it finally installed.

Question is, is this person trusted? Does this fix defeat the purpose of having keys in the first place? Seems pretty stupid.

I should have gone with a debian based distro. I'm going to bed.

I updated yesterday with the manjaro gui package manager. I am unable to find Bisq listed in my applications now and the GNOME activities search does not bring it up in a search.

I am hesitant to reinstall the package because I have some bitcoins in the current bisq installation. Any ideas on next steps here? I attempted to open Bisq in the command line under /opt/bisq/bisq-desktop but it was an invalid command. I did confirm in pacman that the bisq package is still installed. Any further guidance would be appreciated. Thanks.

I just updated the build to fetch the newly available signed source tarball off github. finally.

If you stumble over the message that a key is not trusted just do a gpg --recv-keys 29CDFD3B and you should be good

For Arch users with GNOME (hence Wayland):

To me Bisq didn't want to know to start, so I tried to install all the versions of Java that I found (apart from the older ones) and set the default OpenJDK11, and now everything works. Here are the commands I gave, but I don't know exactly which of the things I installed is the one that made Bisq work (I'm newbie):
sudo pacman -Syuv java-environment-common jdk-openjdk openjdk-doc openjdk-src jre11-openjdk jdk11-openjdk openjdk11-doc openjdk11-src java-openjfx java-openjfx-doc java-openjfx-src java11-openjfx java11-openjfx-doc java11-openjfx-src --noconfirm &&
sudo archlinux-java set java-11-openjdk
I hope it can be of help to someone. You probably just need to install OpenJDK11 only and then set it to default for Bisq to work, but I haven't tried.