[FFe] Transition from src:wine1.6 to src:wine from Debian

Bug #1558480 reported by Graham Inggs
88
This bug affects 13 people
Affects Status Importance Assigned to Milestone
wine (Ubuntu)
Fix Released
High
Unassigned
Nominated for Xenial by Alberto Salvia Novella
wine1.6 (Ubuntu)
Fix Released
High
Unassigned
Nominated for Xenial by Alberto Salvia Novella

Bug Description

Please consider the uploads of wine 1.8.4-1ubuntu1 and wine1.6 1:1.8.4ubuntu1 for a FeatureFreeze Exception.
The current wine packages in Ubuntu are nearly two years old and several upstream releases behind.

Debdiffs of the proposed packages are in comments #54 and #55.
Build logs are available from the PPA mentioned in comment #42, along with instructions for testing.
Install logs are in comments #52 and #53.

-----------------------------------------------------------------------------

The following was sent to ubuntu-devel on 2016-09-15:
https://lists.ubuntu.com/archives/ubuntu-devel/2016-September/039498.html

Wine has been maintained separately from Debian in Ubuntu since
forever, and almost single-handedly by Scott Richie (thanks!).

Sadly, the Wine packages in Ubuntu have recently fallen behind, and
nobody stepped up to fill Scott's shoes. Earlier this year, I filed a
bug [1] which ended up being used to discuss the situation and various
possible solutions.

During DebConf16, I met Jens Reyer of Debian's Wine Team and we came
up with a plan to transition to the Wine packages from Debian,
providing a smooth upgrade path and avoiding the epoch bump. After
18.04 we would be able to drop the delta between the Debian and Ubuntu
packages.

We plan to upload to Yakkety the wine source package from Debian with
additional breaks and replaces and a few other minor packaging
changes. We would also upload a replacement for the wine1.6 source
package consisting of transitional packages that conflict with the old
Ubuntu packages and depend on the new packages from Debian.

The packages are currently available for testing from Jens' PPA [2].

Unfortunately, we will lose some of the desktop integration features
that Scott worked on, as these do not fit in with the Debian Wine
Team's current plans and some are seen as security risks. However, we
will benefit from the up-to-date packages and the reduced maintenance
overhead by adopting the Debian packages.

[1] https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1558480
[2] https://launchpad.net/~jre-phoenix/+archive/ubuntu/transition+wine1.6+wine/

-----------------------------------------------------------------------------

Wine 1.6.2 was released in October 2014. The last upload from a Wine Team [1] member was wine 1.6 1:1.6.2-0ubuntu6 on 2014-10-06. There have been subsequent uploads by other Ubuntu Developers fixing bugs and transitioning libraries.

The next stable releases from upstream were 1.8 in December 2015 and 1.8.1 in February 2016.

The Wine Team uploaded wine1.8 1:1.8.0-0ubuntu1 to their PPA [2] on 2015-12-24, but I haven't seen any activity since then.

In Debian, both wine [3] (currently at 1.8.1-2) and wine-development [4] (currently at 1.9.5-3) are maintained.
The wine1.6, wine1.7 and wine1.8 packages build a 'wine' binary package which conflicts with the Debian wine package and so wine is currently on the sync blacklist [5]. Wine-development is currently in Ubuntu [6], syncs automatically, and is on 1.9.1-1 due to sync freeze.

I propose that wine1.6 be removed from the archive now, before the LTS release.
We can then look at migrating to the Debian packages.

