# Mandatory upgrade to v1.8.0 unavailable in Arch Linux AUR

**URL:** <https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280>\
**Category:** Support\
**Created:** [December 15, 2021, 1:15pm UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280 "2021-12-15T13:15:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![marke](https://bisq.community/letter_avatar/marke/32/5_5575768a8748004e209b776fc1b2916d.png) [@marke](https://bisq.community/u/marke)\
**Post date:** [December 15, 2021, 1:15pm UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/1 "2021-12-15T13:15:32Z")

</div>

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/](https://aur.archlinux.org/packages/bisq/)

> <https://github.com/bisq-network/bisq/issues/5807#issuecomment-963641322>
>
> \### 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

---

<div class="post-metadata">

**Author:** ![bisquicked](https://bisq.community/letter_avatar/bisquicked/32/5_5575768a8748004e209b776fc1b2916d.png) [@bisquicked](https://bisq.community/u/bisquicked)\
**Post date:** [February 9, 2022, 8:26am UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/2 "2022-02-09T08:26:36Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\
**Post date:** [February 11, 2022, 9:18am UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/3 "2022-02-11T09:18:37Z")

</div>

I just created this wiki article: [Fix Arch release - Bisq Wiki](https://bisq.wiki/Fix_Arch_release)

---

<div class="post-metadata">

**Author:** ![bisquicked](https://bisq.community/letter_avatar/bisquicked/32/5_5575768a8748004e209b776fc1b2916d.png) [@bisquicked](https://bisq.community/u/bisquicked)\
**Post date:** [February 12, 2022, 9:52pm UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/4 "2022-02-12T21:52:44Z")

</div>

Thank you!

Quick question, how did you get this shasum?

> `sha256sums=('d69bab29875eed312811cb34a84ac7920acac74f9a86eb637e56e92e5fcbcbbb'`

---

<div class="post-metadata">

**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\
**Post date:** [February 12, 2022, 11:21pm UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/5 "2022-02-12T23:21:04Z")

</div>

quick reply, copypasted by a user who built this procedure… but it’s trivial to compute a sha256 of a file 🙂

---

<div class="post-metadata">

**Author:** ![bisquicked](https://bisq.community/letter_avatar/bisquicked/32/5_5575768a8748004e209b776fc1b2916d.png) [@bisquicked](https://bisq.community/u/bisquicked)\
**Post date:** [February 13, 2022, 1:40pm UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/6 "2022-02-13T13:40:52Z")

</div>

Well yeah, but I’m not sure where you can find the sha256 on the bisq github to confirm it’s correct.

---

<div class="post-metadata">

**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\
**Post date:** [February 14, 2022, 11:51am UTC](https://bisq.community/t/mandatory-upgrade-to-v1-8-0-unavailable-in-arch-linux-aur/11280/7 "2022-02-14T11:51:03Z")

</div>

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