0.2.8_beta3: release process and bugs
0.2.8_beta3: release process and bugs
The initial tag for beta3 is done; since yesterday, the following moves have been made:
- a small notice has been added to the map tutorial about its current outdated status.
- Fortress zone rotation speed fixed (the zone was initially non-rotating)
- "make dist" fixed for the resources
- The "Element not in heap" error message has gotten an additional description; it usually indicates an error further ahead.
- When there is packet loss, the network does not try frantically to fire out the same message a thousand times in rapid succession.
Known problems that won't be fixed for beta3:
- More than two fortress zones don't make too much sense for now. I'm working on it, but not for the beta.
- There are these random connection losses. As far as I can tell, they are real network problems (messages being sent, but not received), but somehow the reason for that must be rooted in the code. It seems to happen more frequently on full servers.
- The "User 0 timed out" problem is still there, and still with unknown cause.
- Configuration strings, most notably MAP_FILE, cannot have spaces in them. I'll add quoting for the release candidate.
- Arena walls are still not properly visible when viewed head on, and the texture stretching bug is still there.
- a small notice has been added to the map tutorial about its current outdated status.
- Fortress zone rotation speed fixed (the zone was initially non-rotating)
- "make dist" fixed for the resources
- The "Element not in heap" error message has gotten an additional description; it usually indicates an error further ahead.
- When there is packet loss, the network does not try frantically to fire out the same message a thousand times in rapid succession.
Known problems that won't be fixed for beta3:
- More than two fortress zones don't make too much sense for now. I'm working on it, but not for the beta.
- There are these random connection losses. As far as I can tell, they are real network problems (messages being sent, but not received), but somehow the reason for that must be rooted in the code. It seems to happen more frequently on full servers.
- The "User 0 timed out" problem is still there, and still with unknown cause.
- Configuration strings, most notably MAP_FILE, cannot have spaces in them. I'll add quoting for the release candidate.
- Arena walls are still not properly visible when viewed head on, and the texture stretching bug is still there.
Last edited by Z-Man on Mon Oct 24, 2005 11:38 am, edited 1 time in total.
Oh, I forgot.
What I'm waiting for before I publish the archives:
Lucifer had these problems with Belly of the Beast. I'm waiting for reports that indicate it's completely his own fault
I found at least one of the reasons the game sometimes crashes when you leave a server (missing NULL pointer checks again). I'll include that fix as well.
What I'm waiting for before I publish the archives:
Lucifer had these problems with Belly of the Beast. I'm waiting for reports that indicate it's completely his own fault

