#SUDO APT GET REMOVE WINE INSTALL#

You can identify your architecture with the following command: dpkg -print-architectureĮ.g. The implementation is not perfect so it is still recommended to enable 32-bit architecture, See: If you are running such a version, you may opt to not use multiarch packages. On Wine Versions greater than 7.0, it is possible to run 32 bit applications in a 64 bit Wine environment due to modern ?WoW64 support. This is needed for running 32-bit Windows applications (many modern apps are still 32-bit), but also for large parts of the Windows subsystem itself. On 64-bit systems you should enable a 32-bit architecture for multiarch. Otherwise, dependency non-compliance issues will occur. This procedure works only if the following requirements are met:ġ - Packages migrated to new versions (stable-security) that modify the C libraries have not been installed.Ģ - No packages from deb-multimedia have been installed.

#SUDO APT GET REMOVE WINE INSTALL#

If you install both sets, 'wine' will take precedence unless you configure your system otherwise, see 'Usage' below. You can either install both sets at the same time, or only one of them. Do not mix this up with the *-dev packages which contain the header files and development libraries. version 5.12).ĭespite its name wine-development is also intended to be used by regular users. version 5.0.1), and wine-development the development releases (e.g. Wine tracks the stable releases from (e.g. Since Debian Bullseye, wine-development is no longer available, it is only available in Sid. Since Debian Jessie you can choose between two sets of Wine packages: wine and wine-development. Installing and removing Windows programs.Command names (choosing between wine and wine-development).Installation on Debian Jessie and newer.

Sudo apt get remove wine