Search Criteria
Package Details: bisq-desktop 1.10.7-1
Package Actions
| 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, bisq-bin, bisq-git |
| Provides: | bisq |
| Replaces: | bisq |
| Submitter: | dmp1ce |
| Maintainer: | dmp1ce (nojo) |
| Last Packager: | nojo |
| Votes: | 69 |
| Popularity: | 0.048375 |
| First Submitted: | 2017-07-05 14:43 (UTC) |
| Last Updated: | 2026-08-26 06:11 (UTC) |
Dependencies (3)
- jdk21-openjdk (openjdk-zulu21-ca-fx-binAUR, openjdk-liberica21-full-binAUR, zing-21-binAUR, jdk21-temurinAUR)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- jdk21-openjdk (openjdk-zulu21-ca-fx-binAUR, openjdk-liberica21-full-binAUR, zing-21-binAUR, jdk21-temurinAUR) (make)
Latest Comments
1 2 3 4 5 6 .. 14 Next › Last »
nojo commented on 2026-08-24 09:40 (UTC)
@catzer @corv1d Thanks for the pings and the work — but the package deliberately isn't updating, and switching to a tarball + sha256-only PKGBUILD is the wrong fix. A checksum of a GitHub autogenerated tarball only pins "whatever GitHub served the day it was computed"; it says nothing about who made the release. The current PKGBUILD builds from the git tag with ?signed + validpgpkeys, so makepkg verifies the release is signed by the pinned Bisq release key (E222AA02) before anything is built.
The updates are stuck because upstream published v1.10.5 and v1.10.6 with unsigned (lightweight) tags. The automated updater (https://github.com/nikicat/aur-bisq-updater) test-builds every release and refuses to push when tag verification fails — for an app that holds your bitcoin, shipping faster by silently dropping provenance is the wrong trade.
Tracked upstream: https://github.com/bisq-network/bisq/issues/8032 — same problem as v1.10.4 (#7967), which upstream fixed by retro-signing the tag; the installer .asc files are already signed by the right key, so this is a release-process slip, not anything suspicious. The moment the tag is signed, the daily job pushes the update automatically. If it drags on, please add your voice on that issue.
catzer commented on 2026-08-23 05:44 (UTC) (edited on 2026-08-23 19:33 (UTC) by catzer)
Thanks, I Updated it for v1.10.6
corv1d commented on 2026-08-22 06:00 (UTC) (edited on 2026-08-22 06:13 (UTC) by corv1d)
catzer commented on 2026-08-21 10:35 (UTC)
can you update to 1.10.5 please?
corv1d commented on 2026-05-31 12:00 (UTC)
new pkgbuild for 1.10.1, also it would fail build on arch due to latest jdk being v26, edited pkgbuild to specifically use the version it's built and tested with (could have changed gradle version instead ig but i think this makes sense.) also i'm using the .desktop from >transgressoft so thanks. new PKGBUILD:
transgressoft commented on 2026-05-21 18:49 (UTC)
This is the updated PKGBUILD for the latest, 1.10.0 version:
and this the updated bisq.desktop file pointing to jdk21-openjdk:
<deleted-account> commented on 2026-05-16 00:14 (UTC)
Please remove the --scan argument from gradle. It is unnecessary, and it uploads data about the build to a Gradle cloud service, which is not ideal for privacy.
inThe-FLesh commented on 2026-01-05 03:07 (UTC)
@ldahleen54 @catzer Thanks!
catzer commented on 2026-01-04 16:11 (UTC) (edited on 2026-01-04 16:12 (UTC) by catzer)
@ldahleen54 leading zero missing so sha256 checksum is 0a7dbf8e01f7ce293a6b9d580f507c03b093bf7c062e8bd3a1b93334bf76b002
ldahleen54 commented on 2026-01-03 18:06 (UTC) (edited on 2026-01-03 18:08 (UTC) by ldahleen54)
version 1.9.21 is very broken. Until the AUR is updated, its best to edit the PKGBUILD file to use 1.9.22 and update the sha256 checksum to a7dbf8e01f7ce293a6b9d580f507c03b093bf7c062e8bd3a1b93334bf76b002
1 2 3 4 5 6 .. 14 Next › Last »