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: 65
Popularity: 1.41
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 8 .. 13 Next › Last »

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?

dmp1ce commented on 2023-01-09 17:00 (UTC)

@dmrobotix, see https://bbs.archlinux.org/viewtopic.php?id=280386

I'm not sure if this is something I can fix in the PKGBUILD.

dmrobotix commented on 2023-01-09 16:31 (UTC) (edited on 2023-01-09 16:32 (UTC) by dmrobotix)

I'm getting the following error with bsdtar and yay is unable to finish building and installing the latest version as a result.

bsdtar: Option --no-read-sparse is not supported Usage: List: bsdtar -tf <archive-filename> Extract: bsdtar -xf <archive-filename> Create: bsdtar -cf <archive-filename> [filenames...] Help: bsdtar --help ==> ERROR: Failed to create package file. -> error making: bisq

dmp1ce commented on 2022-12-28 21:28 (UTC) (edited on 2022-12-28 21:33 (UTC) by dmp1ce)

@janders, what you did is exactly right for updating and should be safe to install. I figured out why my build wasn't working and I should have 1.9.8 pushed shortly.

There is also the bisq-bin package if this one doesn't work for some reason.

janders commented on 2022-12-28 19:26 (UTC) (edited on 2022-12-28 19:29 (UTC) by janders)

The latest update (1.9.8) is required, no trades are allowed with older versions. Since the AUR doesn't have the 1.9.8 yet, this is what I did to the PKGBLD file:

Edit the pkgver line to be:

pkgver=1.9.8

I downloaded the source code from GitHub, calculated the SHA256 checksum, and edited the sha256sums line with it:

sha256sums=('fcec6a070f69be68b53328fe0bdd9948dd49aa557fd4c24bb6ec4f68eff1d23e'
            'SKIP'
            '687d643fbe84660c3ebfe6270de98214f2e3ea791cb1d07d96d7ed889d61d406')

I was then able to build and install the package. But I'm not exactly sure if this is safe to run. Is what I've done sane? What drawbacks, risks, or implications are there to doing this?

dmp1ce commented on 2022-12-24 10:57 (UTC)

I'm having trouble with the build. Does anyone have a suggestion?

Starting a Gradle Daemon (subsequent builds will be faster)

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

FAILURE: Build failed with an exception.

* Where:
Build file '/build/bisq/src/bisq-1.9.8/build.gradle' line: 200

* What went wrong:
A problem occurred evaluating root project 'bisq'.
> Cannot run program "git": error=2, No such file or directory

* 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 18s

pinball_wizard commented on 2022-03-03 18:33 (UTC)

@dmp1ce

Great! Fixed it!

dmp1ce commented on 2022-03-03 11:55 (UTC)

@jvybihal I had trouble getting bisq to build without the wrapper. I am getting the following errors:

Welcome to Gradle 7.4!

Here are the highlights of this release:
 - Aggregated test and JaCoCo reports
 - Marking additional test source directories as tests in IntelliJ
 - Support for Adoptium JDKs in Java toolchains

For more details see https://docs.gradle.org/7.4/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'bisq'.
> Dependency verification failed for configuration ':classpath'
  5 artifacts failed verification:
    - log4j-2.17.1.pom (org.apache.logging.log4j:log4j:2.17.1) from repository MavenRepo
    - log4j-api-2.17.1.jar (org.apache.logging.log4j:log4j-api:2.17.1) from repository MavenRepo
    - log4j-api-2.17.1.pom (org.apache.logging.log4j:log4j-api:2.17.1) from repository MavenRepo
    - log4j-core-2.17.1.jar (org.apache.logging.log4j:log4j-core:2.17.1) from repository MavenRepo
    - log4j-core-2.17.1.pom (org.apache.logging.log4j:log4j-core:2.17.1) from repository MavenRepo
  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.4/userguide/dependency_verification.html#sec:troubleshooting-verification

  Open this report for more details: file:///build/bisq/src/bisq-1.8.2/build/reports/dependency-verification/at-1646308114172/dependency-verification-report.html

* 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 2m 11s

Do you have any suggestions? Maybe the wrapper is setting the "classpath"?