Re: [Warzone-dev] Bug#458275: should warzone2100 (beta) be in Debian testing (and migrate to stable)?
On Wed, 2008-07-23 at 01:15 +0200, Giel van Schijndel wrote: Any thoughts on this? Another beta might be a good idea, if it is done quickly. Also, when the final release is done, we can put a warzone2100 backport on backports.org for lenny users to upgrade to. Many people don't know about backports.org though, so that might become a support issue/FAQ for the warzone devs. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone-commits] r5639 - in /branches/2.1: ./ data/tagdefinitions/savegame/map.def src/droid.c src/function.c src/game.c src/map.c src/oprint.c src/research.c src/researchdef.h src/
On Tue, Jul 22, 2008 at 8:53 PM, Giel van Schijndel [EMAIL PROTECTED] wrote: All just bugfixes? No, all of that boils down to code removal actually. The only code that cannot contain bugs is no code. That is not true. Code removal can definitely trigger new bugs. Even if the code removal is done correctly, the removed code might contain a (perhaps accidental) workaround for some bug that was not anticipated or known beforehand. There is no good reason to backport anything that is not strictly necessary to a stable branch nearing release. Stop doing it. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] [bug #12070] 2.1 branch FTBFS from r5639 onwards
URL: http://gna.org/bugs/?12070 Summary: 2.1 branch FTBFS from r5639 onwards Project: Warzone Resurrection Project Submitted by: pabs Submitted on: Wednesday 07/23/2008 at 07:01 Category: None Severity: Blocker Priority: 5 - Normal Status: None Assigned to: None Originator Email: Open/Closed: Open Discussion Lock: Any Release: svn/branches/2.1 Operating System: GNU/Linux Planned Release: None ___ Details: Cannot build the 2.1 branch at the moment: make[3]: Entering directory `/home/pabs/devel/games/warzone/src' gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DYY_NO_INPUT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -I/usr/include/libpng12-DDEBUG -DDATADIR=\/home/pabs/opt/share/warzone2100\ -DLOCALEDIR=\/home/pabs/opt/share/locale\ -I.. -O0 -g -Wall -Werror -Wno-unused-label -Wno-pointer-to-int-cast -Wmissing-field-initializers -Wcast-align -Wwrite-strings -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith -MT stats.o -MD -MP -MF .deps/stats.Tpo -c -o stats.o stats.c cc1: warnings being treated as errors stats.c: In function ‘loadPropulsionStats’: stats.c:1054: error: passing argument 2 of ‘getPropulsionType’ from incompatible pointer type make[3]: *** [stats.o] Error 1 ___ Reply to this item at: http://gna.org/bugs/?12070 ___ Message sent via/by Gna! http://gna.org/ ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] [bug #12083] radar's frustum is drawn incorrectly
URL: http://gna.org/bugs/?12083 Summary: radar's frustum is drawn incorrectly Project: Warzone Resurrection Project Submitted by: None Submitted on: Thursday 07/24/2008 at 04:35 CEST Category: Engine: Graphics Severity: Normal Priority: 5 - Normal Status: None Assigned to: None Originator Email: meh Open/Closed: Open Discussion Lock: Any Release: svn/trunk Operating System: All Planned Release: None ___ Details: On the bigger maps, the coordinates turn negative when the mouse cursor approaches the top boundry of the radar window, and it draws the 'frustum' incorrectly as a result. On smaller maps, it kicks the frustum to the upper left. ___ File Attachments: --- Date: Thursday 07/24/2008 at 04:35 CEST Name: wz2100_shot_028.jpg Size: 49kB By: None http://gna.org/bugs/download.php?file_id=4624 --- Date: Thursday 07/24/2008 at 04:35 CEST Name: wz2100_shot_027.jpg Size: 48kB By: None http://gna.org/bugs/download.php?file_id=4623 ___ Reply to this item at: http://gna.org/bugs/?12083 ___ Message sent via/by Gna! http://gna.org/ ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Bug#458275: should warzone2100 (beta) be in Debian testing (and migrate to stable)?
On 7/23/08, Giel van Schijndel [EMAIL PROTECTED] wrote: Paul Wise schreef: On Wed, 2008-07-23 at 01:15 +0200, Giel van Schijndel wrote: Any thoughts on this? Another beta might be a good idea, if it is done quickly. Also, when the final release is done, we can put a warzone2100 backport on backports.org for lenny users to upgrade to. Many people don't know about backports.org though, so that might become a support issue/FAQ for the warzone devs. To all devs (with or without commit access): I would really like this to be an active decision on our part, as opposed to a passive one, where we allow the decision to be made for us due to time passing. I.e. either we decide that we do want our current state of 2.1 to be included in Debian's next stable release, or we decide that we don't want that to happen. As long as that decision is an active one, I can live with both. The only negative impact of this on us I can see is the support/FAQ issue mentioned above by Paul. -- Giel For what it is worth, I rather have 2.1 (beta or not) be included, for the simple fact that if it is not, then people keep submitting bugs for 2.0.10, and that doesn't do anybody any good. I guess you could add/modify the version string on the main menu, to point people to backports.org, or stick it in the README file or whatever. I don't see that as big of a negative compared to getting old bug reports. I don't suppose it is possible to include them both? I say that since I know that 2.0.10 works on systems that 2.1 don't work on, be it because it is running on very low end hardware, and or having some kind of issues with one of the newer libs we use (QuesoGLC or fontconfig or...), but it might be nice to have that as a option. I know that 2.0.10 won't be maintained, but that version of warzone is better than having no warzone right? (Yes, I know that defeats what I wrote above, about the bug reports, but I digress! ;)) ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
