Quack, On 2022-03-11 21:52, Adrian Bunk wrote:
dxvk should have an RC bug documenting why it is not in testing, and this bug in dxvkshould be fixed by using the non-development version of wine.
I agree documenting is nice but this is not my decision. It is unlikely that wine maintainers would change their mind and push -devel in a stable release but if that were to happen then this package would needlessly be blocked by this bug now. The fact that it does not work with wine-stable is another matter entirely.
As for the use of wine-stable as stated previously I have no idea what are the consequences of building with an old version and using it with the -devel one. Creating a dxvk-stable would be safer but since I never use wine-stable I would not wish to maintain it. I do not have any knowledge of the DXVK or wine code and did not have time to look into it or ask upstream about it, but if you do then I'll be happy to hear about it (you seem to be sure that's the obvious solution so I guess you do).
For testing migration of dxvk this does not make a difference, but it highlights that there is a bug in dxvk that needs fixing.
This is a new feature of the package, thus "wishlist" severity. And I'm not going to skip over this BR just because the severity is not RC.
Anyway, that does not change much but I find it very annoying when people play with severity without explaining why. I think mixing the not-in-stable and does-not-work-with_wine-stable questions is confusing.
Regards. \_o< -- Marc Dequènes
