How to find out if a patch set was already implemented or no

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
Barafu Albino
Newbie
Newbie
Posts: 1
Joined: Thu Mar 28, 2019 7:11 am

How to find out if a patch set was already implemented or no

Post by Barafu Albino » Thu Mar 28, 2019 7:24 am

I have encountered a problem with an application installer. I have found this discussion https://bugs.winehq.org/show_bug.cgi?id=23934 that describes a very similar problem and a patch set that should solve it.
I tried to install wine-staging and create a new prefix, but it did not solve the problem.

How can I find out if a patch in discussion is applied to wine-staging package or not? Because if not, then I need to learn how to compile wine, apply patches, install it. If yes, then the patch does not help me and I should not spend time on this, instead I should find some workarounds.

User avatar
dimesio
Moderator
Moderator
Posts: 12743
Joined: Tue Mar 25, 2008 10:30 pm

Re: How to find out if a patch set was already implemented o

Post by dimesio » Thu Mar 28, 2019 8:04 am

If the bug status is STAGED, as it is for the bug you linked to, that means the patch is in wine-staging.

User avatar
Bob Wya
Level 12
Level 12
Posts: 2813
Joined: Sat Oct 16, 2010 7:40 pm
Location: Scotland
Contact:

Re: How to find out if a patch set was already implemented o

Post by Bob Wya » Sun Mar 31, 2019 4:11 pm

Barafu Albino wrote:I have encountered a problem with an application installer. I have found this discussion https://bugs.winehq.org/show_bug.cgi?id=23934 that describes a very similar problem and a patch set that should solve it.
I tried to install wine-staging and create a new prefix, but it did not solve the problem.

How can I find out if a patch in discussion is applied to wine-staging package or not? Because if not, then I need to learn how to compile wine, apply patches, install it. If yes, then the patch does not help me and I should not spend time on this, instead I should find some workarounds.
@Barafu Albino

Clone the wine-staging git tree and test alterations to the patchset in question.
In your case this patchset was first introduced years ago...
More crucially it was last updated with Wine Staging release 3.19 ...

It would appear your Wine problems are of a different nature... Your problem being what exactly?

Are you running the application directly from the "correct" directory? (Bearing in mind that Windows will search the present working directory first for both libraries and executable files...)
See: WineHQ User's Guide: 3 Using Wine

Bob

Locked