[1] https://launchpad.net/~ubuntu-wine
[2] https://launchpad.net/~ubuntu-wine/+archive/ubuntu/ppa
[3] https://tracker.debian.org/pkg/wine
[4] https://tracker.debian.org/pkg/wine-development
[5] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt
[6] https://launchpad.net/ubuntu/+source/wine-development

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in wine1.6 (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Please don't just remove the wine1.6 package without having a replacement package that handles upgrades properly. wine1.6 works, and is suitable for the LTS release.

Simply syncing the Debian package will result in failed upgrades.

There are two ways forward:

1- Look at the state of the wine1.8 package in the team PPA, and upload that to Xenial

or

2- Modify the debian wine package to handle upgrades from earlier Ubuntu releases properly.

Revision history for this message
AsciiWolf (asciiwolf) wrote :

Any news regarding this issue?

Revision history for this message
Scott Ritchie (scottritchie) wrote :

Everyone's waiting for me to do it and I've been lazy.

Mathew Hodson (mhodson)
no longer affects: wine (Ubuntu)
Changed in wine1.6 (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Mathew Hodson (mhodson) wrote :

Bug #1543616 proposes syncing with wine 1.8.1-2 from Debian unstable.

Bug #1556344 proposes adding a wine1.8 package.

tags: added: xenial yakkety
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in wine (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote : Re: Make Wine packages synced from Debian

I would simply sync the packages from Debian as they are structured there, and modify them there too if there is any incompatibility with Ubuntu.

summary: - remove wine1.6 package
+ Make Wine packages a sync from Debian
summary: - Make Wine packages a sync from Debian
+ Make Wine packages synced from Debian
Changed in wine1.6 (Ubuntu):
importance: Wishlist → High
Changed in wine (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
Changed in wine1.6 (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

In reality we only need the latest stable Wine version in Ubuntu, as nearly all applications supported in previous releases are well supported in later ones.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Also this is a special case where having a stable release upgrade for Xenial will serve better software stability than staying with the old Wine package.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

We just need to make sure there are no important integration problems with the various desktop environments.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

@ Mathew Hodson

I am setting this report to "high" because this is not only bringing more features, but also allowing the package to be upgraded properly in the various Ubuntu releases.

Revision history for this message
Matthias Klose (doko) wrote :

no, just syncing is wrong. you have to care about the upgrade too.

Revision history for this message
Graham Inggs (ginggs) wrote :
Revision history for this message
jre (jre-phoenix) wrote :

I'm jre from Debian's pkg-wine.

It would be great if Ubuntu based its wine packages on Debian.
If you've got any questions or need help, please just ask. I'd be happy to work on this closely together.

Revision history for this message
jre (jre-phoenix) wrote :

I don't really know the Ubuntu packages, so what I offer is mainly to help explaining what Debian does in its wine packages. Whatever ...

1.)
I assume the wineprefixes, notably the default prefix in $HOME/.wine, would just continue to work. Since the WoW64 changes I made in January there shouldn't be any Debian specifics left to take care of, and I assume none to be in Ubuntu.

2.)
Gecko/Mono is broken in the current Debian packages (wine and wine-development), but I committed a fix for that (still disabling the automatic download on purpose, but allowing for automatic installation of already downloaded gecko/mono installers). Ubuntu just has to drop disable/addons-download.patch if it also wants to restore the download of installers, or preferrably offer these packages in the required version (Debian is generally doing so, but is currently behind on that).

3.)
The main difference that I assume for Ubuntu is the Desktop integration. All Debian does is to ship "wine-binfmt" with /usr/share/binfmts/wine. But as of now there is no activation of this (see https://bugs.debian.org/819255, not sure if the maintainer wants to change that).
"wine-development" doesn't work yet with "wine-binfmt" (although it suggests it). This requires me finally implementing the Debian alternatives system (eta 1-2 months).
More desktop integration of wine-development has already been requested in https://bugs.launchpad.net/ubuntu/+source/wine-development/+bug/1576326. I'm unlikely to work on that.

So the main issue (1) is already dealt with. All you need should be to transition from one package set to the new one (provides, breaks, replaces, ...).

However I imagine (2) and (3) are blockers for Ubuntu.
Maybe you want to replace Debian with Ubuntu in patches/version-string.patch.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

@jre-phoenix
what about changing that patch version-string to some code in rules file?
ifneq ($(shell dpkg-vendor --derives-from ubuntu && echo true),true)
     (debian)
else
     (ubuntu and derivatives)
endif

this would allow us to sync the package, instead of having such delta (that BTW I would consider to not have, just call it Debian also in Ubuntu should be fine)

Revision history for this message
jre (jre-phoenix) wrote :

@LocutusOfBorg: Thanks! After writing my comment I wondered about automating this, but didn't know what to call.

version-string.patch is mainly intended to make upstream's life easier if bugreports are filed directly with them. It gives you this:

$ wine --version
wine-1.8.2 (Debian)

What is Ubuntu usually doing for such things? I'd now suggest to replace 'Debian' with the vendor name (dpkg-vendor --query Vendor).

Revision history for this message
jre (jre-phoenix) wrote :

@LocutusOfBorg
Nevermind, I'll change it do display vendor and the Debian version (dpkg-parsechangelog).

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I don't think dpkg-parsechangelog is actually making differences, because syncd packages have the same changelog as the debian packaging.

Revision history for this message
jre (jre-phoenix) wrote :

I meant I'll add to d/rules:
export VENDOR=$(shell dpkg-vendor --query Vendor && dpkg-parsechangelog -S Version)

and replace in version-string.patch (which applies to a Makefile) "Debian" with "$(VENDOR)".

Then "wine --version" should give something like these examples:
wine-1.8.2 (Debian 1.8.2-1)
wine-1.8.2 (Ubuntu 1.8.2-1)
wine-1.8.2 (Ubuntu 1.8.2-1ubuntu2)

I'd assume this is absolutely fine for Ubuntu, too. Please correct me if I'm wrong, I only use Debian, but want to have it right for Ubuntu, Debian and upstream.
This doesn't require to change anything, but imo gives the best information for e.g. bugreports filed at winehq.org (I don't want to encourage anyone to do this initially, but I assume that unfortunately some Debian and Ubuntu users just do this).

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I'm not speaking with any authority, but I *really* like the approach, and I really like packages being in sync between Debian and Ubuntu :)

thanks!

Revision history for this message
shankao (shankao) wrote :

I suppose that the desktop integration is on the patches in ubuntu's "wine1.6". Do they apply into debian's "wine"?

Revision history for this message
AsciiWolf (asciiwolf) wrote :

Any news?

Revision history for this message
carlix (carlixlinux) wrote :

Ubuntu 16.10 and Wine 2.0 will be released this year but Ubuntu will still be using wine 1.6 FOREVER

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Been working on this a bit, the Debian package is quite close to just being able to be synced, I had to change:
 * Add breaks/replaces to fonts-wineVERSION specifying wine1.6
 * Add breaks/replaces to libwineVERSION specifying wine1.6,wine1.6-amd64,wine1.6-i386
 * Add breaks/replaces to wine64VERSION specifying wine1.6-amd64
 * Add breaks/replaces to wine32VERSION specifying wine1.6-i386
 * Bump version to 1:1.8.3... so upgrades work (added the 1: to the Debian version)
 * Make it include the .orig file (debuild -S -sa) - PPA Issue?
 * Comment out override_dh_shlibdeps in rules which fails with:
    /usr/bin/ld: cannot find libGL.so.1
 (*I believe this will be fixed in yakkety as we pull the latest debian build stuff)

Upgrades require that you do a apt full-upgrade for package removal. wine-mono,gecko are not removed by the new packages, but an autoremove does remove them. I haven't looked into wine-binfmt, but I think there is a good argument to just follow what Debian does there...

You can try and break it here (Yakkety only): https://launchpad.net/~bryanquigley/+archive/ubuntu/wine-sync-testing.

*Wine-development packages is broken on the same thing for yakkety.

Revision history for this message
dino99 (9d9) wrote :

@Bryan

installed your ppa and then installed wine64 on a yakkety 64 system:
- the installation is fine
- the wineconfig file is missing; but the autoconfig script is ran when terminal.exe is hitted
- but then wine fails with:

oem@u64:~/.wine/drive_c/Program Files86/FxPro - MetaTrader 4$ wine terminal.exe
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"

sudo apt-get install wine32
...
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 wine32:i386 : Depends: libwine:i386 (= 1:1.8.3-2ubuntu3) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

****** these packages are not provided **********

Revision history for this message
Scott Ritchie (scottritchie) wrote :

As a reminder, Wine absolutely requires the 32 bit subsystem even on 64 bit systems running 64 bit Windows apps, so if that dependency isn't absolute then something is broken with the packaging ;)

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

@dino99, thanks for testing. that is odd, it seems that wine -> wine32 or wine64, and then wine64 only recommends wine32
Can you pastebin or attach the output of dpkg -l and apt-cache showpkg libwine:i386 ? Thanks!

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

I also noticed that installing:
fonts-horai-umefont fonts-unfonts-core libfreetype6:i386 libpng16-16:i386
really helps make more apps work. Will investigate further tomorrow.

Revision history for this message
jre (jre-phoenix) wrote :
Download full text (3.2 KiB)

Great, bryanquigley! You might get in contact with ginggs who's also working on this.

1.) Breaks/Replaces:
Test all packages (e.g. wineNN-tools, libwine-dev, wineNN-preloader). The -tools may be installed without "wine" itself, so you shouldn't rely on breaks/replaces in wine/wineNN itself.
(At least in the long run) you should add "1:" to every versioned breaks/replaces in d/control.in.

2.) Dependencies (dh_shlibdeps):
> * Comment out override_dh_shlibdeps in rules which fails with:
> /usr/bin/ld: cannot find libGL.so.1
> (*I believe this will be fixed in yakkety as we pull the latest debian build stuff)

