A failure occurred in build().

[Aerialflame7125]

Arch Linux;

Mainly attempted to install wine-tkg-roblox via the tutorial here:
Here is prepare.log:
prepare.log

[noisecode3]

This happens when I build an older wine like 9.8, with the vulkan child window proton patch

HEAD is now at 655de4b0bf0 Release 9.8.

childwindow-proton-5481415.patch -- ( Applied child window for vk patch )
patching file dlls/win32u/ntuser_private.h
Hunk #1 succeeded at 258 (offset 1 line).
patching file dlls/win32u/vulkan.c
Hunk #9 FAILED at 298.
Hunk #10 FAILED at 326.
Hunk #11 succeeded at 305 (offset -55 lines).
2 out of 11 hunks FAILED -- saving rejects to file dlls/win32u/vulkan.c.rej
patching file dlls/win32u/window.c
patching file dlls/winemac.drv/vulkan.c
patching file dlls/winewayland.drv/vulkan.c
patching file dlls/winex11.drv/vulkan.c
patching file dlls/winex11.drv/window.c
Hunk #1 succeeded at 1469 (offset 13 lines).
Hunk #2 succeeded at 1636 (offset 13 lines).
Hunk #3 succeeded at 1646 (offset 13 lines).
Hunk #4 succeeded at 1838 (offset 13 lines).
Hunk #5 succeeded at 1857 (offset 13 lines).
Hunk #6 succeeded at 1865 (offset 13 lines).
Hunk #7 succeeded at 2718 (offset 65 lines).
patching file dlls/winex11.drv/x11drv.h
Hunk #1 succeeded at 656 (offset 7 lines).
patching file include/wine/vulkan_driver.h

You see it failed at 298 and 326; It's just c and we can figure that out easy by just looking at the old/new patch and the code and see what its about and what is going.

That patch might not be the most important so it can still work but should be addressed at some point

[noisecode3]

so in my case with wine 9.8 it was just before it implemented lazy vulkan functions. To fix this it can check if its before it had lazy vulkan so it should add this patch before it add the this one. In you're case it was the config file is that still a problem?
I can pr this one but not sure you're problem is still present
some line like that should be the problem
git merge-base --is-ancestor 5481415d438d41ac2b9fe42beb669d19af3af974 HEAD;

[noisecode3]

no Im not doing that, maybe organize patches with a number 0000-name.patch... like that for a start. its too messy.. do I have to script something just to find the patch ord.. Im out