Arch Linux User Repository

!!! Please do NOT flag the package out of date just because a new version has been release. !!!

Parsec self-updates and as long as the package still installs (no sha256 mismatch), there is no reason to update it in the AUR as the .deb actually is an older version.

For those having the sha256sum issue, try to find the "parsec-linux.deb" file on your system and remove it from the caches.

For me, pamac was caching the deb file, because pacman -Sc did not help. I used the tool fd to find it.

>>> fd parsec-linux.deb /
/var/tmp/pamac-build-yulian/parsec-bin/parsec-linux.deb

After I removed the parsec-linux.deb file from that tmp folder for pamac, it all worked swimmingly. It might be in a different place for your preferred package tool, or distro.

@usernamerequired If you are using yay (or an other AUR helper) it might be possible that it doesn't download the new parsec-linux.deb file.

If you git clone it in a totaly new folder/thing it works fine, because parsec-linux.deb doesn't already exist so it downloads the newer version.

This is only my assumption, but for the moment, I upgrade parsec-bin manually.

-> Found parsec-linux.deb ==> Validating source_x86_64 files with sha256sums... parsec-linux.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build parsec-bin

i checked the sha256 and the seem to be correct, dont know whats the hiccup here.

The sha256 sum doesn't match anymore, pacaur refuses to install it as is.

Edit: Nevermind! Thanks :)

@erkexzcx Forgot to reply yesterday, sorry.
The .deb package can't have changed as otherwise the sha256 sum wouldn't match anymore.
I agree that parsecgaming could do a better job with providing versioned .deb packages but as they don't we have to work with what we've got.

In regards to automatically updating the PKGBUILD, I think that's a bad idea. I'd rather have a final look at what changed rather then automatic the process.
Whenever there's a new version and I miss to update, just flag the package out-of-date and I usually get to it within 1-2 hours (unless I'm in bed)

Not sure what changed (seems it's upstream change), but /usr/share/applications/parsec.desktop got changed from Terminal=true to Terminal=false which is great since we have native desktop app (no longer need to use browser).

But wondering why I had to perform trizen -S parsec-bin manually to update this package and there is no update for such little change in https://parsecgaming.com/changelog/ ? Also parsec versioning control is such a mess....

So, @tadly - if you could make me a maintainer, I could set up script to auto update this PKGBUILD according to provided content-length attribute from the server:

curl -sI https://builds.parsecgaming.com/package/parsec-linux.deb | grep -i Content-Length | awk '{print $2}'

@Thulinma I remember this being an issue with another package I maintain.
Thanks for the heads-up, should be fixed now :)

Hey there! Thanks for keeping this package up to date. Unfortunately the software does hash checks on some of its files, meaning Arch's stripping of binaries changes the hash and can very easily result in a corrupt install. To prevent issues, please add:

options=('!strip')

To the PKGBUILD and it should no longer happen. :-)

@erkexzcx thanks. This would have been a big issue actually. Hope this iteration fixes it (Don't have a arm device available to test)

Not a big issue, but sources on AUR website for arm architectures looks slightly misleading... :D

https://builds.parsecgaming.com/package/parsec-linux.deb (x86_64)
https://builds.parsecgaming.com/package/parsec-rpi.deb (arm)
https://builds.parsecgaming.com/package/parsec-rpi.deb[@] (armv6h)
https://builds.parsecgaming.com/package/parsec-rpi.deb[@] (armv7h)
https://builds.parsecgaming.com/package/parsec-rpi.deb[@] (aarch64)