![]() The following example commands make sure that all required packages are pulled from bullseye-backports instead of bullseye.ĭo not simply use "apt install -t bullseye-backports wine" instead of the following example commands. But once they are installed you receive automatic updates. Packages from backports are not installed automatically. To enable bullseye-backports add this line to your sources.list (or add a new file with the ".list" extension to /etc/apt//): deb bullseye-backports main Install wine-development on a 32-bit architecture: sudo apt install \įor Debian Bullseye wine is available as backport. Install wine-development on a 64-bit architecture (amd64 with i386 as foreign 32-bit architecture): sudo dpkg -add-architecture i386 & sudo apt update Install wine on a 32-bit architecture: sudo apt install \ Install wine on a 64-bit architecture (amd64 with i386 as foreign 32-bit architecture): sudo dpkg -add-architecture i386 & sudo apt update Install wine on a 64-bit architecture: $sudo apt install \ "sudo apt install libpulse0:i386/testing"), and then continue to install Wine. To solve this install the i386 package from the same suite as the already installed amd64 package (e.g. Debian Backports or Unstable) then some newly needed i386 packages might have another version, and you face broken dependencies. But if you install Wine from another suite (e.g. ![]() These packages are the versions from your default release, e.g. Usually you already have most of the required amd64 library packages installed. amd64 and i386 to be in exactly the same version. It's quite easy to run into broken dependencies when installing Wine: The multiarch setup requires packages from e.g. To run 32-bit Windows applications on (this is the most common case, independently of your Debian architecture) make sure that wine32 (or wine32-development) is installed (requires step 1) This is not required on Wine versions >7.0. This should automatically install all other required packages if you already have enabled multiarch (step 1). You always need to install the wine (or wine-development) package. Enable it with the following command: sudo dpkg -add-architecture i386 & sudo apt update for amd64 (which most users have) you may need i386. 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. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |