Release process for 0.2.8_beta2
Release process for 0.2.8_beta2
The bug count seems to be rapidly decreasing; so I'd suggest we tag the sources for the second beta on Friday so we can build the binaries over the weekend. Or are there other improvements I'm currently not aware of we want in the second beta?
I'd like an opportunity to sanity-check the Mandriva packages, but I should have that before Friday. 
Also, I'd like to have an Autopackage build of beta2, but I probably need some help there. The issues involve resolving the SDL dependency somehow. The problem was getting it to staticly link SDL for the build, which I wasn't able to do. With that problem resolved, we should be good to go for the autopackage build.
So, beta2 I'm wanting to have a Mandriva client package that works for Swampy, a Mandriva dedicated server package that works for Swampy (I can build it on my 10.1 machine if I need to), and an Autopackage build of the client. I'd like to have an autopackage build of the server, too, which shouldn't be too terribly difficult, but I'm not in a hurry to make it. (Well, I am in a hurry to make it, but there's three packages that I rank as higher priority than it, and I'm willing to go without an autopackage server)
(to answer preemptively, the reason I want it to work for Swampy isn't because I'm singling him out, it's because he's testing it in an ass-different environment than I'm building, making a successful test on his machine easy to extrapolate as WorksForAll)
(Also, my currently-installed beta1 is now too old for me to find new bugs, and since I switched my sandbox out with cvs head I'm currently unable to build a new beta without a fresh checkout. Been lazy on that front, sorry)

Also, I'd like to have an Autopackage build of beta2, but I probably need some help there. The issues involve resolving the SDL dependency somehow. The problem was getting it to staticly link SDL for the build, which I wasn't able to do. With that problem resolved, we should be good to go for the autopackage build.
So, beta2 I'm wanting to have a Mandriva client package that works for Swampy, a Mandriva dedicated server package that works for Swampy (I can build it on my 10.1 machine if I need to), and an Autopackage build of the client. I'd like to have an autopackage build of the server, too, which shouldn't be too terribly difficult, but I'm not in a hurry to make it. (Well, I am in a hurry to make it, but there's three packages that I rank as higher priority than it, and I'm willing to go without an autopackage server)
(to answer preemptively, the reason I want it to work for Swampy isn't because I'm singling him out, it's because he's testing it in an ass-different environment than I'm building, making a successful test on his machine easy to extrapolate as WorksForAll)
(Also, my currently-installed beta1 is now too old for me to find new bugs, and since I switched my sandbox out with cvs head I'm currently unable to build a new beta without a fresh checkout. Been lazy on that front, sorry)
Check out my YouTube channel: https://youtube.com/@davefancella?si=H--oCK3k_dQ1laDN
Be the devil's own, Lucifer's my name.
- Iron Maiden
Be the devil's own, Lucifer's my name.
- Iron Maiden
I think I can try to help out with the autopackage problems. The specfiles or whatever they are called are in the armagetronad_build module, right? I also had my problems with static linking I want solved; our biggest dependency trouble is the C++ standard library, and I could not get that one statically linked for the life of me.
That reminds me, I wanted to staticly link the C++ standard library too.z-man wrote:I think I can try to help out with the autopackage problems. The specfiles or whatever they are called are in the armagetronad_build module, right? I also had my problems with static linking I want solved; our biggest dependency trouble is the C++ standard library, and I could not get that one statically linked for the life of me.

The spec file is in armagetronad_build/autopackage, iirc. You have to run makeinstaller from the armagetronad_build root. I did that so it could easily be added to the makefile there.

Check out my YouTube channel: https://youtube.com/@davefancella?si=H--oCK3k_dQ1laDN
Be the devil's own, Lucifer's my name.
- Iron Maiden
Be the devil's own, Lucifer's my name.
- Iron Maiden
-
- Dr Z Level
- Posts: 2246
- Joined: Sun Mar 20, 2005 4:03 pm
- Location: IM: luke@dashjr.org
Couple little bugs i noticed but never got round to posting...
When i press network connect it dosnt load up the server list for me i have to press refresh then it does.. im on windows beta1..
there was one more little nagging one when i remember it ill edit this and put it here....
When i press network connect it dosnt load up the server list for me i have to press refresh then it does.. im on windows beta1..
there was one more little nagging one when i remember it ill edit this and put it here....
Damn, it sure has been a while!
Also, when i get scilenced i usually hit escape and press disc and hit enter twice fast and it reconnects fast..
But now it crashes the client and gives me a bug popup and the client sitll shows open under task bar but dosnt do anything (this is the other i couldnt remember.
But now it crashes the client and gives me a bug popup and the client sitll shows open under task bar but dosnt do anything (this is the other i couldnt remember.
Damn, it sure has been a while!
-
- Dr Z Level
- Posts: 2246
- Joined: Sun Mar 20, 2005 4:03 pm
- Location: IM: luke@dashjr.org
We could add an option to auto-ban someone who disconnects for ten seconds or so. When he reconnects fast, he'll get the two minute penaltyLuke-Jr wrote:Hmm, so should servers block a fast (user-commanded) reconnect?TiTnAsS wrote:Also, when i get scilenced i usually hit escape and press disc and hit enter twice fast and it reconnects fast..

TnA: The second one is no little annoyance. Crashes are serious. Can you try to make a recording? There must be something else involved, fast reconnecting works for me here.
The first one may be an uninitialized variable; I could use a recording there, too, because (you guessed it) it works for me.
To make a recording, open a console window and enter (assuming you installed AA on E:\Program Files\Armagetronad)
Code: Select all
E:\
cd "\Program Files\Armagetronad"
.\armagetronad.exe --record crash.rec
"Error in in
E:\Development\AADevel\0_2_8_beta1_debug\armagetronad\src\network
\nNetObject.cpp:811 :
Netobject 41078 requested, but was never spawned."
Thats the error msg i get with the crash after trying to reconnect. This time it let me reconnect once and then i tried again a minute later and it crashed and gave me that message and said armagetron was open on the task bar, but when i clicked it it didn't do anything...
Heres a screenshot of the other problem. What it does is just sit like that til i hit r...it only happens sometimes though.
E:\Development\AADevel\0_2_8_beta1_debug\armagetronad\src\network
\nNetObject.cpp:811 :
Netobject 41078 requested, but was never spawned."
Thats the error msg i get with the crash after trying to reconnect. This time it let me reconnect once and then i tried again a minute later and it crashed and gave me that message and said armagetron was open on the task bar, but when i clicked it it didn't do anything...
Heres a screenshot of the other problem. What it does is just sit like that til i hit r...it only happens sometimes though.
You do not have the required permissions to view the files attached to this post.
Damn, it sure has been a while!
Thanks, that netobject info could be useful; this means the error is not really Windows specific. And it also means it's probaly related to the bugs nemo posted about, the missing player and the messaging clutter (the clutter comes from the same function as your error message).
With "console window" I meant the thing that comes with windows; in earlier times, it was called "Dos box", it may also go as "Command line interface" or whatever.
Here, please unzip the attached archive into your AA installation directory (so armagetronad.exe and the .bats are in the same directory) and start record.bat with a doubleclick. Try to reproduce the bugs as fast as possible (so the recording size is small and you can upload the result here); test the recording with playback.bat. Then, upload the file bug.aarec here (zipped, so you're allowed to do so). record.bat will overwrite the previous recording, so you'll have to do one bug at a time.
With "console window" I meant the thing that comes with windows; in earlier times, it was called "Dos box", it may also go as "Command line interface" or whatever.
Here, please unzip the attached archive into your AA installation directory (so armagetronad.exe and the .bats are in the same directory) and start record.bat with a doubleclick. Try to reproduce the bugs as fast as possible (so the recording size is small and you can upload the result here); test the recording with playback.bat. Then, upload the file bug.aarec here (zipped, so you're allowed to do so). record.bat will overwrite the previous recording, so you'll have to do one bug at a time.
You do not have the required permissions to view the files attached to this post.