[This code is for generating some dependencies that are only used with dlopen. See https://bugs.debian.org/823991 (libwine: Does not declare a Depends: on libpng)]

It would be great if yakkety automatically fixed that, but I doubt it. ginggs and I have been looking into this. Best fix I found was to make the sonames (that dh_shlibdeps looks for) unversioned. See:
- bugs.debian.org/827770 (wine-development: FTBFS in Ubuntu)
- https://lists.debian.org/debian-mentors/2016/07/msg00148.html

Looking for unversioned sonames normally still should get the correct dependencies, but I guess it has the potential for a regression, so I don't want to just add this in Debian. wine-WorkaroundShlibdepsSonames.patch attached.

If that gets fixed, there's still a related ftbfs on armhf:
- https://lists.debian.org/debian-arm/2016/07/msg00090.html

If you simply workaround this by commenting the code, you indeed should manually add some dependencies. I recommend libfontconfig, libfreetype and libncurses (the dh_shlibdeps code in Debian generates a libwine *depends* on them on each architecture, otherwise you'd usually have them only installed on your host arch). The same code also generates a libwine *recommends* for a lot of dependencies, one of them libpng.

Once libfreetype6:i386 is installed, do you really need the two fonts- packages? Not sure if Korean and Japanese fonts should be pulled by wine. If you use these languages, doesn't something more relevant pull them in?

3.) wine32:
As bryanquigley said wine depends on wine32|wine64, and wine64 recommends wine32. So wine tries hard to get wine32, but doesn't enforce it. However (as long as you are using wine in the terminal) it will show you the mentioned message, or (only on *amd64* with i386 not enabled as foreign arch) it will also output instructions how to add the foreign arch. See /usr/bin/wine (https://anonscm.debian.org/git/pkg-wine/wine.git/tree/debian/scripts/wine.in) for details.

In Debian we want to be able to install wine without having i386 enabled as foreign arch:

- There are valid use cases for installing only 64-bit wine.
- I assume telling the users how to enable i386 from /usr/bin/wine has more potential to help them, then to enforce it before installation (and putting the information in the package long description). Automatically adding i386 is not wanted and afaik not possible.

@scottritchie: Was it possible to install wine1.6 without i386 as foreign arch?

@dino99:
> E: Unable to correct problems, you have held broken packages.
The wine packages need to be of the exact sa...

Read more...

Revision history for this message
dino99 (9d9) wrote :

@Bryan

from #28 request:

oem@u64:~$ sudo dpkg -l libwine:i386
dpkg-query: no packages found matching libwine:i386
oem@u64:~$ sudo apt-cache showpkg libwine:i386
Package: libwine:i386
Versions:
1:1.8.3-2ubuntu3 (/var/lib/apt/lists/ppa.launchpad.net_bryanquigley_wine-sync-testing_ubuntu_dists_yakkety_main_binary-i386_Packages)
 Description Language:
                 File: /var/lib/apt/lists/ppa.launchpad.net_bryanquigley_wine-sync-testing_ubuntu_dists_yakkety_main_binary-amd64_Packages
                  MD5: fa6ba9c73f02c30ec6c20a5ad4c5cf58
 Description Language:
                 File: /var/lib/apt/lists/ppa.launchpad.net_bryanquigley_wine-sync-testing_ubuntu_dists_yakkety_main_binary-i386_Packages
                  MD5: fa6ba9c73f02c30ec6c20a5ad4c5cf58
 Description Language: en
                 File: /var/lib/apt/lists/ppa.launchpad.net_bryanquigley_wine-sync-testing_ubuntu_dists_yakkety_main_i18n_Translation-en
                  MD5: fa6ba9c73f02c30ec6c20a5ad4c5cf58

Reverse Depends:
  fonts-wine,libwine:i386 1.7.41-2~
  wine32:i386,libwine:i386 1:1.8.3-2ubuntu3
  libwine-dev:i386,libwine:i386 1:1.8.3-2ubuntu3
  libwine,libwine:i386 1:1.8.3-2ubuntu3
  libwine,libwine:i386 1:1.8.3-2ubuntu3
  fonts-wine,libwine:i386 1.7.41-2~
Dependencies:
1:1.8.3-2ubuntu3 - libasound2:i386 (2 1.0.16) libc6:i386 (2 2.17) libglu1-mesa:i386 (16 (null)) libglu1:i386 (0 (null)) liblcms2-2:i386 (2 2.2+git20110628) libldap-2.4-2:i386 (2 2.4.7) libmpg123-0:i386 (2 1.13.7) libopenal1:i386 (2 1.14) libpcap0.8:i386 (2 0.9.8) libpulse0:i386 (2 0.99.1) libx11-6:i386 (0 (null)) libxext6:i386 (0 (null)) libxml2:i386 (2 2.9.0) ocl-icd-libopencl1:i386 (16 (null)) libopencl1:i386 (0 (null)) ocl-icd-libopencl1:i386 (18 1.0) libopencl-1.1-1:i386 (0 (null)) zlib1g:i386 (2 1:1.1.4) wine1.6 (0 (null)) wine1.6:i386 (0 (null)) wine32 (3 1.7.51-2~) wine64 (3 1.7.51-2~) libgl1-mesa-dri:i386 (0 (null)) libasound2-plugins:i386 (0 (null)) fonts-liberation:i386 (0 (null)) fonts-wine:i386 (2 1.8.2-1~) cups-bsd:i386 (0 (null)) ttf-mscorefonts-installer:i386 (0 (null)) wine1.6 (0 (null)) wine1.6:i386 (0 (null)) libwine (35 1:1.8.3-2ubuntu3) libwine (38 1:1.8.3-2ubuntu3) wine32:i386 (3 1.7.51-2~)
Provides:
1:1.8.3-2ubuntu3 -
Reverse Provides:

Revision history for this message
dino99 (9d9) wrote :

Well, i've glanced at win64 installation from winehq wikis and else
But Yakkety seems having a real problem to upload the i386 arch:

 "sudo dpkg --add-architecture i386" seems doing nothing.

Revision history for this message
Scott Ritchie (scottritchie) wrote :

> - There are valid use cases for installing only 64-bit wine.

Could you give some examples? 64 bit windows apps generally require the 32 bit subsystem as it's always available on Windows.

Revision history for this message
jre (jre-phoenix) wrote :

> "sudo dpkg --add-architecture i386" seems doing nothing.

@9d9: i386 is enabled on your system, otherwise you'd get another message from the new wine packages.

Generally you always need to issue a "sudo apt update" afterwards (you don't mention that anywhere in your recent bugs). However your apt-cache command proves you did that and that the package is available already.

So try:
$ sudo apt install wine32=1:1.8.3-2ubuntu3 libwine:i386=1:1.8.3-2ubuntu3

If that still goes wrong please post the whole unshortened output of this command.

> Could you give some examples? 64 bit windows apps generally require the 32 bit subsystem as it's always available on Windows.

- Some developers who build and test their own app for Windows in Wine.
- Afaik most arm64 users only have the 64-bit parts installed.

But I obviously agree that normally you need wine32.

Revision history for this message
dino99 (9d9) wrote :

@jre

 sudo apt install wine32=1:1.8.3-2ubuntu3 libwine:i386=1:1.8.3-2ubuntu3
....

The following packages have unmet dependencies.
 libwine:i386 : Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
                Depends: libpulse0:i386 (>= 0.99.1) but it is not going to be installed
                Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed
                Recommends: libasound2-plugins:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

All these dependencies are 'main' or 'proposed' genuine yakkety packages (but also have mostly all the gnome3 staging packages installed)

Revision history for this message
jre (jre-phoenix) wrote :

I had hoped that in "...." there is some clue what's wrong on your system, that's why I asked for unshortened. Not sure what's "gnome3 staging packages", I don't know that. But I guess some Gnome staging PPA has the potential to conflict with a Wine PPA. Someone more into Ubuntu might help there, and figure out if there are conflicting PPAs, manually set on hold packages, broken apt preferences, or some other broken package state that blocks this.

Anyway, by now from my pov bryanquigley's wine packages look fine (or are not broken in this respect at least). :)

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

@jre
Thanks for the feedback!

1.) Breaks/Replaces:
>Test all packages (e.g. wineNN-tools, libwine-dev, wineNN-preloader). The -tools may be installed without "wine" itself, so you shouldn't rely on breaks/replaces in wine/wineNN itself.

I'm going through testing now. Yes, the breaks/replaces would just be needed until 18.04 releases. That way we can handle upgrades from 16.04 (wine1.6) -> 18.04.

>(At least in the long run) you should add "1:" to every versioned breaks/replaces in d/control.in.

I'm not sure what that means exactly. I haven't added any "versioned" breaks/replaces just using the 1.6 in the package name.

2.) Dependencies (dh_shlibdeps):
Still looking into this further, will talk to ginggs about it.

