Package Details: wine-staging-git 6.1.r8.g6347bdd1-1

Git Clone URL: (read-only, click to copy)
Package Base: wine-staging-git
Description: A compatibility layer for running Windows programs (staging branch, git version)
Upstream URL:
Keywords: staging windows wine
Licenses: LGPL
Conflicts: wine, wine-wow64
Provides: wine=6.1, wine-staging=6.1.r8.g6347bdd1, wine-wow64
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 16
Popularity: 0.000134
First Submitted: 2016-03-27 06:19
Last Updated: 2021-02-09 19:04

Dependencies (145)

Required by (259)

Sources (4)

Latest Comments

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

Shatur commented on 2018-03-04 10:25

Wine Staging 3.3 released: I suggest to change link in PKGBUILD to this fork.

dbermond commented on 2018-02-24 13:27

@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):

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:

ahjolinna commented on 2018-02-20 09:11

it seems the Lutris people are going to maintain the fork ..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

@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.

ahjolinna commented on 2018-02-18 00:11

@dbermond: have you seen this?

maybe move/change to the fork? (which they recommend)

dbermond commented on 2017-10-03 00:31

Yes, it is now building and working as usual after the rebase commits.
Thank you for the report.

ahjolinna commented on 2017-10-02 23:44

everything works now...(it's A LIVE!! it's A LIVE!!!) back to playing SW:TOR asp (it requires staging to work)

dbermond commented on 2017-09-28 16:32

That's normal and expected.
In my previous comment I have already stated that wine-staging-git can take a little longer to get the fix, since it needs an upstream rebase commit.
And this rebase commit not happened yet at the time of this writing.

ahjolinna commented on 2017-09-28 16:21

wine-git builds now with ft2.8.1 but wine-staging(-git) wont..yet

dbermond commented on 2017-09-24 15:59

@Cork and @ahjolinna
I can reproduce the issue. Thank you for reporting this.
The proposed patch from wine bug #43715 does not fix the building issue. Package still does not build after applying the mentioned patch.
Since this is an upstream problem, there is nothing we can do here on the packaging side. The bug reports were marked as blocker ones and we should wait for an upstream fix. Since we are using wine-staging, things can take a little longer because we may need an upstream rebase commit, and sometimes this happens only near the next release.
The only "solution" currently available is to downgrade freetype, as stated by a wine developer in the duplicated wine bug #43762 (comment #2).