wine (10.0~repack-12) unstable; urgency=medium

    With this release, 32-bit Windows applications are now supported natively
    on amd64 and arm64. The wine32 package and multiarch are no longer strictly
    necessary.

    Certain 32-bit applications do not currently perform as well with wine64
    compared to the purely native wine32 build. As such, the multiarch wine32
    package continues to be provided and supported.

    If wine64 and wine32 are both co-installed, the Debian Wine helper script
    now defaults to wine64.

    When migrating from prior versions of the Debian packages, "$HOME/.wine"
    may still be a 32-bit prefix. You will see an error stating this when
    launching wine or wine64. If you run into this, the easiest solution is
    to move the old 32-bit prefix where wine32 will use it by default:
    $ mv $HOME/.wine $HOME/.wine32

    Additionally, the /usr/bin/wineserver helper script is no longer included.
    The wineserver version appropriate to the desired architecture tuple "*"
    may be launched manually from /usr/lib/*/wine/. For more info, please see:
    $ man wineserver

    Finally, the name for the group of wine alternatives has been changed from
    wine to wine.collection. To configure wine's alternatives, please execute:
    $ sudo update-alternatives --config wine.collection

    Please see /usr/share/doc/wine-common/README.Debian.gz for more detail.

 -- Michael Gilbert <mgilbert@debian.org>  Tue, 21 Oct 2025 21:55:00 +0000

wine (4.0~rc2-1) unstable; urgency=medium

  The package wine-binfmt (not part of a standard Wine installation) will now
  automatically register Wine as interpreter for Windows executables.  This
  causes Wine to be invoked automatically whenever a matching file is executed.
  (Previously wine-binfmt only installed support for this, but you still needed
  to activate it manually.)

  Warning: This increases the risk of inadvertently launching Windows malware,
  so please make sure that you understand the security risks before installing
  this package.

  For more information please refer to Wine's README.Debian.

 -- Jens Reyer <jre.winesim@gmail.com>  Sun, 28 Jan 2018 18:51:42 +0100

wine-development (1.9.16-1) unstable; urgency=medium

  Debian has two sets of Wine packages: wine and wine-development. They now use
  the Debian alternatives system to provide /usr/bin/wine and other commands.

  If both are installed this system defaults to use the commands provided by
  wine (no change in behavior because wine already provided these unsuffixed
  commandnames previously).

  But if configured, or if only wine-development is installed, you may now use
  wine-development's commands without the "-development" suffix.

  For more information on this please have a look at README.Debian.

 -- Jens Reyer <jre.winesim@gmail.com>  Sun, 24 Jul 2016 23:43:42 +0200

wine-development (1.9.0-2) unstable; urgency=medium

  Wine now uses a shared 64-bit wineprefix per default if wine32 and wine64 (or
  wine32-development and wine64-development) are installed. For more
  information on this please have a look at README.Debian.

  * The package wine (or wine-development) needs to be installed in any case
    now.
  * Existing 32-bit wineprefixes don't get changed and continue to work.
  * Existing 64-bit wineprefixes in $HOME/.wine64 aren't found
    automatically anymore if you are running Wine from a terminal, while
    Desktop launchers continue to work. You may rename the prefix to
    $HOME/.wine and adjust any launcher, or run:
    $ export WINEPREFIX="$HOME/.wine64"
  * The wineserver is now in PATH, its old filepath doesn't exist
    anymore. Any existing WINESERVER configuration must be dropped or
    adjusted.

 -- Jens Reyer <jre.winesim@gmail.com>  Sun, 10 Jan 2016 00:51:06 +0100