>If you simply workaround this by commenting the code, you indeed should manually add some dependencies. I recommend libfontconfig, libfreetype and libncurses (the dh_shlibdeps code in Debian generates a libwine *depends* on them on each architecture, otherwise you'd usually have them only installed on your host arch). The same code also generates a libwine *recommends* for a lot of dependencies, one of them libpng.

Right, turns out commenting out code without fully understanding it can break things. Thanks for the detailed explanation.

>Once libfreetype6:i386 is installed, do you really need the two fonts- packages? Not sure if Korean and Japanese fonts should be pulled by wine. If you use these languages, doesn't something more relevant pull them in?

Yes, I was just selecting a bunch of packages given the error I was seeing so I likely selected too many.

@dino99:
I tried installing the gnome3 testing PPA and wasn't able to reproduce.

Revision history for this message
jre (jre-phoenix) wrote :

@bryanquigley
>>(At least in the long run) you should add "1:" to every versioned breaks/replaces in d/control.in.

>I'm not sure what that means exactly. I haven't added any "versioned" breaks/replaces just using the 1.6 in the package name.

If you add the epoch ("1:") to the version in d/changelog, then you'd also have to take care of changing any versioned breaks/replaces that we add *in Debian* in the future.

But I really hope that this is not necessary and we find a way to go without the epoch ("1:").

Revision history for this message
jre (jre-phoenix) wrote :

I've now got two solutions (tested in Debian with rebuilt Ubuntu packages) for an upgrade path from src:wine1.6 (1:1.6.2-0ubuntu15) to either the Debian packages src:wine (1.8.3-3) or src:wine-development (1.9.16-1). After a transition (until including the next 18.04) the Debian packages might theoretically be synced.

- Both make src:wine1.6 ship only transitional packages (based on ginggs' previous attempt).
- Both work with "apt dist-upgrade" and uninstall the old wine metapackage.
- There are minor unrelated TODOs in the changelog.

I've pushed the proposals to my git repository at github[1] and uploaded to 2 separate PPAs. Check the launchpad sites to see which versions you need from git. NOTE: wine-development is the same for both versions, but currently only uploaded to one repo.

Unfortunately src:wine-development fails to build because of a new cups version (but ginggs told me that this is fixed in the next version) and src:wine fails, too (someone needs to investigate).

[1]: https://github.com/jre-wine/wine
git branches:
  jre.stretch/Ubuntu.src.wine
  jre/Ubuntu.src.wine.development
  jre/wine1.6-transition

For building the packages I made the following changes:
* Use unversioned sonames in debian/scripts/sonames2elf
  so that dpkg-shlibdeps can find libGL.so in Ubuntu.
* Don't build on armhf.

1.) Transition to src:wine-development

- This switches users to the *development branch* from winehq, but that might be not wanted for these packages, especially in a LTS! Up for discussion!
- The recently implemented Debian alternatives system makes sure that the commands can be used without any suffix, e.g. /usr/bin/wine.
- "apt install wine" installs Debian's wine *next to* wine-development.
  The system defaults to use src:wine's commands then.

https://launchpad.net/~jre-phoenix/+archive/ubuntu/transition+wine1.6+wine-development

2.) Transition to src:wine

