Constant Sync Errors on Debian Testing (wheezy)

[yanom]

So I'm running Debian Testing (Wheezy) and whenever I play a game online I get sync errors - every mod, every map.

I installed spring from the Debian Testing repositories.

I only have one copy of each mod so it's not caused by conflicting mod data.

Does anyone know why I keep getting desynced?

[hoijui]

we believe it is cause they use gcc 4.6 in debian testing,
you could compile spring yourself with gcc 4.5-, or use the spring package from debian stable or ubuntu.

[jandd]

we believe it is cause they use gcc 4.6 in debian testing,
you could compile spring yourself with gcc 4.5-, or use the spring package from debian stable or ubuntu.

Yes it is caused by gcc 4.6 builds and happened on Fedora too. The problem is known as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629272

Maybe the information provided in the bug report can help to find the real cause of the problem.

[yanom]

kk. how do I use 4.5 insted of 4.6?

[hoijui]

i would recommend you try the ubuntu package first, before trying to compile.

Tests indicate, that the desync does not happen in spring master (and thus next release), so we do not plan to investigate further into why exactly this happens.

[yanom]

the package on the official ubuntu packages website is 0.82.5

Any other place I can get a .deb for current spring version?

EDIT: Or compile from source with gcc 4.5?

[koshi]

https://launchpad.net/~spring/+archive/ppa

[yanom]

https://launchpad.net/~spring/+archive/ppa

Tried that - it only works for Ubuntu. Trying it on Debian left some incomplete something or another.... it just wouldn't work.

[yanom]

I recompiled with GCC and G++ 4.5 and I still get the errors.

help!

[abma]

sorry, we currently don't know the reasion, why spring desyncs. i still guess it's because of some newer system-lib like boost/libdevil on the system, where spring is compiled.

you could try to run a win32-spring with wine... i know, thats an ugly solution, but it should work...


you also could debootstrap an ubuntu 10.04, and run it chrooted, that should work, too...

next release should/will fix that.