Freeciv

Marko Lindqvist wrote:

That code is so badly deprecated, that I'm worried that upstream may not fix it any more.

OTOH, glib development snapshot 2.67.1 news in https://ftp.acc.umu.se/pub/GNOME/sources/glib/2.67/glib-2.67.1.news has an item that might affect that error:
"Remove `volatile` from various public APIs, including `G_DEFINE_*`. You should
adjust your code to not use `volatile` for atomic variables, `GOnce`
variables, or mostly anything else (see
http://isvolatileusefulwiththreads.in/c/). (#600)"

From the original gna ticket about getting rid of gtkpixcomm ( https://web.archive.org/web/20170307062859/http://gna.org/patch/?6938 ), comments about why this was not done to S2_6 gtk3-client back then (here 'trunk' -> 3.0, 'gtk3x-client' -> gtk3.22-client):

I've been thinking about the S2_6 case.

- Introducing this patch series there is almost guaranteed to open up some corner cases. That's not nice in a branch that should be stabilizing already
- I'm worried that not introducing this series might cause us some trouble during the lifetime of S2_6. Yet, I can't say what exactly could break
- In trunk I'm about to bump minimum gtk3 version to 3.10, so that all the converting back and forth between formats can be avoided (implementations similar to gtk3x-client could be used). However, since S2_6 has msys1 as windows build environment, and the currently known good gtk3 package for it is 3.8, we can't bump requirement in S2_6 -> we would be stuck with the poor implementation.

Mainly because of the last point I'm removing S2_6 target from this.