Package Details: wine-valve-git 4.2.r270.g06353f78c3-1

Git Clone URL: (read-only)
Package Base: wine-valve-git
Description: A compatibility layer for running Windows programs (Valve version)
Upstream URL:
Licenses: LGPL
Conflicts: bin32-wine, wine, wine-staging, wine-staging-git, wine-wow64
Provides: bin32-wine=4.2.r270.g06353f78c3, wine=4.2.r270.g06353f78c3, wine-valve=4.2.r270.g06353f78c3, wine-wow64=4.2.r270.g06353f78c3
Replaces: bin32-wine
Submitter: Forty-Bot
Maintainer: JoshH100
Last Packager: JoshH100
Votes: 2
Popularity: 0.317629
First Submitted: 2018-11-11 06:14
Last Updated: 2019-04-09 16:22

Dependencies (148)

Required by (221)

Sources (3)

Latest Comments

1 2 Next › Last »

JoshH100 commented on 2019-03-11 20:32

I've removed the harmony font patch and updated the pkgver() function as the upstream repo seems to no longer have tags (perhaps it never did). Anyway it does compile now. Any suggestions are welcome as this package has quite a complex system of makedepends so simplifying would be nice.

Also, I have no idea how upstream is doing versioning and/or tracking Wine upstream. I've taken to just using 3.16.$LAST_COMMIT_DATE. If this causes any issues, let me know.

datafox commented on 2019-03-09 21:01

I just checked why the patch doesn't work and it seems like the new source from Valve has included parts that look similar to the patch to some areas of the code and while I'm not that fluent in C to confirm that it has been fixed upstream, at least something has changed. I'll try removing the patch from the PKGBUILD and report back with my findings.

polensky commented on 2019-02-08 15:39

@MollyMillions I have the exact same problem.

MollyMillions commented on 2019-01-18 13:42

Seems like patches are somewhat out of date, or is it something with my setup?

==> Retrieving sources... -> Found harmony-fix.diff -> Found 30-win32-aliases.conf -> Found wine-binfmt.conf ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources... -> Creating working copy of wine-valve-git git repo... Cloning into 'wine-valve-git'... done. Checking out files: 100% (7666/7666), done. ==> Starting prepare()... patching file dlls/gdi32/freetype.c Hunk #1 FAILED at 996. Hunk #2 FAILED at 7271. Hunk #3 FAILED at 7357. Hunk #4 FAILED at 7439. 4 out of 4 hunks FAILED -- saving rejects to file dlls/gdi32/freetype.c.rej ==> ERROR: A failure occurred in prepare(). Aborting... ==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/molly/build

Forty-Bot commented on 2018-11-29 13:13

Hm, that's not how every other wine variant packages it's stuff. If you submit a patch I'll merge it I suppose.

yannleretaille commented on 2018-11-29 11:03

I can no longer use wine-staging to run programs like office because of bugs like that have been fixed recently (downgrading is also not an an option because it conflicts with wine-staging, but is required for proton). Wouldn't it make more sense to have wine-valve point to its own set of executables instead of fully replacing mainline wine?

bulletproof commented on 2018-11-24 19:59

Please update, if possible.

Forty-Bot commented on 2018-11-14 04:44

This is the version of wine valve ships with proton. If you want it to be updated, pester upstream about it :P

bulletproof commented on 2018-11-14 04:33

Why not 3.20 wine version or same updates contain than wine 3.20 version?

Forty-Bot commented on 2018-11-11 15:35

Ok, thanks for that. I've had some trouble getting this to work due to the very long build time, and because wine already has tons of errors in namcap.