[pkg-wine-party] Bug#825395: winetricks: Remove wine versioned dependence to prevent conflicts with alternative wine

Jens Reyer jre.winesim at gmail.com
Tue Sep 20 13:14:42 UTC 2016

control: tags -1 + patch

Hi Joseph,

On 05/28/2016 10:49 PM, Joseph Bisch wrote:
> I'll make the "Depends" line be:
>  wine | wine-development,
> and the "Recommends" line be:
>  wine (>= 1.8-2) | wine-development (>= 1.9.1-1),

This is probably indeed the correct setup to reflect all
recommendations. But in practice this doesn't enforce specific versions
(which is indeed wanted in order to allow one to install alternative
Wine packages), and I never saw this kind of setup for any other packages.

In a recent discussion on debian-devel [1] it was stated that version
requirements in the packaging should only ensure that the package may be
built, and no severe (data-loss) things happen. However ensuring a fully
bug-free runtime environment is beyond what can be sensibly done in
d/control. We saw that in winetricks already.

wine-development (stretch/sid/jessie-backports) employs the alternatives
system for wine, so with wine-development installed /usr/bin/wine and
/usr/bin/wineserver exist, which is what winetricks requires.
To reflect this fact that wine-development is now a full replacement for
wine it now has a "Provides: wine" in d/control.

Long story short: I suggest to remove every Wine related dependency
except an unversioned "Depends: wine". See attached patch, based on your
0.0+20160425-2 (uploaded to mentors.do on 2016-05-28 21:26).


[1] Adding version constraints in dependencies to avoid bugs,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch0.patch
Type: text/x-patch
Size: 516 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-wine-party/attachments/20160920/64041e55/attachment.bin>

More information about the pkg-wine-party mailing list