Ticket #43719

Msys2-next after 211115

Open Date: 2022-01-28 15:34 Last Update: 2022-03-15 20:42

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
4

Details

We've done msys2 environment snapshots about once every three months, and that time will be up since 211115 snapshot in a couple of weeks.

- There's a new upstream base snapshot 220118
- As we found out in #42343, Qt6 is not co-installable with Qt5 in msys2 and as we will need Qt5 for some time (to make it possible to backport new msys2 environment to S3_0), we can't have Qt6 in the official snapshot.

For that last part I try (time permitting) to check if the "not co-installable" still is true with latest msys2. It's unlikely that the thing has changed, but it would really help us.

Ticket History (3/12 Histories)

2022-01-28 15:34 Updated by: cazfi
  • New Ticket "Msys2-next after 211115" created
2022-02-20 11:45 Updated by: cazfi
Comment

I've been making build tests on a msys2 environment hacked up (not going to release that dirty environment, but going to make a fresh one for this ticket).

- Qt6 is not co-installable with Qt5, and both working Qt5-client and working Qt6-client can be built from such an environment.
- As we are scaling down win32 support, and the size of msys2 environment snapshots are causing trouble already, I've installed Qt6 for the win64 target only (no new functionality for win32). This derives from the old standard that environment for both win32 and win64 targets are identical

2022-03-09 10:38 Updated by: cazfi
Comment

After the delays in taking 220220 to use, it's gotten weeks old already. I've now made new 220308 snapshot with the idea that we go directly to that one. Of course, if it turns out in the testing that it introduces new regressions compared to 220220, we can still choose the older one.

In addition to the being newer snapshot, these changes have been made to the process of creating the snapshot package:
- Package 'nano' is not installed explicitly (it's already present)
- Instead of metapackage 'autoconf', install 'autoconf2.71'. Former installs multiple autoconf versions, when we want only the current one. We've already done similar change for installation of automake.

2022-03-09 10:57 Updated by: cazfi
Comment

Reply To cazfi

- Instead of metapackage 'autoconf', install 'autoconf2.71'. Former installs multiple autoconf versions, when we want only the current one.

This breaks things - autom4te is not present in the system.

2022-03-11 12:19 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Resolution Update from None to Accepted
Comment

Did another iteration as 220309, with 'autoconf' installed. Environment uploaded to http://files.freeciv.org/packages/windows/msys2/ . Patches to take it to use attached.

2022-03-13 05:02 Updated by: cazfi
  • Resolution Update from Accepted to None
Comment

This does not build in CI environment, where current version of setup-msys2 uses older msys2 snapshot.

2022-03-13 20:31 Updated by: cazfi
  • Resolution Update from None to Accepted
Comment

- New versions that fix build in CI

2022-03-15 20:42 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login