I found at least one of the reasons the game sometimes crashes when you leave a server (missing NULL pointer checks again). I'll include that fix as well.
I guess we don't need to hold up the release for invisible bugs on my server anymore, right? 

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
- klax
- Project Developer
- Posts: 481
- Joined: Tue Jun 08, 2004 3:51 pm
- Location: Barcelona, Spain
- Contact:
Edit: Integrated debian build into generic build. But still don't know why armagetronad is build 3 times (1st one isn't used)...
Don't know where to upload packages, I upload them here gzipped:
armagetronad 0.2.8.0 beta3 - Ubuntu Breezy 5.10 amd64 packages:
Don't know where to upload packages, I upload them here gzipped:
armagetronad 0.2.8.0 beta3 - Ubuntu Breezy 5.10 amd64 packages:
You do not have the required permissions to view the files attached to this post.
Sweet, klax.
The x86 builds are up on aabeta!
http://beta.armagetronad.net/?product=a ... =#download
Edit: the 64 bit builds are up there, too. One problem with the 64 bit .package files: they don't install on the system they were build with; I get a strange GLIBC error.
And whoops, I think the .package files were done in debug mode. I've got to take care of proper integration.
The x86 builds are up on aabeta!
http://beta.armagetronad.net/?product=a ... =#download
Edit: the 64 bit builds are up there, too. One problem with the 64 bit .package files: they don't install on the system they were build with; I get a strange GLIBC error.
And whoops, I think the .package files were done in debug mode. I've got to take care of proper integration.
- klax
- Project Developer
- Posts: 481
- Joined: Tue Jun 08, 2004 3:51 pm
- Location: Barcelona, Spain
- Contact:
Time for ubuntu breezy 32bit debs.
Now with the generic build system in 32bit chroot it builds armagetronad 2 times... I believe I need a rest hehe
Please, people with debian systems try these builds to test compatibility between debian and ubuntu breezy.
armagetronad 0.2.8.0 beta3 - Ubuntu Breezy 5.10 i386 packages:
Now with the generic build system in 32bit chroot it builds armagetronad 2 times... I believe I need a rest hehe
Please, people with debian systems try these builds to test compatibility between debian and ubuntu breezy.
armagetronad 0.2.8.0 beta3 - Ubuntu Breezy 5.10 i386 packages:
You do not have the required permissions to view the files attached to this post.
I'll upload klax's builds to SF. Klax, what parts of the names are changable? If I want to put them up on aabeta, I have to conform to Luke's standards, and they require changing the OS part of the filename at least. The version, too, probably.
Edit: The two "common" packets have the same name; do they have the same content? Do I remember correctly that they contain the configuration and data files?
Edit: The two "common" packets have the same name; do they have the same content? Do I remember correctly that they contain the configuration and data files?
- klax
- Project Developer
- Posts: 481
- Joined: Tue Jun 08, 2004 3:51 pm
- Location: Barcelona, Spain
- Contact:
I believe I can only change this part (0.2.8.0beta3-1)z-man wrote:I'll upload klax's builds to SF. Klax, what parts of the names are changable? If I want to put them up on aabeta, I have to conform to Luke's standards, and they require changing the OS part of the filename at least. The version, too, probably.
Edit: The two "common" packets have the same name; do they have the same content? Do I remember correctly that they contain the configuration and data files?
The architecture isn't changeable because an error is thrown in dh_gencontrol, and I believe debian is very strict about architectures...
The more I can get is this:
armagetronad_0.2.8beta3-1.inst.gnulinux_i386.deb
Yep they should have the same content hehe.
- philippeqc
- Long Poster - Project Developer - Sage
- Posts: 1526
- Joined: Mon Jul 12, 2004 8:55 am
- Location: Stockholm
- Contact:
Re: Release process for 0.2.8_beta3
That was for me and I didnt notice it ;)z-man wrote:- a small notice has been added to the map tutorial about its current outdated status.
Could someone make sure to remind me in due time to copy the whole wiki page in the tutorial to be shipped in time for the final release? (*)
Thanks
-ph
* The raw wiki format is quite readable, with its nice "==" and "===" and "'''". I'm sure some people would appreciate having at least a good copy locally rather than always relying on a net connection ;)
Canis meus id comedit.
Re: Release process for 0.2.8_beta3
In that case, we might consider having the documentation generator work off the wiki and move all the documentation to the wiki. In this case we'd keep a copy of the documentation in cvs (so building cvs shouldn't require the wiki be available), and then we could update the documentation periodically in cvs. This would break the "no auto-generated files in cvs" rule.philippeqc wrote: * The raw wiki format is quite readable, with its nice "==" and "===" and "'''". I'm sure some people would appreciate having at least a good copy locally rather than always relying on a net connection
The thing to know here is that it's possible to have the wiki export each page to a certain xml format, which we can then transform into plaintext for documentation. So that's not hard, the tools are there, we just need to wrap them up. The xml format the wiki exports doesn't render the wiki text, it leaves it as-is, but adds some meta data to the xml, like the edit history.
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
- Tank Program
- Forum & Project Admin, PhD
- Posts: 6712
- Joined: Thu Dec 18, 2003 7:03 pm
Finally, a Mac OS X 10.2 version. 10.2 user(s?) rejoice!
10.2.8 build tested, everything worked fine.
10.3+ build tested, worked fine.
The Recorder app to start Armagetron Advanced recordings does not work on 10.2, so they must start it the painful way.
http://generalconsumption.org/armagetro ... x10.3+.dmg
http://generalconsumption.org/armagetro ... 10.2.8.dmg
10.2.8 build tested, everything worked fine.
10.3+ build tested, worked fine.
The Recorder app to start Armagetron Advanced recordings does not work on 10.2, so they must start it the painful way.
Code: Select all
./Armagetron\ Advanced.app/Contents/MacOS/Armagetron\ Advanced --record ~/your_file.rec
http://generalconsumption.org/armagetro ... 10.2.8.dmg