Arch Linux User Repository

@chovy you can always try adding it manually.

1. Download the key manually, for example

wget -O keyfile.asc https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xB493319106CC3D1F252E19CBF806F422E222AA02

1. Import the key: gpg --import keyfile.asc

@dmp1ce Hello, here is an updated PKGBUILD https://github.com/nikicat/bisq-pkgbuild/blob/master/PKGBUILD (pkgname should be changed though)

@Sir-Photch I don't know. I'll try to test it and figure out the problem. A patch is welcome. Also, another maintainer would be nice. I don't always get to the updates in a timely manner.

bisq-desktop doesn't work for me; Running /opt/bisq/bin/desktop directly works. Why is that?

/usr/bin
/usr/bin/bisq-desktop: line 13: ./gradlew: No such file or directory

The missing signature file for 1.9.15 is already present in the released GitHub package.

@kostrse I don't think this is a good idea for this package. We are building from source here, so we need to use the specific java version recommended by the developers of the app. In their build instructions on github, the devs specify: Bisq currently works with JDK 11 and JDK 15, and later they state: If you do not have JDK 11 installed, check out scripts in the scripts directory or download it manually from https://jdk.java.net/archive/. (Source: https://github.com/bisq-network/bisq/blob/master/docs/build.md). This makes you think that JDK 11 is the optimal version to build Bisq. I don't think we should losen the dependency here, since users may face several bugs (or the app may not compile at all) when using a version of java that isn't recommended by upstream. Then, these same users could come here to complain that this package is broken, buggy, etc. In short, this isn't a good idea.

@chovy this issue is not related to this package, but rather to an inability of gpg to retrieve the key from the key server. Maybe it can be fixed by running gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys B493319106CC3D1F252E19CBF806F422E222AA02 , and then try installing this package again. However, I recommend you check if your DNS config is working properly, and maybe change your DNS server also, then try again. I never had any issue using cloudflare's 1.1.1.1.

Would be great to not have a hard dependency on specific version of JDK. Could you losen the dependency?

:: (1/1) Parsing SRCINFO: bisq
gpg: error reading key: No public key

 :: PGP keys need importing:
 -> B493319106CC3D1F252E19CBF806F422E222AA02, required by: bisq
:: Import? [Y/n] 
:: Importing keys with gpg...
gpg: keyserver receive failed: Server indicated a failure
 -> problem importing keys

:: PGP keys need importing: -> B493319106CC3D1F252E19CBF806F422E222AA02, required by: bisq :: Import? [Y/n] :: Importing keys with gpg... gpg: keyserver receive failed: Server indicated a failure -> problem importing keys

@waasl , good to see your problem was solved. So in reality your problem was kinda the opposite of what I was thinking: this PKGBUILD makes sure to compile bisq with java-11-openjdk (good to know that, actually), so the issue was that your system was trying to run the app with a much older version of java (8). But I knew that setting the right archlinux-java environment would fix it in the end, one way or another.

But there is still the issue of needing to call directly /opt/bisq/bin/desktop to be able to run Bisq, which works, but isn't ideal. The maintainer should try to look at this issue and solve it. My humble guess is that the problem lies in the /opt/bisq/bisq-desktop file, where it tries to start Bisq with this command: ./gradlew :desktop:startBisqApp . However, I don't know what would be the best way to solve this.