marke
December 15, 2021, 1:15pm
1
Since some v1.8.0 users are getting trade errors when transacting with users on earlier versions, and the upgrade to v1.8.0 is mandatory, the Arch Linux AUR probably needs to be updated ASAP to avoid further trade problems escalating.
Relevant links:
https://aur.archlinux.org/packages/bisq/
opened 12:07PM - 04 Nov 21 UTC
closed 09:07AM - 19 Apr 23 UTC
### Description
Bisq does not build due to checksum mismatch in gradle witnes… s
#### Version
v1.7.5
### Steps to reproduce
Build from scratch
### Expected behaviour
Build successfull
### Actual behaviour
Stops on error:
Checksum failed for com.github.JesusMcCloud:jtorctl:389d61b1b5a85eb2f23c582c3913ede49f80c9f2b553e4762382c836270e57e5
#### Additional info
Change in gradle-witness.gradle from:
com.github.JesusMcCloud:jtorctl:389d61b1b5a85eb2f23c582c3913ede49f80c9f2b553e4762382c836270e57e5
to:
com.github.JesusMcCloud:jtorctl:6465e0b22b921344a065a6e82a5390ab2f9dac5ab293c38bd8a76baddead6492
I tried to do the same by modifying the PKGBUILD to specify pkgver=1.8.2,
Then all you have to do is update the sha256sums, but I’m not sure what the shasums should be. Any ideas?
It should work as long as we update the pkgver and shasums.
I just created this wiki article: Fix Arch release - Bisq Wiki
1 Like
Thank you!
Quick question, how did you get this shasum?
sha256sums=('d69bab29875eed312811cb34a84ac7920acac74f9a86eb637e56e92e5fcbcbbb'
quick reply, copypasted by a user who built this procedure… but it’s trivial to compute a sha256 of a file
Well yeah, but I’m not sure where you can find the sha256 on the bisq github to confirm it’s correct.
that would be the sha256sum of a file inside the release, so you download said release and check against the file that you are supposed to edit as per the wiki article