forum.freeciv.org

New freeciv master msys2 build from sources of 28-Feb-20 (3.0.92-dev-200228), commit '55be574cfd', available at http://files.freeciv.org/packages/windo ... snapshots/

- Built against msys2 environment 200224

The error isn't with nations ruleset only, nor is it occurring with nations ruleset first. It finds no rulesets at all. Since this is in launching the server, it's the classic (default in 2.6) ruleset it can't find. What command exactly you use to launch the server?

No idea what is going wrong, surely I have t.l1.mangrove_cell_u000 (mangrove.spec is included in tileset files section). In most cases such problems have been caused by forgetting to add comma to the end of the line listing previously last filename in tilespec 'files', so the new filenames are not ...

In preparation to 2.6.2 release in two weeks, a new msys2 based test build has been made

New experimental msys2 build from S2_6 sources of 29-Jan-20 (2.6.1+-200129), commit 'dc13ebbd93', available: http://files.freeciv.org/packages/windo ... snapshots/

A new msys1 environment has been taken to use again, and 2.6.2 release is approaching. Time for a new test build. New msys1 snapshot build from S2_6 28-Jan-20 sources (2.6.1+-200128), commit 'd472e6ad60', available. It's available from http://files.freeciv.org/packages/windows/testing/cazfi/installe...

I see patch attachments on the second one and don't see that code in the 2.6.1 in client/audio.c The first line that the patch changes is replacing old 'bool excluded = FALSE;' line with 'int excluded = -1;'. 2.6.1 most definitely has the new 'int excluded = -1;' line (line 419, later changes have ...

If you don't use git, the command to use is 'patch -u -p1 -d freeciv < patch_file.patch', where 'freeciv' is the source directory and 'patch_file.patch' is the patch file.

Neither of those issues seem to be resolved yet, there's no patches in those tickets (except a partial fix that is part of 2.6.1 already)

Currently planned date for 3.0 network protocol freeze is 8th of February 2020 ( http://www.hostedredmine.com/issues/656467 ) Builds made from S3_0 after that will be compatible with each other, including future 3.0.x releases. As we want to concentrate on 2.6.2 release related work at the moment, ...

chippo wrote:

sveinung wrote:git checkout S3_0

Tx. The primer actually led me to:
git checkout remotes/origin/S3_0

That (checking out remote branch directly) leads you to 'detached HEAD' -state, I think. So 'git pull' won't work like it should. Check out local branch like sveinung said.