@sauyon Fair point. Something I could have thought of myself. Updated and pushed
Search Criteria
Package Details: parsec-bin 150_95-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/parsec-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | parsec-bin |
| Description: | Remotely connect to a gaming pc for a low latency remote computing experience |
| Upstream URL: | http://parsec.app |
| Keywords: | parsec remote streaming |
| Licenses: | custom |
| Provides: | parsec |
| Submitter: | sdellysse |
| Maintainer: | tadly |
| Last Packager: | tadly |
| Votes: | 54 |
| Popularity: | 0.31 |
| First Submitted: | 2017-08-10 02:44 (UTC) |
| Last Updated: | 2024-07-28 06:54 (UTC) |
Dependencies (8)
- ffmpeg4.4
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- libglvnd (libglvnd-gitAUR)
- libxcb (libxcb-gitAUR)
- libxext (libxext-gitAUR)
- libxi (libxi-gitAUR)
- openssl-1.1
- libva (libva-gitAUR, intel-media-stack-binAUR, libva-headlessAUR) (optional) – For hardware accelerated decoding
Required by (0)
Sources (1)
tadly commented on 2020-07-10 08:50 (UTC)
sauyon commented on 2020-07-10 08:43 (UTC)
For those having the sha256sum issue, try to find the "parsec-linux.deb" file on your system and remove it from the caches.
FWIW I like adding the version number to the name of the downloaded file, since it gets around this issue and it makes it a bit easier to tell when building manually too.
kajmaj87 commented on 2020-06-25 16:40 (UTC) (edited on 2020-06-25 16:40 (UTC) by kajmaj87)
Is the downgrading to mesa<=18.0.4 still the only solution to avoid the libsndio.so.6.1: cannot open shared object file: No such file or directory error?
tadly commented on 2020-06-10 06:09 (UTC) (edited on 2020-06-10 06:10 (UTC) by tadly)
!!! 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.
kerenua commented on 2020-03-07 00:56 (UTC)
what worked for me in locating the file was find . -name "parsec*"
the fd command gave me no output for some reason.
Daegalus commented on 2020-02-25 19:11 (UTC)
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.
entrix commented on 2020-02-23 11:20 (UTC) (edited on 2020-02-23 11:20 (UTC) by entrix)
@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.
<deleted-account> commented on 2020-02-23 09:03 (UTC)
-> 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.
Saff commented on 2020-02-02 14:22 (UTC) (edited on 2020-02-02 21:52 (UTC) by Saff)
The sha256 sum doesn't match anymore, pacaur refuses to install it as is.
Edit: Nevermind! Thanks :)
tadly commented on 2020-01-03 11:01 (UTC)
@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)
Pinned Comments
tadly commented on 2020-06-10 06:09 (UTC) (edited on 2020-06-10 06:10 (UTC) by tadly)
!!! 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.