- src:wine:
  - Rename binary package wine -> wine-stable
- Additionally create a native src:wine1.6-transition:
  - Package wine depends wine-stable
  - Not needed for the transition itself, but to make sure that
    "apt install wine" installs the default src:wine.

https://launchpad.net/~jre-phoenix/+archive/ubuntu/transition+wine1.6+wine

So a transition to src:wine would be cleaner, but put a higher burden on the maintainers the next 2 years (these changes wouldn't be in Debian). There are a few (not much) changes to d/control.in and d/rules necessary, and some files need to be renamed. Don't know how this works with the Ubuntu merging.

Revision history for this message
jre (jre-phoenix) wrote :

After sleeping a bit, I realized that the additional native package src:wine1.6-transition is not needed at all for the transition to src:wine. Instead I now just added the binary package "wine" to src:wine, next to the renamed binary package "wine-stable".

So the new updated state in https://launchpad.net/~jre-phoenix/+archive/ubuntu/transition+wine1.6+wine/ might be the way to go:

src:wine
version: 1.8.3-3+local41+Ubuntu.src.wine
git branch: jre.stretch/Ubuntu.src.wine
git commit: a0bbf793 Update changelog for 1.8.3-3+local41+Ubuntu.src.wine release

src:wine-development
version: 1.9.16-1ubuntu2~ppa0~jre30
git branch: jre/Ubuntu.src.wine.development
git commit: 3130976 Update changelog for 1.9.16-1ubuntu1~ppa0~jre30 release

src:wine1.6
version: 1:1.6.2ubuntu1~ppa0~jre40
git branch: jre/wine1.6-transition
git commit: 88b5d8a release 1:1.6.2ubuntu1~ppa0~jre40

Using these packages you'll get on apt "dist-upgrade":

The following packages will be REMOVED:
  wine wine1.4-dbg wine1.4-dbg:i386 wine1.6-dbg wine1.6-dbg:i386
The following NEW packages will be installed:
  fonts-wine libwine libwine:i386 libwine-dev wine-stable wine32:i386 wine64 wine64-tools
The following packages will be upgraded:
  wine1.6 wine1.6-amd64 wine1.6-dev wine1.6-i386:i386

You may "apt install wine" later at any point, you'll stay with src:wine.

TODO:
- remove the old /etc/xdg/menus/applications-merged/wine.menu
- check if old system binfmt support is removed
- adapt d/copyright, especially for the native package
- maybe care for the wine1.4 packages in src:wine1.6 (currently they just stay installed)
- maybe care for src:wine1.7 and src:wine1.8
- transition the -dbg packages (I don't know the Ubuntu way to handle them, but for -dbg packages I think just uninstalling them as I currently do is ok)

Unfortunately src:wine still FTBFS due to the cups issues (cups 2.2~rc1-4). In the meantime wine-development built successfully, also with 2.2~rc1-4.

Revision history for this message
Graham Inggs (ginggs) wrote :

Attached is a patch for wine 1.8.3 to fix the FTBFS with the new version of cups.
It is already included in the wine-development branch.

Revision history for this message
jre (jre-phoenix) wrote :

Great, Graham! That worked.

So now everybody may test the transition from src:wine1.6 to src:wine in:

https://launchpad.net/~jre-phoenix/+archive/ubuntu/transition+wine1.6+wine/

CAVEAT: I messed up the Ubuntu versioning in there (1.8.3-3+local50+Ubuntu.src.wine), so there won't be an automatic upgrade to a potential Ubuntu package until a new Debian release is out (which will happen soon (1.8.4-1)).

Other changes:
I replaced the Conflicts: wine1.6* (<< 1:1.6.2ubuntu) with Breaks.

The previously TODO is still open.

Git sources: https://github.com/jre-wine/wine

src:wine (1.8.3-3+local50+Ubuntu.src.wine)
branch: jre.stretch/Ubuntu.src.wine
commit: 072427f Update changelog for 1.8.3-3+local50+Ubuntu.src.wine release

src:wine-development (1.9.16-1ubuntu2~ppa0~jre50)
branch: jre/Ubuntu.src.wine.development
commit: e8449d0 Update changelog for 1.9.16-1ubuntu2~ppa0~jre50 release

src:wine1.6 (1:1.6.2ubuntu1~ppa0~jre40)
branch: jre/wine1.6-transition
commit: 88b5d8a release 1:1.6.2ubuntu1~ppa0~jre40

Revision history for this message
jre (jre-phoenix) wrote :

For the record: the cups patch will be in the upcoming 1.8.4, so it's only needed for a short time.

Revision history for this message
Graham Inggs (ginggs) wrote :

I've just run another test of upgrading from wine1.6 on yakkety amd64 system to the latest packages from jre's PPA. Below is what it looks like.
We plan to upload jre's wine1.6 package along with wine 1.8.4 to yakkety in about one week, so please test and report back in this bug.

$ sudo add-apt-repository ppa:jre-phoenix/transition+wine1.6+wine
$ sudo apt-get update
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  gnome-exe-thumbnailer libsamplerate0:i386 libspeexdsp1:i386 wine1.6:i386
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  fonts-wine libgsm1:i386 libodbc1:i386 libpcap0.8:i386 libwine libwine:i386 wine-stable wine32:i386 wine64
The following packages will be upgraded:
  wine1.6:i386 wine1.6-i386:i386
2 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 36.9 MB of archives.
After this operation, 183 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Revision history for this message
dino99 (9d9) wrote :

Feedback 1.8.3-3

Wants to remove gnome-disk-utility when trying to install wine64

Revision history for this message
Graham Inggs (ginggs) wrote :

@dino99: I have gnome-disk-utility installed, and it was not removed during the procedure above.

Revision history for this message
dino99 (9d9) wrote :
Download full text (3.6 KiB)

New test:

1) first purge gnome-disk-utility, then reinstall it
2) install wine64 : that time no error/warning
3) try to run a 32 bits apply (terminal.exe from Metaquotes Metatrader 4), but get again some conflicts:

