Wine staging 4.11 release

[Alistair Leslie-Hughes]

Binary packages for various distributions will be available from:
https://www.winehq.org/download

Summary since last release
* Rebased to current wine 4.11 (818 patches are applied to wine vanilla)

NOTE:
FAudio will not be supported until distro's have FAudio library as part 
of their
standard repositories.

Upstreamed (Either directly from staging or fixed with a similar patch).
* ddraw: Set ddsOldCaps correctly in ddraw7_GetCaps.
* winex11: Make GetMonitorInfo() give a different device name 
(.\DISPLAY<n>) to each monitor.
* user32: Implement EnumDisplayDevicesW() based on EnumDisplayMonitors() 
and GetMonitorInfoW().
* user32: Return a more reasonable display DeviceID.
* ntdll/directory: Add support for EXT4 case folding per directory.
* dxgi: Improve stubs for MakeWindowAssociation and GetWindowAssociation.
* wininet: Silence wininet no support on this platform message.

Added:
* [37058] mshtml: Improve IOleInPlaceActiveObject TranslateAccelerator.

Updated:
* kernel32-PE_Loader_Fixes

Where can you help
* Run Steam/Battle.net/UPlay.
* Try you favorite game.
* Test your favorite applications.
* Improve staging patches and get them accepted upstream.

As always, if you find a bug, please report it via
https://bugs.winehq.org

Best Regards
  Alistair.

[Tim Schumacher]

On 22.06.19 03:44, Alistair Leslie-Hughes wrote:
> NOTE:
> FAudio will not be supported until distro's have FAudio library as part
> of their
> standard repositories.

Both Debian [1] and Ubuntu [2] adopted packages for FAudio into
their repositories for the next release (obviously, the next Debian
stable release to include those packages won't release in quite
a while). Arch and Manjaro, being rolling release distros, support
FAudio already, and Fedora supports FAudio since version 29 [3].

Is there any actual milestone set, that implies that FAudio
has been adopted wide enough to rely on it?

Also, if I might ask, how comes that the main Wine project
doesn't share the same concerns about FAudio that the Wine
staging project has?

[1] https://packages.debian.org/sid/libfaudio0
[2] https://packages.ubuntu.com/eoan/libs/libfaudio0
[3] https://apps.fedoraproject.org/packages/libFAudio

Tim

[Tim Schumacher]

On 22.06.19 03:44, Alistair Leslie-Hughes wrote:
> NOTE:
> FAudio will not be supported until distro's have FAudio library as part
> of their
> standard repositories.

Both Debian [1] and Ubuntu [2] adopted packages for FAudio into
their repositories for the next release (obviously, the next Debian
stable release to include those packages won't be released in quite
a while). Arch and Manjaro, being rolling release distros, support
FAudio already, and Fedora supports FAudio since version 29 [3].

Is there any actual milestone set, that implies that FAudio
has been adopted wide enough to rely on it?

Also, if I might ask, how comes that the main Wine project
doesn't share the same concerns about FAudio that the Wine
staging project has?

[1] https://packages.debian.org/sid/libfaudio0
[2] https://packages.ubuntu.com/eoan/libs/libfaudio0
[3] https://apps.fedoraproject.org/packages/libFAudio

Tim

[Jens Reyer]

On 22.06.19 14:00, Tim Schumacher wrote:
> On 22.06.19 03:44, Alistair Leslie-Hughes wrote:
> > NOTE:
> > FAudio will not be supported until distro's have FAudio library as part
> > of their
> > standard repositories.
>
> Both Debian [1] and Ubuntu [2] adopted packages for FAudio into
> their repositories for the next release (obviously, the next Debian
> stable release to include those packages won't be released in quite
> a while).

Debian 10 (buster) will probably be released in 2 weeks (on 2019-07-06).

https://lists.debian.org/debian-devel-announce/2019/06/msg00003.html

[Tim Schumacher]

On 22.06.19 15:18, Jens Reyer wrote:
> On 22.06.19 14:00, Tim Schumacher wrote:
> > On 22.06.19 03:44, Alistair Leslie-Hughes wrote:
> > > NOTE:
> > > FAudio will not be supported until distro's have FAudio library as part
> > > of their
> > > standard repositories.
> >
> > Both Debian [1] and Ubuntu [2] adopted packages for FAudio into
> > their repositories for the next release (obviously, the next Debian
> > stable release to include those packages won't be released in quite
> > a while).
>
> Debian 10 (buster) will probably be released in 2 weeks (on 2019-07-06).
>
> https://lists.debian.org/debian-devel-announce/2019/06/msg00003.html

