broken downloads = desync. needs new version to fix: 9.729

[knorke]

At the moment games can desync.
abma says it is because there are multiple XTA 9.728 versions on rapid.

<[AG]abma> [f=0000000] Using game archive: fdff84362dd9db524605925792e5c1cd.sdp
<[AG]abma> [f=0000000] Using game archive: fa954cc8cedea507fe2649d1bb1de94e.sdp
<[AG]abma> yours vs mine
<[2up]knorke> rapid vs sdz?
<[AG]abma> no, both on rapid
<[AG]abma> looks like two versions of "XTA 9.728" exist there

<[AG]abma> xta:revision:345,fa954cc8cedea507fe2649d1bb1de94e,,XTA 9.728
<[AG]abma> xta:stable,fa954cc8cedea507fe2649d1bb1de94e,,XTA 9.728
<[AG]abma> thats on rapid

<[AG]abma> ah, three versions: xta:latest,fdff84362dd9db524605925792e5c1cd,,XTA 9.728
<[AG]abma> it looks like someone did manual upload 9.728

Deleting wrong versions from rapid is not so easy (and players would have to do same) so best way to fix is new XTA version.
Current version is unplayable for/with some players so unless somebody screams STOP, I will do that in next few minutes...

[Silentwings]

I made exactly this mistake the first time we used RevisonNinja to put BA onto rapid - if you use VERSION{x.xx} then you shouldn't do a manual upload.

edit after doing VERSION you can fish out the sdz from here: http://packages.springrts.com/builds/

[knorke]

there is different content in the manual upload..looks like someone zipped up his development copy or something.

But there still is also a bug in rapid and abma was not certain if making new release via SVN would not create something broken again.
/edit
but now abma fixed something and i did VERSION{9.729}
now waiting..

[knorke]

The desyncs were caused by somebody manually making a XTA upload on rapid, parallel to the svn {version} thing, with different files. This kills the rapid and some players downloaded that wrong version.

abma fixed the other problem with rapid, whatever it was.
So then it was possible to make new mod release.
I know it is stupid to have a new XTA version again so soon but to "repair" 9.728 it would have been nessecary to:
-figure out which version in download system is the correct one and remove all others (not trivial appearently)
-tell all players to delete the broken files (which some would have missed to do, causing desync errors again)

Helium is now set to 9.729 and if one joins it should autodownload the mod. If not, download is here:
http://packages.springrts.com/builds/xta-9.729.sdz

Played a testgame with abma and it synced and everything seemed to work.

[Jools]

Well, some points:

* I committed 9.728 by using VERSION{9.728} in svn. I also put the same version to springfiles, but with the version in modinfo changed manually. Det also put a version manually to rapid, and this is the version that we put there. It's probably different only because the version tags are different.

* Having a new xta version out isn't bad anyway, it has some bugs fixed.

[Deadnight Warrior]

* I committed 9.728 by using VERSION{9.728} in svn. I also put the same version to springfiles, but with the version in modinfo changed manually.

Don't do that, archive CRC depends on file dates, so if you change anything after VERSION{9.728} or you did a SVN update on different time than rapid host, the archives' CRCs will be different and cause desync errors, even though the contents is byte identical.