oem@u64:~/.wine/drive_c/Program Files/FxPro - MetaTrader 4$ wine terminal.exe
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"
wine: Bad EXE format for C:\Program Files\FxPro - MetaTrader 4\terminal.exe.

oem@u64:~$ sudo apt-get install wine32
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 wine32:i386 : Depends: libwine:i386 (= 1.8.3-3+local61+Ubuntu.src.wine) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

oem@u64: sudo apt-get install libwine:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libwine:i386 : Depends: libglu1-mesa:i386 but it is not going to be installed or
                         libglu1:i386
                Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
                Depends: libpulse0:i386 (>= 0.99.1) but it is not going to be installed
                Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed
                Recommends: libcups2:i386 (>= 1.4.0) but it is not going to be installed
                Recommends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed
                Recommends: libgl1-mesa-glx:i386 but it is not going to be installed or
                            libgl1:i386
                Recommends: libosmesa6:i386 (>= 10.2~) but it is not going to be installed
                Recommends: libtiff5:i386 (>= 4.0.3) but it is not going to be installed
                Recommends: libxslt1.1:i386 (>= 1.1.25) but it is not going to be installed
                Recommends: libgl1-mesa-dri:i386 but it is not going to be installed
                Recommends: libasound2-plugins:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

oem@u64: sudo apt-get install wine32-preloader:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distri...

Read more...

Revision history for this message
Graham Inggs (ginggs) wrote :

@dino99: remember, what we are testing here is transitioning from a working wine1.6 installation to the Debian wine package.

Graham Inggs (ginggs)
summary: - Make Wine packages synced from Debian
+ Transition from src:wine1.6 to src:wine from Debian
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : Re: Transition from src:wine1.6 to src:wine from Debian

The attachment "Workaround for FTBFS from sonames2elf script (by using unversioned solinks)" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :

It would be nice if new src:wine packages from ppa:jre-phoenix/transition+wine1.6+wine could be backported to Ubuntu 16.04 LTS - currently wine 1.8.4-1ubuntu1~ppa1 source doesn't build on Ubuntu 16.04 LTS because of older debhelper and unicode-data packages:

Missing build dependencies: debhelper (>= 9.20160702), unicode-data (>= 9.0)

See https://launchpad.net/~baltix/+archive/ubuntu/ppa/+build/10627809

Please not force to use at least unicode-data 9.0 - Ubuntu 16.04 LTS has older unicode-data 8.0

Revision history for this message
jre (jre-phoenix) wrote :

@mantas

Unfortunately the dependency on unicode-data (>= 9.0) is necessary, because this is an incompatible change in the source. The current Wine source only builds with Unicode 9, but not with Unicode 8. The old Wine source built only with Unicode 8, but not with Unicode 9. (Just verified that again).

I'll only provide my PPA for testing until the packages are added to Ubuntu in a few days. Then I'll delete it. However I'd be happy to support anyone in creating backports in a PPA, similarily like I'm working with brianquigley and ginggs to get the packages in Ubuntu. I'll probably know what is needed because I'm doing Debian Jessie backports (Jessie is older than Ubuntu 16.04).

For jessie-backports I backported khronos-api and unicode-data - I suggest to do the same for the latter in a backporting PPA. Since it's only a build-dependency, but not a runtime-dependency, this is safe to do. Alternatively you might just drop unicode-9.patch in src:wine.

Further changes (e.g. for older debhelper) can/will be found in the git repository (check its history):
  https://anonscm.debian.org/git/pkg-wine/wine.git
  branch jessie-backports-1.8.x for src:wine
  branch jessie-backports-1.9.x for src:wine-development
For current versions this is only reverting one commit. So for everyone interested, this is more about commitment in the long run, than about doing complicated stuff.

