[pkg-wine-party] wine 1.4.1-1.2: 64/32-bit support, proper multiarch dependencies

Hilko Bengen bengen at debian.org
Sun Jul 1 17:16:28 UTC 2012

After lots of probing around how multiarch dependencies are
specified, how dpkg/apt/aptitude handle them, and what Lintian has to
say about the results, here's my seoncd NMU to experimental.

What do you think about adopting these changes in unstable and talking
to the release team for a freeze exception?


I have been able to upgrade packages from wine 1.0.1-3.6 to 1.4.1-1.2
without problems. Upgrading from the previous experimental version is
unlikely to work correctly.

Here are the main differences to 1.4.1-1 (unstable):

- wine, wine-preload, and their 64-bit counterparts have been split
  off into wine-loader-32 and wine-loader-64 packages, respectively.
  On amd64 systems, a fake wine-loader-32 package is provided whose
  sole purpose is to inform the user how he can set up a multiarch

- wineserver has been split off into the wine-server package which is
  "Multi-Arch: allowed". It only makes sense to have one instance (per
  Wine version) installed at a time, but as far as I know, a 64-bit
  libwine can't talk to a 32-bit wineserver. This is reflected in the

- wine, wine-preload, wineserver now live in /usr/bin as intended by
  upstream, allowing me to back out most path modifications for
  libwine (the *SUFFIX changes are still there).

  This solved a problem with wineboot not being able to find wine.inf.
  If I recall correctly, lintian also had bad things to say about
  executables in a multiarch libdir of a "Multi-Arch: same" package.

- The alternatives setup scripts are no longer used. They complicated
  my work to a point where I got annoyed enough to disable them.

  I wouldn't object to re-enabling them, but, frankly, I don't see the
  benefit in having alternatives for the 32 vs. 64 bit versions of
  notepad.exe or any other Windows system program.

- Build tools have been split off from libwine-dev into the
  libwine-dev-tools package. I did this early in the process when I
  still believed that the 64-bit tools were needed to build a special
  version of some 32-bit components. (Good thing I asked on wine-dev.)
  FWIW, libwine-dev could be made "Mult-Arch: same" now.

More information about the pkg-wine-party mailing list