Currently the 9999 ebuild does not verify if the staging patchset is compatible with the wine repo. The patchinstaller has an option "--upstream-commit" which prints out the SHA1 hash of the upstream commit. Using that we can checkout the correct git commit for wine to successfully apply the staging patches. I have a little hacked ebuild that works for me locally but as I made some more changes I would not like to put up a patch for that, tbh. Reproducible: Sometimes Steps to Reproduce: 1.emerge wine-9999 when wine repo is not the version staging repo was rebased against. 2. 3.
Patches welcome as this isn't high on my to-do list. It's also not critical as staging usually only lags by a hour or so when they do break upstream compatibility.
Created attachment 424130 [details, diff] wine-9999.ebuild patch Needs a small rework for the patches section, see the FIXME there.
Rebased my local overlay to the current ebuild and uploaded the diff here. Note the FIXME, those file were not in my local overlay thus building failed.
(In reply to Nico (Keridos) from comment #2) > Created attachment 424130 [details, diff] [details, diff] > wine-9999.ebuild patch > > Needs a small rework for the patches section, see the FIXME there. Calling git directly is highly undesirable, the git-r3 eclass should be utilized. Also, the actions involving git manipulating the sources should happen in the src_unpack phase.
Fixed in 4469bdbf74cebf43c949f218a202caf0f5b70f99
