Package Details: proton-ge-custom-bin 1:GE_Proton9_20-1

Git Clone URL: https://aur.archlinux.org/proton-ge-custom-bin.git (read-only, click to copy)
Package Base: proton-ge-custom-bin
Description: A fancy custom distribution of Valves Proton with various patches
Upstream URL: https://github.com/GloriousEggroll/proton-ge-custom
Keywords: d9vk DXVK Faudio GloriousEggroll MediaFoundation Proton protonfixes Steam System-wide Valve vkd3d Wine
Licenses: custom, BSD, MPL, LGPL, MIT, zlib
Conflicts: proton-ge-custom
Provides: proton, proton-ge-custom
Submitter: RogueGirl
Maintainer: Jaja (floriplum, chaotic-aur, PedroHLC)
Last Packager: chaotic-aur
Votes: 215
Popularity: 7.38
First Submitted: 2020-02-21 11:06 (UTC)
Last Updated: 2024-11-11 11:31 (UTC)

Dependencies (28)

Required by (7)

Sources (4)

Pinned Comments

PedroHLC commented on 2021-07-27 19:39 (UTC)

The "chaotic-aur" co-maintainer is a bot that pulls any merged PR in https://github.com/chaotic-aur/pkgbuild-proton-ge-custom-bin back to this package. So if you guys have contributions or bump versions earlier than the maintainer, please share them as PRs. The commits will keep your authorship.

Happy gaming!

Latest Comments

1 2 3 4 5 6 .. 26 Next › Last »

Strykar commented on 2024-09-24 12:15 (UTC)

Updating to 9_14-1 threw the non-fatal warning:

libfakeroot internal error: payload not recognized!

No other issues noticed, full log - https://gist.github.com/Strykar/964042e756a609469560e9b995b2aedc

sir-wallaby commented on 2024-09-02 18:14 (UTC)

@PedroHLC I actually did notice the rm errors, but I did not want to impose on the repo by making too many changes. Sorry all!

blueman commented on 2024-09-02 14:56 (UTC)

Thanks :)

blueman commented on 2024-09-01 19:04 (UTC)

Can you bump the pkgrel number so the package gets re-downloaded with the fix included? paru still has the same error.

PedroHLC commented on 2024-09-01 17:07 (UTC)

My mistake, I thought I had merged the PR with fixes before pushing. Sorry!

Thank sir-wallaby and fpetros1 for the bump and fix.

otakian commented on 2024-09-01 16:58 (UTC) (edited on 2024-09-01 17:07 (UTC) by otakian)

It's some issue with the Protonfixes folder, it no longer has any tar or git files in it and the license file is no longer there.

Commenting out lines 90,91, and 106 is all it takes for the script to run correctly. So my best guess is the protonfix folder inside of the proton-ge package has been modified to be extracted and license file no longer located within but would need one of the packagers to confirm.

trinaldi commented on 2024-09-01 16:45 (UTC) (edited on 2024-09-01 16:49 (UTC) by trinaldi)

@veganvelociraptr, same here, so until a new fix comes, I removed the rm commands from build() and also the #Licenses and its mvs from PKGBUILD.

My PKGBUILD https://gist.github.com/trinaldi/62362ac0953b935964f489a425dedf6d

Then moved the LICENSES as intended

veganvelociraptr commented on 2024-09-01 15:07 (UTC) (edited on 2024-09-01 15:08 (UTC) by veganvelociraptr)

This happens when I try to update from 9_11-1 to 9_12-1:

==> Starting build()...

rm: cannot remove 'GE-Proton9-12/protonfixes/*.tar.xz': No such file or directory

==> ERROR: A failure occurred in build().

Aborting...

jacklul commented on 2024-08-03 18:38 (UTC)

@PedroHLC I actually meant 10-games.conf, my mistake. I can see that there doesn't seem to be /usr/*/limits.d/ dir so putting it in /etc one is the way to go. All good, I just didn't understand it correctly.

PedroHLC commented on 2024-07-25 19:52 (UTC)

@jacklul we're not editing pam_limits.conf, we create a file in limits.d that is supposed to belong to this package (owned) and has the impact required for this software in a way that should not be edited by the user later.

1 2 3 4 5 6 .. 26 Next › Last »