0.2.8_beta4: release process and bugs

[Z-Man]

Here come AMD64 binaries for Linux. They require libxml 2.6.0 or higher to be installed, unlike previous ones and the 32 bit builds, where libxml is included. I'm only posting them here only, in the hope that someone else can buld a better version to upload to SF/aabeta.

No RPMs. I can't build them any more.

Background: The system I'm building on changed from SuSE to Ubuntu. The RPM tools are installed, but don't seem to work properly, I get this error:

Code: Select all

+ rpmbuild -ba /files/home/part3/moos/NoBack/redhat/SPECS/armagetronad.spec
error: File : /files/home/part3/moos/NoBack/redhat/SOURCES/armagetronad-0.2.8_beta4.src.tar.bz2: No such file or directory
make: *** [builds/b_0.2.8_beta4/RC2/.rpm] Error 1
make: Target `rpm' not remade because of errors.
moos@l04:~/Tron/Release/0_2_8_beta4/release$ ls -l /files/home/part3/moos/NoBack/redhat/SOURCES/armagetronad-0.2.8_beta4.src.tar.bz2
-rw-r--r--  1 moos thp 1510883 2005-11-21 18:08 /files/home/part3/moos/NoBack/redhat/SOURCES/armagetronad-0.2.8_beta4.src.tar.bz2

So rpmbuild is not finding a file that exists and is readable. Strange.

Autopackage won't let me statically link to libxml compiled with apgcc. Static linking with a gcc compiled library may work, but then the glibc compatibility stuff autopackage provides does not work.

I'd also build .debs, but I don't have root access and fakeroot does not exist, either. What is it anyway?

[Z-Man]

Your_mom: here's your test EXE. Unzip it into a beta4 installation. It claims to be beta1, but that should not bother you. Start it from the installation directory, report back the exact content of the error message you get and the files stdout.txt and stderr.txt.
In fact, I think I found the reason for the failure and hope I fixed it; so with luck, you get a working version. In that case, please post stdout.txt and stderr.txt of a short session anyway.

Edit: it's compiled with VC6, so probably fits the VC6 distribution best.

[Fonkay]

I'm using the 0.2.8_beta_4.vc6 and while in fortress a few minutes ago, I had a crash. Some sort of runtime error.
When I restarted AA I could not get it to go into fullscreen. Played for a round or 2 in windowed, when it crashed again in the same way. a few others seemed to be going in and out as well. TheGuy (who i know has some form of beta_4) and belenus, and other users as well.
I'm going to DL and try the GCC, but I still can't seem to DL the vc8.

EDIT: I did manage to get the vc8 after all. Just took a bit of work, and the trial and error of chooing a mirror.

[Z-Man]

Fonkay: Can you try making a recording? It's in the start menu. For the initial crash, I mean. I can't do anything about the not-going-back-to-fullscreen thing from a recording, sorry. It's likely your video card got messed up.

[Your_mom]

Your_mom: here's your test EXE. Unzip it into a beta4 installation. It claims to be beta1, but that should not bother you. Start it from the installation directory, report back the exact content of the error message you get and the files stdout.txt and stderr.txt.
In fact, I think I found the reason for the failure and hope I fixed it; so with luck, you get a working version. In that case, please post stdout.txt and stderr.txt of a short session anyway.

Edit: it's compiled with VC6, so probably fits the VC6 distribution best.

The zip'd exe doesnt do anything (I put it in the beta4 vc6 dir like you said.), i try running it and nothing happens. Here's what was in stderr.txt, there was no stdout.txt

Error in in E:\Development\AADevel\0_2_8\beta4_vc6\armagetronad-0.2.8_beta4-win\src\tron\gArmagetron.cpp:527 :
var directory not writable or does not exist. It should reside inside your user data directory and should have been created automatically on first start, but something must have gone wrong. You can access your user data directory over one of the start menu entries we installed.

[Fonkay]

Of course, now that I'm ready to make a recording, it wont crash.

[crispy]

I get the following on 2 computers, my roommate's and my laptop, beta4 works fine on my main deskotp though

var directory not writable or does not exist. It should reside inside your user data directory and should have been created automatically on first start, but something must have gone wrong. You can access your user data directory over one of the start menu entries we installed.

var is definitely there and perms are set right

the vc builds give me the same error Your_mom was getting

on the brighter side.. got beta 4 running as a dedicated server on my fbsd box funky.beats.org =]

[Z-Man]

Welcome, crispy! Could you also try the zipped exe I uploaded?

Your_mom: Hmm, the stderr.txt looks like the one from the official beta4 exe, there definitely should be some more error output from the special exe. I'll have a look at it tonight, but could you try again in the meantime, deleting std*.txt before you do?

Fonkay: Yes, that is to be expected according to quantum mechanics Does recording hurt your performance? If no, I'd suggest you simply always play with recording enabled. If your client crashes again, quickly rename the recording on your desktop, start a new recording and try to reconnect. The second recording may be useful, too, and much smaller, so it will be easier to get to me.

[Your_mom]

Your_mom: Hmm, the stderr.txt looks like the one from the official beta4 exe, there definitely should be some more error output from the special exe. I'll have a look at it tonight, but could you try again in the meantime, deleting std*.txt before you do?

It doesnt load, or do anything. No errors, the game doesnt start. So i guess thats why nothing is generated

[hang3r]

(while this is off the current topic) For the record, i have not had beta4 compiled with mingw GCC crash yet. And i have been playing alot with it, everything seems fine.

[Z-Man]

Good to hear, hang3r.

Fonkay: I've had a look at the server logs; it appears it's the same error and crash Oscilloscope was reporting. Or was it nemo? A Mac user anyway. So it probably is not VC6's fault.
From the server's perspective, you simply logged out most of the time. You timed out only once. So there must be something wrong going on on the client. Triggered by something going wrong on the server, probably, but we can't have a client crashing just because it gets a corrupted packet.
So please, everyone: play with recording enabled. Delete the desktop icon and copy the recording start menu entry to your desktop instead if that helps.

[Z-Man]

About the voting problems: It seems beta3 and beta4 clients let the votes time out too early. It's a clientside bug. Additionally, votes timed out too early for old clients. That's a serverside bug fixable by changing settings (increase VOTING_TIMEOUT).

Tank: Time to add the beta to the web page.
I'll merge beta4 back into the trunk tonight. Seems stable enough.

[Your_mom]

@z-man - should i just wait for beta-5(or a final release)?

[Z-Man]

@z-man - should i just wait for beta-5(or a final release)?

I'll probably build an unofficial sort of beta-4.2 the next days and post it here, yes, you should wait for that.

The merge is complete. I used

Code: Select all

cvs update -j v0_2_8_beta1 -j v0_2_8_beta4

and there were only trivial conflicts.

[Revan]

No, it isn't. I didn't know about a warpy wall glitch, so logically, I could not fix it.
Unless, of course, it was one of the side effects of the timer problems. Sounds like it could be. So maybe it's fixed. If not, please provide details

Yeah I'm talking about that timer thingy where every time you turned on a server my walls would warp..Warpy Walls!