Package Details: wine-staging-git 8.2.r7.g7b0d44f8-1

Git Clone URL: https://aur.archlinux.org/wine-staging-git.git (read-only, click to copy)
Package Base: wine-staging-git
Description: A compatibility layer for running Windows programs (staging branch, git version)
Upstream URL: https://www.wine-staging.com/
Keywords: staging windows wine
Licenses: LGPL
Conflicts: wine, wine-wow64
Provides: wine, wine-staging, wine-wow64
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 18
Popularity: 0.000000
First Submitted: 2016-03-27 06:19 (UTC)
Last Updated: 2023-02-25 13:42 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

dbermond commented on 2018-12-11 13:51 (UTC)

@C0rn3j This can be a lot of things on your system or even on the machine. Try to build in a clean chroot and see if it works.

C0rn3j commented on 2018-12-11 10:05 (UTC)

https://haste.rys.pw/raw/acibawakus I can't build this package on a system with Ryzen 2400G, it works on a Ryzen 1700 box. Compressed compilation folder (0.5GB) - https://cloud2.rys.pw/s/oNyL9DQc5TFN76d

It seems to fail on random things each run.

during RTL pass: final ../../../wine-git/dlls/wined3d/arb_program_shader.c: In function ‘shader_arb_select’: ../../../wine-git/dlls/wined3d/arb_program_shader.c:4688:1: internal compiler error: Segmentation fault

dbermond commented on 2018-10-11 21:41 (UTC)

@SilverSynch Thank you for reporting this. Package updated.

SilverSynch commented on 2018-10-11 16:58 (UTC)

The Freetype Harmony fix has been merged in Wine. It cannot remain in the package as the patch fails to apply.

https://source.winehq.org/git/wine.git/commit/66e446c5ec5c7f4f072358712151d75305dfbd49

dbermond commented on 2018-03-04 20:15 (UTC)

Important notice:

Upstream wine-staging hosted at 'https://github.com/wine-compholio/wine-staging/' is no more maintained. A community fork is now maintained at 'https://github.com/wine-staging/wine-staging/'.

As a result, the source repository of this package has changed. If you have a copy of the old source repository on disk and want to upgrade the package, please follow this step: before running makepkg, delete the directory wine-staging-git from the location where the PKGBUILD file is placed. New users building the package for the first time does not need to do anything.

Shatur commented on 2018-03-04 10:25 (UTC)

Wine Staging 3.3 released: https://github.com/wine-staging/wine-staging/releases I suggest to change link in PKGBUILD to this fork.

dbermond commented on 2018-02-24 13:27 (UTC)

@ahjolinna As far as I can tell, the new wine-staging will not be maintained by the Lutris team.

It will be maintained by Alistair at the following repository (which is not from Lutris): https://github.com/wine-staging/wine-staging/

The Lutris post on Twitter that you shared is just some news about the new wine-staging repository. It does not mean that they are now maintaining it. It seems that the people who commented there do not get the point.

See here: https://www.winehq.org/pipermail/wine-devel/2018-February/123080.html

ahjolinna commented on 2018-02-20 09:11 (UTC)

it seems the Lutris people are going to maintain the fork https://twitter.com/LutrisGaming/status/965329572873949184 ..but I'm not sure but could be that they are not going to release any new patches, only existant patches will be refreshed for each version of Wine...which is fine (for now)

dbermond commented on 2018-02-18 17:09 (UTC)

@ahjolinna Yes, I'm aware of all this situation and the surrounding discussions. Although the wine-staging news page mention the fork made by Alistair (github user @alesliehughes), there is currently no official word from the wine team of what will become wine-staging, and there is no guarantee that this fork will be the new wine-staging post-3.0. So I think that it's a bit early to change things here, and that it will be more prudent to wait a little longer to see how this transition will be adopted and received by the mainstream people. Besides, the current wine-staging 2.21 is building and working fine. Thank you for the interest. Let's see how this will develop in the (hopefully) near future.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »