Package Details: sunshine-bin 2025.122.141614-2

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: 13
Popularity: 1.34
First Submitted: 2023-03-27 15:27 (UTC)
Last Updated: 2025-02-20 06:26 (UTC)

Latest Comments

1 2 3 4 Next › Last »

antoyo commented on 2025-02-21 02:22 (UTC)

I know get the following error when trying to run this package:

sunshine: error while loading shared libraries: libicuuc.so.75: cannot open shared object file: No such file or directory

Using patchelf to fix this leads to another error:

sunshine: symbol lookup error: sunshine: undefined symbol: ucnv_getMaxCharSize_75

Any idea of how to fix this? Thanks.

escape0707 commented on 2025-02-20 06:27 (UTC)

Hi, @krims0n @steakscience

I reapplied the patchelf hack and I think the latest version runs. Please update and give it a try.

krims0n commented on 2025-02-12 09:08 (UTC)

sunshine: error while loading shared libraries: libminiupnpc.so.18: cannot open shared object file: No such file or directory

Downgrading miniupnpc to 2.2.8 is a workaround.

steakscience commented on 2025-02-05 19:07 (UTC)

I think the latest update created an issue with: error while loading shared libraries: libminiupnpc.so.18: cannot open shared object file

zhengnanlee commented on 2024-09-04 04:08 (UTC)

It seems that the sunshine-bin, as of today (Sep. 04, 2024), requires boost v1.83, which is now obsolete.

<deleted-account> commented on 2024-07-12 17:59 (UTC)

@escape0707 To clarify, the pacman-repo we provide has both stable and beta prebuilt packages. So effectively equivalent of AUR sunshine (un-compiled stable), sunshine-bin (compiled-stable), and sunshine-git (un-compiled beta)... but not if anyone is applying custom patches.

The repo holds the stable PKGBUILD, and downloads the beta PKGBUILD from GitHub releases.

The stable build we provide will include patches that are required for compilation, such as the recent miniupnpc patch.

I have no issue if you want to keep using this AUR repo, I just ask that anyone filing bugs try the officially provided versions first. sunshine-bin is pretty low risk though as it's basically just one of our release assets.

escape0707 commented on 2024-07-11 06:55 (UTC)

@LizardByte

Thank you, sir, for the information here and your effort when you helped me to solve problems at the upstream GitHub.

To my understanding, the pacman-repo you provide now is more like a -nightly build of the package and since this is a -bin package, usually the convention is to follow upstream stable release versions. The nightly build might be a good workaround to use when some breakage like this miniupnp one happen in the future. But it not that easy to track the version of it and might be a step further away from "reproducibility". As for this -bin package, maybe only bug reproducibility might be relevant, although managing tar file checksum might get harder, too. For these reasons, I think this -bin package that tracks stable release would probably still stay here for those who don't want to download nightly versions every day. In this regard, consistent upstream prebuild package support and nightly build support definitely help!

And I think sunshine-git will not be obsolete, because some AUR users might use those -git packages and add some custom patch to the build process to satisfy their own flavor. And I wish when these users encounter any problems, they will take they own responsibility to verify the issue with upstream suggested manual build procedure and confirm and provide all the info they will give independently when creating a bug report at the upstream. This effectively circumvents AUR (which basically just bash build scripts ;) ) and should satisfy the upstream requirement of probably in the future not going to accept bug encountered with some AUR packages.

Also, either version of appindicator is okay!

Thank you for clarifying this and continuously devoting your effort into this very useful software project!

Best regards!

<deleted-account> commented on 2024-07-10 18:43 (UTC)

Sorry for all the drama in the other AUR repo. Hope you brought popcorn...

We will still release an archive of the PKGBUILD as well as pre-built packages in GitHub releases going forward. We also now have our own pacman-repo, which will serve pre-built packages that are rebuilt on a daily basis. You may want to grab pre-builds from there?

This is the repo, https://github.com/LizardByte/pacman-repo

In the near future I'm planning to add the beta/pre-release to that repo as well, which may make sunshine-git and sunshine-bin obsolete.

Also, either version of appindicator is okay!

escape0707 commented on 2024-07-09 03:46 (UTC)

@pyamsoft

Since ayatana is installed and preferred by upstream, libappindicator-gtk3 should be dropped from the dependency list.

Thanks for the heads-up. I reverted my change of adding libappindicator-gtk3.

Future releases of the project may not include Archlinux packaged sources

From what I've read in the upstream PR, it seems that upstream will still release prebuilt binary packages. I guess we'll just stick to what we have now. And it seems that the upstream as filed an orphan / takeover request against the sunshine package, and more discussion might happen there. I hope it can go to a good direction.

pyamsoft commented on 2024-07-09 01:57 (UTC)

Also, please note that the upstream has dropped support for Archlinux and the AUR because of maintainer burnout and online harassment. https://github.com/LizardByte/Sunshine/pull/2819

Future releases of the project may not include Archlinux packaged sources, so you may need to prepare for a future where you extract the release from one of the other releases like the DEB or RPM.

Thanks!

1 2 3 4 Next › Last »