Package Details: bisq 1.9.14-1

Git Clone URL: https://aur.archlinux.org/bisq.git (read-only, click to copy)
Package Base: bisq
Description: Cross-platform desktop application that allows users to trade national currency (dollars, euros, etc) for bitcoin without relying on centralized exchanges
Upstream URL: https://bisq.network
Licenses: AGPL3
Conflicts: bisq-bin, bisq-git
Provides: bisq
Submitter: dmp1ce
Maintainer: dmp1ce
Last Packager: dmp1ce
Votes: 63
Popularity: 0.45
First Submitted: 2017-07-05 14:43 (UTC)
Last Updated: 2023-10-18 00:14 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 12 Next › Last »

wag commented on 2023-10-21 17:55 (UTC) (edited on 2023-10-21 18:11 (UTC) by wag)

@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.

dmp1ce commented on 2023-10-21 11:06 (UTC)

@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.

waasl commented on 2023-10-21 06:54 (UTC) (edited on 2023-10-21 07:08 (UTC) by waasl)

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

dmp1ce commented on 2023-10-18 00:18 (UTC)

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

FreddieChopin commented on 2023-10-17 11:24 (UTC)

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!

dmp1ce commented on 2023-10-14 18:20 (UTC)

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

dmp1ce commented on 2023-08-21 22:40 (UTC)

@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.

nbryskin commented on 2023-08-21 10:05 (UTC)

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

dmp1ce commented on 2023-02-12 02:01 (UTC)

@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.

dipunm commented on 2023-02-10 22:15 (UTC) (edited on 2023-02-10 22:19 (UTC) by dipunm)

I'm getting the error:

ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

Upgrading from 1.9.6-1 to 1.9.9-1.

I have jdk11-openjdk installed, and I have never had to add anything to my bash profile before.

I also verified, java is in my PATH variable.

I was able to address this by running: JAVA_HOME=/usr/lib/jvm/java-11-openjdk/ yay -Sy bisq but I'm wondering what has changed?