Arbitrary dependency on specific Wine version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pq (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pq
The current dependency on specific Wine version (>= 0.9.46) is completely arbitrary. Technically the dependecy should be either 1) changed to a specific version recommended by upstream, 2) changed to a specific version based on (serious?) problems on (every?) earlier version of Wine, or 3) replaced with a version-less dependency definition. Changing the version definition thusly would allow people to run the package on platforms that ship with some early version of Wine.
The question of how we should deal with this however, is quite interesting as Progress Quest has some minor problems even with the latest Wine versions. So what does the policy exactly state? Should we eventually depend on a Wine version that has zero problems, or should we downgrade the requirement to the first version of Wine that barely worked?
It seems the arbitrary dependency breaks the package with latest wine from winehq. So it should be fixed.