Note: There's a bug in my Bisq 2 Nix package.
The symptom is an immediate failure to connect to the Tor network, and it can happen after updating Nixpkgs.
The cause is that once Bisq 2 extracts the Tor binary (BASH script) from it's JAR archive, it doesn't extract it again; At least for the same version of Bisq 2. This can lead to the extracted scripting pointing to a Tor binary that's no longer in the Nix store.
I fixed it by deleting the directory where Tor is extracted, so that Bisq 2 has to extract upon every start up.
#nix #bisq
emmanuelrosa / Emmanuel
npub18e…ucvu7
2024-04-05 23:09:49
Author Public Key
npub18eynzyyrx0v46qjnvtj6mvekpxlfnkq06e3zfd6q9487vty0lfaszucvu7Published at
2024-04-05 23:09:49Event JSON
{
"id": "c0ea1cf52e5ecd3a97999120487b442a5dd80060388a6363e1995547871e6f4b",
"pubkey": "3e4931108333d95d025362e5adb33609be99d80fd66224b7402d4fe62c8ffa7b",
"created_at": 1712351389,
"kind": 1,
"tags": [
[
"t",
"nix"
]
],
"content": "Note: There's a bug in my Bisq 2 Nix package.\n\nThe symptom is an immediate failure to connect to the Tor network, and it can happen after updating Nixpkgs.\n\nThe cause is that once Bisq 2 extracts the Tor binary (BASH script) from it's JAR archive, it doesn't extract it again; At least for the same version of Bisq 2. This can lead to the extracted scripting pointing to a Tor binary that's no longer in the Nix store.\n\nI fixed it by deleting the directory where Tor is extracted, so that Bisq 2 has to extract upon every start up.\n\n#nix #bisq",
"sig": "002fc85c4ac19d0d37393e3cd43eaa48804c7384f59ba4e534f16b84d7e784e6f69f9418ddc6dca5722b8d3f01c1dc3fd6aae05bb6e81f869da9155d80c9d260"
}