Assigning to akien who did the 4.0 & 4.0.1 commits; CC'ing tv who did the 5.0 commits.

CC: (none) => thierry.vignaud
Assignee: bugsquad => rverschelde

Pushed wine-4.0.3-1.mga7 to Mageia 7 core/updates_testing.

Note: Build still ongoing on the buildsystem, feel free to reassign to me in case it fails.

Advisory:
=========

Updated wine packages provide latest stable release

  This update provides Wine 4.0.3, the current stable release in the 4.0.x branch.

  Please see the referenced release announcements for changes since Mageia 7's
  previous 4.0.1 version.

References:
 - https://www.winehq.org/announce/4.0.2
 - https://www.winehq.org/announce/4.0.3

RPMs in core/updates_testing:
=============================

x86_64:
wine64-4.0.3-1.mga7
wine64-devel-4.0.3-1.mga7

i586:
wine-4.0.3-1.mga7
wine-devel-4.0.3-1.mga7
wine32-4.0.3-1.mga7

(the i586 wine32 is meant for use on x86_64)

SRPM in core/updates_testing:
=============================

wine-4.0.3-1.mga7

Assignee: rverschelde => qa-bugs
QA Contact: (none) => rverschelde

Quick test for now, x86_64, Plasma, Nvidia
Had 4.0.1 installed recently, had only just tested minesweeper, had no other windows prog.
Uninstalled wine 4.0.1 and company, reinstalled installed q4wine which pulled in wine64-4.0.3-1.mga7, wine32 (and wine-mono, wine-gecko, wine64-gecko).
Launched q4wine again and played minesweeper: OK

MGA7-64 Plasma on Lenovo B50
No installation issues.
Played winemine, opened winefile, installed and opened q4wine (set it to use wine64), all looks OK.
That's as far as I go.

CC: (none) => herman.viaene

I get a popup from wine saying it can not find wine-mono.

But i have installed wine-mono 4.7.5-1.mga7.

Aha! :
Bug 16273 - wine-mono and wine-gecko must be rebuilt when wine is

Assuming that still holds true, I issued
Bug 26106 - wine-mono must be rebuilt because we have a new wine version


For the future: Is it possible to place a note visible to the packagers of wine and wine-mono about this?

Depends on: (none) => 26106

(In reply to Morgan Leijström from comment #5)
> I get a popup from wine saying it can not find wine-mono.

I can't reproduce it, what applications triggered it?

AFAIK wine-mono needs to be *updated* to include the version required by wine, but I'm not sure why a simple rebuild would be necessary. (That's what bug 16273 claims, but I don't see a clear technical justification for needing this rebuild.)

To make wine-mono work, do we need to do something else than install wine-mono?
I am a newbie at wine, it have never worked well for programs i wanted to run...

After comment #3, I installed lutris from testing
  Bug 25584 - Update candidate: lutris 0.5.4
and let it i search for Fusion 360, and clicked to install;
-> After a few seconds that popup about wine-mono missing showed up.

(In reply to Morgan Leijström from comment #7)
> 
> After comment #3, I installed lutris from testing
>   Bug 25584 - Update candidate: lutris 0.5.4
> and let it i search for Fusion 360, and clicked to install;
> -> After a few seconds that popup about wine-mono missing showed up.

I think that's a false positive then.

Lutris typically ships its own versions of wine matching specific requirements for a given application. I just tried installing Fusion 360 and it downloaded its own wine version:

2020-01-23 09:38:26,988: Getting runner information for wine (version: lutris-5.0-x86_64)

So with the default config for this application on Lutris you're not testing this update candidate. You would by changing the config to use "System (4.0.3)" as Wine version.

I confirmed that when running wine-4.0.3-1.mga7 for the first time with wine-mono-4.7.5-1.mga7 (which is installed as recommended package with wine), the mono setup seems functional:

$ rm -rf ~/.wine
$ wine some_program.exe
$ ls ~/.wine/drive_c/windows/mono/mono-2.0/
bin/  etc/  lib/  support/

I don't have any .NET application handy, but I can confirm that the Mono .exe's in the Wine prefix seem functional, e.g. `wine /home/akien/.wine/drive_c/windows/mono/mono-2.0/lib/mono/xbuild/14.0/bin/xbuild.exe` runs OK and throws a message about being deprecated and not called with proper arguments (it's a deprecated build tool for C# solutions).

For me it was lutris internal wine that apparently is not compatible with our wine mono - which is irrelevant for our wine.

So I think we can ship this wine 4.0.3 update.

All right, I'm going to OK this, and validate. Advisory in Comment 2.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update
Whiteboard: (none) => MGA7-64-OK

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0047.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED