Follow-up Comment #9, bug #17439 (project freeciv):
Hmm. Dubious client data structures after a civil war. Could this perhaps be
tied up with our lost-city troubles in bug #17990 et al?
-- jtn
___
Reply to this item at:
Follow-up Comment #8, bug #17990 (project freeciv):
To make my hypothesis of comment #6 more explicit: I'm hopeful that this
could be cleared up by forcing through one last city update to the losing
player after a city has changed hands; a quick read through of the code at the
time suggested to
Follow-up Comment #2, bug #13701 (project freeciv):
FYI, I saw something like this while reproducing bug #17990 (see comment 6 on
that bug).
Since it seems to be about iffy data structures on the client, I wonder if it
could be related to the cause of that bug (but perhaps that's wishful
Follow-up Comment #6, bug #18005 (project freeciv):
Hmm, perhaps we should be looking at this for 2.3.0, since it's apparently
reproducible. (I can't change the target release myself right now.) -- jtn
___
Reply to this item at:
Follow-up Comment #10, bug #17439 (project freeciv):
Dubious client data structures after a civil war.
I assumed this to happen *during* civil war updates (handling of earlier
packet would require information that comes only in later packet), not
*after*, but from the information provided it
Update of bug #17710 (project freeciv):
Status: Ready For Test = Fixed
Open/Closed:Open = Closed
___
Reply to this item at:
