Missing libasound2t64 when intalling Bisq 1.10.0 on Debian 12 Bookworm [workaround]

Hi,

I had an issue installing the Bisq 1.10.0 .deb package on Debian 12 Bookworm because it depends on:

libasound2t64

Debian 12 still provides:

libasound2

Since libasound2t64 belongs to newer Debian releases, I didn’t want to pull it from Trixie/Sid and risk breaking my Bookworm system.

Here is the workaround I used:

mkdir -p ~/deb-fix
cd ~/deb-fix

dpkg-deb -R ~/Bisq-64bit-1.10.0.deb pkg
nano pkg/DEBIAN/control

In the Depends: line, replace:

libasound2t64

with:

libasound2t64 | libasound2

Then rebuild and install:

dpkg-deb -b pkg bisq-bookworm-fixed.deb
sudo apt install ./bisq-bookworm-fixed.deb

Of course, this is just an unofficial workaround. Ideally, the .deb dependency could be changed upstream to support both Debian 12 and newer Debian-based systems.

Yes, this solution implies editing the libasound package itself to also take up the name of the package bisq looks for.
Depending on the kind of solution you want to adopt, you can also leave the package untouched and create a clone with a different name:

Bisq 1.10.0 on Ubuntu 22.04 – Dependency Fix
Problem:
Bisq 1.10.0 requires libasound2t64, which only exists on Ubuntu 24.04+. On Ubuntu 22.04 you get this error:
bisq depends on libasound2t64; but it is not installed
Solution – create a dummy package:

Bash

sudo apt install equivs
cd /tmp
equivs-control libasound2t64
nano libasound2t64

Delete everything in the file and paste this:

Section: misc Priority: optional Standards-Version: 3.9.2 Package: libasound2t64 Version: 1.0 Maintainer: dummy Description: Dummy package for libasound2t64

Save with Ctrl+O → Enter → Ctrl+X, then:

Bash

equivs-build libasound2t64
sudo dpkg -i libasound2t64_1.0_all.deb
sudo dpkg -i ~/Downloads/Bisq-64bit-1.10.0.deb
sudo apt --fix-broken install

Actually, libasound2 and libasound2t64 provides the same alsa library libasound.so.2 (just different version), so there’s no need to edit the libasound2 package.

The package renaming is part of the ABI transition to 64bit time_t, so I don’t think it will cause any trouble (until 2038 at least)

But it still a “dirty workaround”, just to be able to trade waiting for a proper fix…

version 1.10.1 has been released ?

Bisq version 1.10.1 has been released ?