Revision history for this message
Graham Inggs (ginggs) wrote :
Download full text (9.4 KiB)

Another test, this time in an amd64 virtualbox VM. I installed all the wine1.6 packages, enabled jre's PPA, apt-get dist-upgrade then apt-get autoremove. At each step, I ran some applications in wine.

$ sudo apt-get install wine wine1.4 wine1.4-amd64 wine1.4-dbg wine1.4-dev wine1.4-i386 wine1.6 wine1.6-amd64 wine1.6-dbg wine1.6-dev wine1.6-i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  binfmt-support cabextract fonts-horai-umefont fonts-unfonts-core
  fonts-wqy-microhei gcc-6-base:i386 gnome-exe-thumbnailer icoutils
  libasn1-8-heimdal:i386 libasound2:i386 libasound2-plugins:i386
  libasyncns0:i386 libavahi-client3:i386 libavahi-common-data:i386
  libavahi-common3:i386 libbsd0:i386 libc6:i386 libcapi20-3 libcapi20-3:i386
  libcomerr2:i386 libcups2:i386 libdb5.3:i386 libdbus-1-3:i386
  libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386
  libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexif12:i386
  libexpat1:i386 libffi6:i386 libflac8:i386 libfontconfig1:i386
  libfreetype6:i386 libgcc1:i386 libgcrypt20:i386 libgd3:i386 libgif7
  libgif7:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386 libglapi-mesa:i386
  libglu1-mesa:i386 libgmp10:i386 libgnutls30:i386 libgpg-error0:i386
  libgphoto2-6:i386 libgphoto2-port12:i386 libgpm2:i386 libgssapi-krb5-2:i386
  libgssapi3-heimdal:i386 libhcrypto4-heimdal:i386 libheimbase1-heimdal:i386
  libheimntlm0-heimdal:i386 libhogweed4:i386 libhx509-5-heimdal:i386
  libice6:i386 libicu57:i386 libidn11:i386 libieee1284-3:i386
  libjack-jackd2-0:i386 libjbig0:i386 libjpeg-turbo8:i386 libjpeg8:i386
  libjson-c3:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-26-heimdal:i386
  libkrb5-3:i386 libkrb5support0:i386 liblcms2-2:i386 libldap-2.4-2:i386
  libllvm3.8:i386 libltdl7:i386 liblzma5:i386 libmpg123-0 libmpg123-0:i386
  libmspack0 libncurses5:i386 libnettle6:i386 libodbc1 libogg0:i386
  libopenal-data libopenal1 libopenal1:i386 libosmesa6 libosmesa6:i386
  libp11-kit-gnome-keyring:i386 libp11-kit0:i386 libpciaccess0:i386
  libpcre3:i386 libpng16-16:i386 libpulse0:i386 libroken18-heimdal:i386
  libsamplerate0:i386 libsane:i386 libsasl2-2:i386 libsasl2-modules:i386
  libsasl2-modules-db:i386 libselinux1:i386 libsm6:i386 libsndfile1:i386
  libspeexdsp1:i386 libsqlite3-0:i386 libssl1.0.0:i386 libstdc++6:i386
  libsystemd0:i386 libtasn1-6:i386 libtiff5:i386 libtinfo5:i386
  libtxc-dxtn-s2tc0:i386 libudev1:i386 libusb-1.0-0:i386 libuuid1:i386
  libv4l-0:i386 libv4lconvert0:i386 libvorbis0a:i386 libvorbisenc2:i386
  libwebp6:i386 libwind0-heimdal:i386 libwrap0:i386 libx11-6:i386
  libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
  libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386
  libxcomposite1:i386 libxcursor1:i386 libxdamage1:i386 libxdmcp6:i386
  libxext6:i386 libxfixes3:i386 libxi6:i386 libxinerama1:i386 libxml2:i386
  libxpm4:i386 libxrandr2:i386 libxrender1:i386 libxshmfence1:i386
  libxslt1.1:i386 libxt6:i386 libxxf86vm1:i386 ocl-icd-libopencl1
  ocl-icd-libopencl1:i386 odbcinst odbcinst1debian2 p11-kit-modules:i386 p7zip
  ttf-mscorefonts-inst...

Read more...

Revision history for this message
Graham Inggs (ginggs) wrote :
Download full text (3.2 KiB)

Same as the previous test, but this time in a i386 virtualbox vm.

$ sudo apt-get install wine wine1.4 wine1.4-dbg wine1.4-dev wine1.4-i386 wine1.6 wine1.6-dbg wine1.6-dev wine1.6-i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  binfmt-support cabextract fonts-horai-umefont fonts-unfonts-core
  fonts-wqy-microhei gnome-exe-thumbnailer icoutils libcapi20-3 libgif7
  libmpg123-0 libmspack0 libodbc1 libopenal-data libopenal1 libosmesa6
  odbcinst odbcinst1debian2 p7zip ttf-mscorefonts-installer ttf-wqy-microhei
  unixodbc wine-gecko2.21 wine-mono0.0.8 winetricks
Suggested packages:
  libterm-readline-gnu-perl | libterm-readline-perl-perl isdnutils-doc
  libmyodbc odbc-postgresql tdsodbc unixodbc-bin p7zip-full dosbox:any winbind
  aria2 tor
Recommended packages:
  fonts-droid
The following NEW packages will be installed:
  binfmt-support cabextract fonts-horai-umefont fonts-unfonts-core
  fonts-wqy-microhei gnome-exe-thumbnailer icoutils libcapi20-3 libgif7
  libmpg123-0 libmspack0 libodbc1 libopenal-data libopenal1 libosmesa6
  odbcinst odbcinst1debian2 p7zip ttf-mscorefonts-installer ttf-wqy-microhei
  unixodbc wine wine-gecko2.21 wine-mono0.0.8 wine1.4 wine1.4-dbg wine1.4-dev
  wine1.4-i386 wine1.6 wine1.6-dbg wine1.6-dev wine1.6-i386 winetricks