The FAudio package only appears in the unstable repositories though,
not in the testing repository, so it unfortunately didn't make it in
time for the soft freeze for Debian 10, which happened in February.

[Alistair Leslie-Hughes]

Hi,

On 22/6/19 11:18 pm, Jens Reyer wrote:
> On 22.06.19 14:00, Tim Schumacher wrote:
> > On 22.06.19 03:44, Alistair Leslie-Hughes wrote:
> > > NOTE:
> > > FAudio will not be supported until distro's have FAudio library as part
> > > of their
> > > standard repositories.
> >
> > Both Debian [1] and Ubuntu [2] adopted packages for FAudio into
> > their repositories for the next release (obviously, the next Debian
> > stable release to include those packages won't be released in quite
> > a while).
>
> Debian 10 (buster) will probably be released in 2 weeks (on 2019-07-06).

My plan is that once Debian is release and the FAudio appears in testing,

I'll start including FAudio by default.

Regards

Alistair.

[Sveinar Søpler]

----- On Jun 22, 2019, at 2:00 PM, Tim Schumacher [e-mail] wrote:
> Both Debian [1] and Ubuntu [2] adopted packages for FAudio into
> their repositories for the next release (obviously, the next Debian
> stable release to include those packages won't be released in quite
> a while). Arch and Manjaro, being rolling release distros, support
> FAudio already, and Fedora supports FAudio since version 29 [3].
>
> Is there any actual milestone set, that implies that FAudio
> has been adopted wide enough to rely on it?
>
> Also, if I might ask, how comes that the main Wine project
> doesn't share the same concerns about FAudio that the Wine
> staging project has?

I can only speculate, but i guess since staging has the option of
"patching away" the library, this is the easiest solution to avoid
any troubles with compatibility perhaps?
Wine-devel does not have this switch, since it is a required library,
and without it, there will be absolutely no XAudio2 support (bad for 
a lot of games). Its a different story with vkd3d i think, cos using
wine without d3d12 support is not "unusable"... Using wine without 
XAudio2 support would probably break too many games. This could have
been solved differently with OpenAL as a fallback incase the library
is not found, but there might be technical issues making this somewhat
hard to implement.

The problem is ofc that it is a library that i guess is not too used
for other things, so things move way too slow when it comes to implementing
said library. Same thing with vkd3d. SOME new distro's will see this,
but debian/ubuntu releases are in no way "experimental" in nature so
unless there is "huge demand", it is probably not prioritized.

Sometime i guess someone decided that providing distro system packages
directly from the WineHQ dl servers could open a huge can'o'worms, and
won't allow it. Ubuntu luckily has "Launchpad" that ppl can provide 
said packages without having to build them theirselves, but slightly
more hassle to depend on that ofc :)

Sveinar
> [1] https://packages.debian.org/sid/libfaudio0
> [2] https://packages.ubuntu.com/eoan/libs/libfaudio0
> [3] https://apps.fedoraproject.org/packages/libFAudio
>
> Tim

OpenBSD/forks

[zap]

I hope this is the right place to ask this,

but I wondered, would you guys be willing to make a version of 
wine-staging, for OpenBSD forks?  Doesn't have to be openbsd itself mind 
you, but forks of it moreover... there aren't a lot of them now, but it 
would be nice to have the most secure os and being able to run 
wine-staging in it.

I saw that you guys don't have any intention of supporting openbsd in 
the future, does this apply to forks of openbsd, and if so, would you be 
willing to reconsider?

But also, I am curious if you can tell me why if you aren't able 
to/don't want to.

This is just a question I ask, my linux distro plans to make a libre 
fork OpenBSD , and I rather like Wine. I would only need wine-staging, 
and only for it to be buildable by source.  Like it does with linux... 
although if you were to want to make the other two versions obviously, 
feel free.

ps, it might be a year before this type of BSD comes out though.  I just 
wanted to ask if you think this is possible in the future.

If I remember correctly, it will be called HyperbolaBSD. it will be made 
by the same people who made Hyperbola GNU/Linux-Libre. I wondered if you 
would be able to support this when its out.

I know this is a hypothetical but can you give me any thoughts as to the 
possibility one way or another/why?