| Git Clone URL: | https://aur.archlinux.org/sunshine-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | sunshine-bin |
| Description: | A self-hosted game stream host for Moonlight. |
| Upstream URL: | https://app.lizardbyte.dev |
| Keywords: | gaming moonlight streaming |
| Licenses: | GPL-3.0-only |
| Conflicts: | sunshine |
| Provides: | sunshine |
| Submitter: | chungn |
| Maintainer: | chungn (escape0707) |
| Last Packager: | escape0707 |
| Votes: | 12 |
| Popularity: | 0.167592 |
| First Submitted: | 2023-03-27 15:27 (UTC) |
| Last Updated: | 2025-03-30 04:09 (UTC) |
@TheJackofClubs Can you try yay -S sunshine-bin --rebuild or vanilla makepkg -sif and see what happens?
Edit: Anyway, you probably don't want to use this package because of this, and I recommend you to use bin package that tracks beta versions or upstream bin repo for now instead.
Yep, vanilla and yay. miniupnpc updated yesterday. It wouldn't update with sunshine-bin installed so I uninstalled, updated, tried to reinstall sunshine-bin and have that error.
@TheJackofClubs That's some very weird error messages that I've never seen. Are you using vanilla Arch/yay or some forks?
unable to satisfy dependency 'libminiupnpc.so=19-64' required by sunshine-bin
There is no such dependency restriction in the definition of this package.
update to miniupnp breaks this package
warning: sunshine-bin-debug-2025.122.141614-2 is up to date -- reinstalling resolving dependencies... warning: cannot resolve "libminiupnpc.so=19-64", a dependency of "sunshine-bin" :: The following package cannot be upgraded due to unresolvable dependencies: sunshine-bin :: Do you want to skip the above package for this upgrade? [y/N] error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'libminiupnpc.so=19-64' required by sunshine-bin -> error installing: [/home/.cache/yay/sunshine-bin/sunshine-bin-2025.122.141614-2-x86_64.pkg.tar.zst /home/.cache/yay/sunshine-bin/sunshine-bin-debug-2025.122.141614-2-x86_64.pkg.tar.zst] - exit status 1
Please do not flag this package as outdated unless there is a newer release from upstream.
If there are dependency issues, please leave a comment here. Sometimes they are mitigable. However, if that is not the case, it is preferable to keep the flagging feature available so maintainers are notified to adopt a newer build more quickly.
@escape0707 indeed, my bad, transferring where appropriate
@Sahnvour This is sunshine-bin here. Maybe you were posting about sunshine?
Apparently requires libsimdjson?
[9/39] Installing NPM Dependencies and Building the Web UI
FAILED: CMakeFiles/web-ui /home/a/.cache/aura/builds/sunshine/src/build/CMakeFiles/web-ui
cd /home/a/.cache/aura/builds/sunshine/src/sunshine && /usr/bin/npm install && /usr/bin/cmake -E env SUNSHINE_BUILD_HOMEBREW= SUNSHINE_SOURCE_ASSETS_DIR=/home/a/.cache/aura/builds/sunshine/src/sunshine/src_assets SUNSHINE_ASSETS_DIR=/home/a/.cache/aura/builds/sunshine/src/build /usr/bin/npm run build
node: error while loading shared libraries: libsimdjson.so.25: cannot open shared object file: No such file or directory
@antoyo This type of dependency breakage problem WOULD happen for dynamic linking software in binary package form for a rolling release system. When ever this happens, there is no real solutions other than: 1. build from the source code. 2. update to a newer upstream binary build recently.
The official GitHub repo doesn't release new versions very often. So for those who don't like to build from the source, the software author prepared a nightly binary build repo for this purpose: https://github.com/LizardByte/pacman-repo
I'm not sure if we should grab a binary package from there whenever a dependency breakage happens. Any advices?
A problem with that approach is that the pacman-repo GitHub release seems doesn't provide fixed permanent links for the binaries. So I'll have to skip checksums.
I also had the same issue with the icu76 update. I just installed aur/sunshine (the non-prepbuilt version) and it works without downgrading icu.
Pinned Comments
escape0707 commented on 2025-05-14 14:31 (UTC) (edited on 2025-05-14 14:33 (UTC) by escape0707)
Please do not flag this package as outdated unless there is a newer release from upstream.
If there are dependency issues, please leave a comment here. Sometimes they are mitigable. However, if that is not the case, it is preferable to keep the flagging feature available so maintainers are notified to adopt a newer build more quickly.