0 upgraded, 33 newly installed, 0 to remove and 65 not upgraded.
Need to get 151 MB of archives.
After this operation, 403 MB of additional disk space will be used.

$ sudo add-apt-repository ppa:jre-phoenix/transition+wine1.6+wine
$ sudo apt-get update
$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  fonts-horai-umefont fonts-unfonts-core fonts-wqy-microhei
  gnome-exe-thumbnailer icoutils libcapi20-3 libgif7 odbcinst odbcinst1debian2
  ttf-wqy-microhei unixodbc wine-gecko2.21 wine-mono0.0.8 wine1.6 wine1.6-dev
  wine1.6-i386
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  wine wine1.4 wine1.4-dbg wine1.4-dev wine1.4-i386 wine1.6-dbg
The following NEW packages will be installed:
  fonts-wine libgettextpo0 libgsm1 libwine libwin$ sudo add-apt-repository ppa:jre-phoenix/transition+wine1.6+wine
$ sudo apt-get updatee-dev wine-stable wine32
  wine32-tools
The following packages will be upgraded:
  wine1.6 wine1.6-dev wine1.6-i386
3 upgraded, 8 newly installed, 6 to remove and 0 not upgraded.
Need to get 22.0 MB of archives.
After this operation, 15.6 MB disk space will be freed.
Do you want to continue? [Y/n] y

$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  fonts-horai-umefont fonts-unfonts-core fonts-wqy-microhei
  gnome-exe-thumbnailer icoutils libcapi20-3 libgif7 odbcinst odbcinst1debian2
  ttf-wqy-microhei unixodbc wine-gecko2.21 wine-mono0.0.8 wine1.6 wine1.6-dev
  wine1.6-i386
0 upgraded, 0 newly installed, 16 to remove and 0 not upgraded.
After this operat...

Read more...

Revision history for this message
Graham Inggs (ginggs) wrote :

Attached is a debdiff between wine 1.8.4-1 from Debian and the proposed wine 1.8.4-1ubuntu1.
It is not as scary as it appears. There are many changes duplicated in debian/control and debian/control.in, and several files are renamed from debian/wineVERSION.* to debian/wineDEBSUFFIX.*.

Revision history for this message
Graham Inggs (ginggs) wrote :

Attached is the proposed wine1.6_1.8.4ubuntu1.tar.xz. A debdiff against wine 1:1.6.2-0ubuntu15 would include the removal of the old wine source and be >20MB in size.

summary: - Transition from src:wine1.6 to src:wine from Debian
+ [FFe] Transition from src:wine1.6 to src:wine from Debian
Graham Inggs (ginggs)
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Indeed this is long-overdue, and as wine is mostly a leaf package the risk is manageable (still a month until release). FFE ack under the condition that upgrades from 16.04 get tested properly. Thanks for working on this!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package wine - 1.8.4-1ubuntu1

---------------
wine (1.8.4-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian unstable. (LP: #1558480)
  * Use unversioned sonames in debian/scripts/sonames2elf
    so that dpkg-shlibdeps can find libGL.so in Ubuntu (closes: #827770).
  * Add versioned breaks/replaces against the wine1.6 packages.
  * Replace package wine with wine-stable. Needed for the transition to a
    0-epoch in the version number.
    Necessary until after the transition is complete (18.04).
  * Generate the correct SERVER_PROTOCOL_VERSION.

 -- Jens Reyer <email address hidden> Tue, 20 Sep 2016 01:02:21 +0200

Changed in wine (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Qwerty Chouskie (asdfghrbljzmkd) wrote :

Any chance of getting this in 16.04, since it is supported until April 2021?

Revision history for this message
AsciiWolf (asciiwolf) wrote :

Please, also backport wine-development from Yakkety since the Xenial one is quite old and cannot run some recent apps/games (for example the World of Warcraft).

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package wine1.6 - 1:1.8.4ubuntu1

---------------
wine1.6 (1:1.8.4ubuntu1) yakkety; urgency=medium

  * Transition from Ubuntu wine1.x packages to Debian wine packages.
    (LP: #1558480)
  * Depend on binary package wine-stable instead of wine (requires change
    in src:wine). Needed for the transition to a 0-epoch in the version
    number.
    Necessary until after the transition is complete (18.04).
  * Remove old conffiles and binfmt support activation.

 -- Jens Reyer <email address hidden> Tue, 20 Sep 2016 02:23:33 +0200

Changed in wine1.6 (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Backporting wine 1.8 (to replace 1.6) to 16.04 is simply not something that would be acceptable in archive.

I would like to see wine-development to be a rolling package in an LTS eventually, but that's not the case today. You can get wine1.9 from the official wine PPA though - https://wiki.winehq.org/Ubuntu.

Revision history for this message
Graham Inggs (ginggs) wrote :

I've just upgraded my amd64 desktop from 16.04 to 16.10 beta.
It had a working wine1.6 installation.
Packages were removed and upgraded as expected.
Now on wine-stable 1.8.4-1ubuntu2.

There are still some NBS binaries to be removed:

$ apt-cache policy wine
wine:
  Installed: (none)
  Candidate: 1:1.6.2-0ubuntu15
  Version table:
     1:1.6.2-0ubuntu15 500
        500 http://za.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages

$ apt-cache policy wine1.4-dev
wine1.4-dev:
  Installed: (none)
  Candidate: 1:1.6.2-0ubuntu15
  Version table:
     1:1.6.2-0ubuntu15 500
        500 http://za.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages

They can also be seen at http://people.canonical.com/~ubuntu-archive/NBS/

Revision history for this message
Graham Inggs (ginggs) wrote :

dssi-vst has been removed from the archive
this should make wine1.4-dev a candidate for NBS removal

Revision history for this message
Graham Inggs (ginggs) wrote :

NBS binaries wine and wine1.4-dev have been removed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.