Arch Linux User Repository

@dmp1ce and @waasl , Ok so I just found out the file /opt/bisq/bisq-desktop (actually a bash script, I haven't noticed before, thought it was a binary) of the current build (1.9.14-1) tries to start bisq with this command:

./gradlew :desktop:startBisqApp

So of course it won't work. I have no idea what this ./gradlew file or directory is doing there. I tried replacing

./gradlew :desktop

with

/opt/bisq/bin/desktop 

(there should be a blank space at the end, after "desktop"), so I replaced that on the /opt/bisq/bisq-desktop file, and now running bisq-desktop or /usr/bin/bisq-desktop now works and bisq starts. Of course, clicking on the icon also started working again. But as I said before, I'm just a simple user messing around with this stuff, I have no idea if "my fix" is ideal or not. Waiting for the maintainer to have a look at this.

@dmp1ce I have the same issue that @waasl pointed out on the second part of his comment - The build is successful, however running bisq-desktop or /usr/bin/bisq-desktop or /opt/bisq/bisq-desktop (or even clicking the bisq icon) doesn't work, and the error is the same as his: line 13: ./gradlew: No such file or directory. I'd like to emphasize this isn't an issue only with yay, because it also happens with paru and also when installing it manually with git and makepkg. I was able to reproduce the issue on 2 different computers, it happened regardless if I was updating this bisq package, or if I was installing it for the first time. However, running /opt/bisq/bin/desktop does work and does start bisq, so please try to look at what is happening here, I'm just a user and I don't know what's going on here.

@waasl I'm not sure. I'm familiar with pamac. Maybe just use yay for now? I build and test with clean-chroot-manager which builds from a very clean environment.

Can't install with pamac:

==> Starting build()...
  -> Building bisq...
/var/tmp/pamac-build-otto/bisq/PKGBUILD: line 30: ./gradlew: Permission denied
==> ERROR: A failure occurred in build().
    Aborting...

Instead installed with:

yay -S bisq

On run in terminal:

$ env JAVA_HOME=/usr/lib/jvm/java-11-openjdk /usr/bin/bisq-desktop

output:

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

please help

@FreddieChopin, Thanks! I applied the changes and the build worked fine.

I asked about this issue on Bisq chat and I'm copying the reply I got from one of Bisq developers:

--

Hi freddie_chopin, sorry for breaking the Arch Linux build. I fixed it here: https://github.com/alvasw/bisq-aur-package You can clone the repository and run makepkg to build a package for pacman. The maintainers fo the AUR package need to update the PKGBUILD file.

--

Hope that helps!

I get an error when building the latest version. The tests fail:

> Task :build-logic:gradle-tasks:jar
:gradle-tasks:jar: No valid plugin descriptors were found in META-INF/gradle-plugins

> Task :build-logic:packaging:compileKotlin
> Task :build-logic:packaging:compileJava NO-SOURCE
> Task :build-logic:packaging:classes
> Task :build-logic:packaging:inspectClassesForKotlinIC
> Task :build-logic:packaging:jar

> Configure project :desktop
Project :desktop => no module-info.java found

> Configure project :p2p
Project :p2p => no module-info.java found

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':desktop:distTar'.
> Could not resolve all dependencies for configuration ':desktop:runtimeClasspath'.
   > Failed to calculate the value of task ':assets:compileJava' property 'javaCompiler'.
      > Unable to download toolchain matching the requirements ({languageVersion=11, vendor=AZUL, implementation=vendor-specific}) from 'https://cdn.azul.com/zulu/bin/zulu11.66.15-ca-jdk11.0.20-linux_x64.zip'.
         > Could not copy file '/build/.gradle/jdks/zulu11/zulu11.66.15-ca-jdk11.0.20-linux_x64/legal/jdk.scripting.nashorn/joni.md' to '/build/.gradle/jdks/azul_systems__inc_-11-amd64-linux/zulu11.66.15-ca-jdk11.0.20-linux_x64/legal/jdk.scripting.nashorn/joni.md'.
            > /build/.gradle/jdks/azul_systems__inc_-11-amd64-linux/zulu11.66.15-ca-jdk11.0.20-linux_x64/legal/jdk.scripting.nashorn/joni.md (Permission denied)

* 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

BUILD FAILED in 1m 44s
31 actionable tasks: 31 executed

@nbryskin I'm not sure. I have never tried to build on aarch64. If someone wants to take a look at building on aarch64 and provide a patch that would be fine.

I'm getting this error when building on aarch64:

> Task :proto:generateProto FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':proto:generateProto'.
> Dependency verification failed for configuration ':proto:protobufToolsLocator_protoc':
    - On artifact protoc-3.19.1-linux-aarch_64.exe (com.google.protobuf:protoc:3.19.1) in repository 'MavenRepo2': checksum is missing from verification metadata.

  If the artifacts are trustworthy, you will need to update the gradle/verification-metadata.xml file by following the instructions at https://docs.gradle.org/7.6/userguide/dependency_verification.html#sec:troubleshooting-verification

  These files failed verification:
    - GRADLE_USER_HOME/caches/modules-2/files-2.1/com.google.protobuf/protoc/3.19.1/756fa5e2ea67d2153e0f2316eb2e97a90082f44d/protoc-3.19.1-linux-aarch_64.exe

@dipunm, I don't know but you might need to set your java version. See: https://wiki.archlinux.org/title/Java

Maybe run the archlinux-java command.