Difference between revisions of "Debian"

From WineHQ Wiki
Jump to: navigation, search
(Restore the Debian Buster link)
 
(29 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{info}} WineHQ only builds binary packages for the development and staging branches, in order to encourage widespread testing of bugfixes and new features by ordinary users. Binary packages for the stable branch are the responsibility of the distros. If you are looking for an updated stable package, ask your distro where to find it.
+
__NOTOC__
 
+
'''Translations of this page:'''  {{flag|China}} [[Debian_zhcn|简体中文]] {{flag|Netherlands}} [[Debian_nl|Nederlands]]
 
== Installing WineHQ packages ==
 
== Installing WineHQ packages ==
 +
{{warning}} '''The WineHQ repository key was changed on 2018-12-19. If you downloaded and added the key before that time, you will need to download and add the new key and run sudo apt update to accept the repository changes.'''
  
First, enable 32 bit packages:
+
{{warning}}'''The WineHQ packages for Debian 10 and later require libfaudio0 as a dependency. Since the distro does not provide it for Debian 10, users of that version can download libfaudio0 packages from the OBS. See https://forum.winehq.org/viewtopic.php?f=8&t=32192 for details.'''
  
sudo dpkg --add-architecture i386
+
{{info}} '''''Raspbian users:''' the WineHQ packages are for x86 architecture only; they cannot be installed on an ARM system.''
  
Then install key which was used to sign packages:
+
Enable 32 bit packages (if you haven't already):
  
  wget https://dl.winehq.org/wine-builds/Release.key
+
  sudo dpkg --add-architecture i386
sudo apt-key add Release.key
 
 
 
Next add the repository to /etc/apt/sources.list or create a *.list under /etc/apt/sources.list.d/ with the following content:
 
  
deb https://dl.winehq.org/wine-builds/debian/ DISTRO main
+
Download and install the repository key:
  
with DISTRO being either wheezy, jessie, stretch or sid
+
wget -nc https://dl.winehq.org/wine-builds/winehq.key
 +
sudo apt-key add winehq.key
  
''To avoid problems with missing dependencies, Wheezy users should also add the following to /etc/apt/sources.list (if it is not already there):''
+
Add the repository to /etc/apt/sources.list or create a *.list under /etc/apt/sources.list.d/ with the following content:
 
+
{|  style="width: 100%" class="wikitable"
deb http://ftp.de.debian.org/debian/ oldstable main
+
!For this version:
 +
!Add this content to /etc/apt/sources.list:
 +
|-
 +
|Debian 10 (Buster)
 +
| deb https://dl.winehq.org/wine-builds/debian/ buster main
 +
|-
 +
|Debian 11 (Bullseye)
 +
| deb https://dl.winehq.org/wine-builds/debian/ bullseye main
 +
|-
 +
|Debian Testing (Bookworm)
 +
| deb https://dl.winehq.org/wine-builds/debian/ bookworm main
 +
|}
  
 
Update packages:
 
Update packages:
  
  sudo apt-get update
+
  sudo apt update
 
 
Then install (example for the development branch):
 
  
sudo apt-get install winehq-devel
+
Then install '''one of the following packages''':
  
If you prefer to use the Staging branch, replace `winehq-devel` with `winehq-staging` in the line above.
+
{|  style="width: 100%" class="wikitable"
 +
! Stable branch
 +
|
 +
sudo apt install --install-recommends winehq-stable
 +
|-
 +
! Development branch
 +
|
 +
sudo apt install --install-recommends winehq-devel
 +
|-
 +
! Staging branch
 +
|
 +
sudo apt install --install-recommends winehq-staging
 +
|}
  
If apt-get complains about missing dependencies, install them, then repeat the last two steps (update and install).
+
If apt complains about missing dependencies, install them, then repeat the last two steps (update and install).
  
 
----
 
----
Line 38: Line 58:
 
'''Some notes on the WineHQ packages:'''
 
'''Some notes on the WineHQ packages:'''
  
* Files are installed to /opt/wine-devel.
+
* Files are installed to /opt/wine-devel or /opt/wine-staging.
  
 
* Menu items are not created for Wine's builtin programs (winecfg, etc.), and if you are upgrading from a distro package that had added them, they will be removed. You can recreate them yourself using your menu editor.
 
* Menu items are not created for Wine's builtin programs (winecfg, etc.), and if you are upgrading from a distro package that had added them, they will be removed. You can recreate them yourself using your menu editor.
  
 
* WineHQ does not at present package wine-gecko or wine-mono. When creating a new wine prefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here. If the download doesn't work for you, please follow the instructions on the [http://wiki.winehq.org/Gecko Gecko] and [http://wiki.winehq.org/Mono Mono] wiki pages to install them manually.
 
* WineHQ does not at present package wine-gecko or wine-mono. When creating a new wine prefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here. If the download doesn't work for you, please follow the instructions on the [http://wiki.winehq.org/Gecko Gecko] and [http://wiki.winehq.org/Mono Mono] wiki pages to install them manually.
 +
 +
* Beginning with Wine 5.7, the WineHQ Debian packages have an optional debconf setting to enable CAP_NET_RAW to allow applications that need to send and receive raw IP packets to do so. This is disabled by default because it carries a potential security risk, and the vast majority of applications do not need that capability. Users of applications that do need it can enable CAP_NET_RAW after installing Wine by running
 +
dpkg-reconfigure wine-<branch>-amd64 wine-<branch> wine-<branch>-i386
 +
and answering yes to the three questions. (Substitute devel, staging, or stable for <branch> in the above command.)
  
 
----
 
----
  
 
== Building a Source Package ==
 
== Building a Source Package ==
The wine-builds repository does not at present include Debian source packages (see [https://bugs.winehq.org/show_bug.cgi?id=39782 bug 39782]); however, you can create one yourself.  
+
Beginning with 4.0-rc2, the WineHQ repository includes the .dsc, .diff.gz, and .orig.tar.gz files generated by the OBS. These source packages can be found in the /main/source subdirectory of your version's repository (e.g., buster).
 
 
Download or clone the [https://github.com/wine-compholio/wine-packaging packaging git repo] and execute the following line:
 
 
 
./generate.py --skip-name --out wine-VERSION_source_dir DISTRO
 
 
 
DISTRO can be one of the following values:
 
 
 
debian-wheezy-development
 
debian-wheezy-staging
 
debian-jessie-development
 
debian-jessie-staging
 
debian-stretch-development
 
debian-stretch-staging
 
debian-sid-development
 
debian-sid-staging
 
 
 
Use `debuild` inside of the wine directory to build the package.
 
  
 
== Building WoW64 ==
 
== Building WoW64 ==
Line 71: Line 78:
 
== See Also ==
 
== See Also ==
 
* Official WineHQ [https://dl.winehq.org/wine-builds/debian/dists/ download site] for Debian.  
 
* Official WineHQ [https://dl.winehq.org/wine-builds/debian/dists/ download site] for Debian.  
 +
* [https://build.opensuse.org/project/show/Emulators:Wine:Debian WineHQ Debian/Ubuntu package build scripts and logs]
 
* The [https://wiki.debian.org/Wine Debian Wiki's page for Wine.]
 
* The [https://wiki.debian.org/Wine Debian Wiki's page for Wine.]
 
* [[Building Wine]]
 
* [[Building Wine]]

Latest revision as of 16:30, 11 September 2021

Translations of this page: Flag of the People's Republic of China.svg 简体中文 Flag of the Netherlands.svg Nederlands

Installing WineHQ packages

Dialog-warning.svg The WineHQ repository key was changed on 2018-12-19. If you downloaded and added the key before that time, you will need to download and add the new key and run sudo apt update to accept the repository changes.

Dialog-warning.svgThe WineHQ packages for Debian 10 and later require libfaudio0 as a dependency. Since the distro does not provide it for Debian 10, users of that version can download libfaudio0 packages from the OBS. See https://forum.winehq.org/viewtopic.php?f=8&t=32192 for details.

Tango-style info icon.svg Raspbian users: the WineHQ packages are for x86 architecture only; they cannot be installed on an ARM system.

Enable 32 bit packages (if you haven't already):

sudo dpkg --add-architecture i386

Download and install the repository key:

wget -nc https://dl.winehq.org/wine-builds/winehq.key
sudo apt-key add winehq.key

Add the repository to /etc/apt/sources.list or create a *.list under /etc/apt/sources.list.d/ with the following content:

For this version: Add this content to /etc/apt/sources.list:
Debian 10 (Buster) deb https://dl.winehq.org/wine-builds/debian/ buster main
Debian 11 (Bullseye) deb https://dl.winehq.org/wine-builds/debian/ bullseye main
Debian Testing (Bookworm) deb https://dl.winehq.org/wine-builds/debian/ bookworm main

Update packages:

sudo apt update

Then install one of the following packages:

Stable branch
sudo apt install --install-recommends winehq-stable
Development branch
sudo apt install --install-recommends winehq-devel
Staging branch
sudo apt install --install-recommends winehq-staging

If apt complains about missing dependencies, install them, then repeat the last two steps (update and install).


Some notes on the WineHQ packages:

  • Files are installed to /opt/wine-devel or /opt/wine-staging.
  • Menu items are not created for Wine's builtin programs (winecfg, etc.), and if you are upgrading from a distro package that had added them, they will be removed. You can recreate them yourself using your menu editor.
  • WineHQ does not at present package wine-gecko or wine-mono. When creating a new wine prefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here. If the download doesn't work for you, please follow the instructions on the Gecko and Mono wiki pages to install them manually.
  • Beginning with Wine 5.7, the WineHQ Debian packages have an optional debconf setting to enable CAP_NET_RAW to allow applications that need to send and receive raw IP packets to do so. This is disabled by default because it carries a potential security risk, and the vast majority of applications do not need that capability. Users of applications that do need it can enable CAP_NET_RAW after installing Wine by running
dpkg-reconfigure wine-<branch>-amd64 wine-<branch> wine-<branch>-i386

and answering yes to the three questions. (Substitute devel, staging, or stable for <branch> in the above command.)


Building a Source Package

Beginning with 4.0-rc2, the WineHQ repository includes the .dsc, .diff.gz, and .orig.tar.gz files generated by the OBS. These source packages can be found in the /main/source subdirectory of your version's repository (e.g., buster).

Building WoW64

Debian's implementation of Multiarch is still incomplete, so for now you can't simply install 32-bit and 64-bit libraries alongside each other. If you're on a 64-bit system, you'll have to create an isolated environment for installing and building with 32-bit dependencies. See Building Wine for instructions on how to build in a chroot or container.

See Also