[Warzone-dev] [bug #12368] Task switching problem
Follow-up Comment #1, bug #12368 (project warzone): Likely a bug in Windows and/or SDL. Thus likely to be Closed/Invalid, sorry. Open a bugreport with Microsoft and/or libsdl. Also: Which version of Windows is that? With any visual extras installed? Graphics card/drivers? ___ Reply to this item at: http://gna.org/bugs/?12368 ___ Nachricht geschickt von/durch Gna! http://gna.org/ ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Montag, 29. September 2008 02:07:12 schrieb [EMAIL PROTECTED]: The Buildbot has detected a new failure of nightly_mingw32 on Warzone 2100: Resurrection Project. Full details are available at: http://build.kynes.de/builders/nightly_mingw32/builds/2 Buildbot URL: http://build.kynes.de/ Buildslave for this Build: i386-debian-etch-2 Build Reason: The Nightly scheduler named 'nightly' triggered this build Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed compile warnings+100 This was a *desired* failure. (In reality we have 505 warnings during builds on the nightly node.) Since everything seemed to work I am removing the hardcoded warningscount and let it measure the warnings itself again. --Devu 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
[Warzone-dev] [bug #12368] Task switching problem
Follow-up Comment #2, bug #12368 (project warzone): I am using Windows XP Home Edition, Service Pack 2. My graphics card is an NVIDIA GeForce 6800. No special graphical gimmicks have been installed. It could be a bug with SDL - I will see if I can investigate that one myself. ___ Reply to this item at: http://gna.org/bugs/?12368 ___ 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 #12370] AI building on burning oil wells.
URL: http://gna.org/bugs/?12370 Summary: AI building on burning oil wells. Project: Warzone Resurrection Project Submitted by: crane Submitted on: Monday 29/09/08 at 12:43 Category: AI Severity: Normal Priority: 5 - Normal Status: None Assigned to: None Originator Email: Open/Closed: Open Discussion Lock: Any Release: 2.1_beta4 Operating System: Microsoft Windows Planned Release: None ___ Details: It was observed in a 2 human vs. 2 AI game that the AI can build on a burning oil well if the well's former derrick belonged to the other AI player. This seems a little unfair to human players. Crane ___ Reply to this item at: http://gna.org/bugs/?12370 ___ 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] [Warzone-commits] r6090 - /branches/2.1/ /branches/2.1/pkg/dpkg/changelog /tags/2.1_beta5/ /tags/2.1_beta5/autorevision.conf /tags/2.1_beta5/makerules/config.mk.tmpl /tags/2.1_beta5/
Dennis Schridde schreef: Am Sonntag, 28. September 2008 15:50:24 schrieb Giel van Schijndel: Tag of the `2.1 beta 5` release http://wiki.wz2100.net/Release_checklist Please follow all the steps listed there. (Missing translation import and bugtracker version increment made me notice you did not. Others may be missing as well, I did not check that.) AFAIK only project admins can do the bug tracker increment. As for translation import, honestly I haven't ever done anything with Launchpad, so I wouldn't know where to start (I saw there where only about 10ish newly translated strings though). As for the checklist, I followed it except for these two things: * Create an AutoPackage / MojoSetup * Announce the release (didn't announce through all channels yet) As for announcing, these are done: * forum/frontpage: has been done * dev mailinglist: I thought this should be done automatically by sending the forum/frontpage notice to the ML (though as of yet I didn't see anything) * IRC Channel: topic is changed, but I'm not going to spam a message constantly * ModDB: Done [1] [1] http://www.moddb.com/games/warzone-2100/news/warzone-2100-21-beta-5-released -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Dennis Schridde schreef: Am Montag, 29. September 2008 02:07:12 schrieb [EMAIL PROTECTED]: The Buildbot has detected a new failure of nightly_mingw32 on Warzone 2100: Resurrection Project. Full details are available at: http://build.kynes.de/builders/nightly_mingw32/builds/2 Buildbot URL: http://build.kynes.de/ Buildslave for this Build: i386-debian-etch-2 Build Reason: The Nightly scheduler named 'nightly' triggered this build Build Source Stamp: HEAD Blamelist: BUILD FAILED: failed compile warnings+100 This was a *desired* failure. (In reality we have 505 warnings during builds on the nightly node.) Since everything seemed to work I am removing the hardcoded warningscount and let it measure the warnings itself again. As interesting as these notices may be, could you please redirect these debug messages/mails to another e-mail address when you're just testing stuff out. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone-commits] r6090 - /bran ches/2.1/ /branches/2.1/pkg/dpkg/changelog /tags/2 .1_beta5/ /tags/2.1_beta5/autorevision.conf /tags/2.1_beta5/makerules/config.mk.tmpl /tags /2.1_be
Am Montag, 29. September 2008 17:10:55 schrieb Giel van Schijndel: Dennis Schridde schreef: Am Sonntag, 28. September 2008 15:50:24 schrieb Giel van Schijndel: Tag of the `2.1 beta 5` release http://wiki.wz2100.net/Release_checklist Please follow all the steps listed there. (Missing translation import and bugtracker version increment made me notice you did not. Others may be missing as well, I did not check that.) AFAIK only project admins can do the bug tracker increment. As for translation import, honestly I haven't ever done anything with Launchpad, so I wouldn't know where to start (I saw there where only about 10ish newly translated strings though). There is a download all translations link (or similar). Click it, and you'll receive a download-link via email, approx 5-10 minutes later. You'll extract that package somewhere and copy over the files in it into the Warzone 2100 directory. You have to look at the diffs though and take care to update the list of copyright owners at the start of the file. Afterwards merge back any changes you made into Launchpad. (I know it's a hassle, but this seems to be the only source for translations atm...) As for the checklist, I followed it except for these two things: * Create an AutoPackage / MojoSetup We left that out for the betas till now. I'll start producing MojoSetup files again when I got time, after the final release. * Announce the release (didn't announce through all channels yet) See my addition to the release-checklist on this. As for announcing, these are done: * forum/frontpage: has been done * dev mailinglist: I thought this should be done automatically by sending the forum/frontpage notice to the ML (though as of yet I didn't see anything) That worked for the last releases afaik... Something broken, Kamaze? * IRC Channel: topic is changed, but I'm not going to spam a message constantly Spamming is not required. --Devu 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
[Warzone-dev] [Warzone 2100 Trac] #81: Game crashes during saving after building a derrick
#81: Game crashes during saving after building a derrick --+- Reporter: Tycho451 |Type: defect Status: new|Priority: critical Milestone: | Component: Campaign Version: svn/trunk |Keywords: crash save savegame tagfile Operating_system: All| --+- When you start a campaign start bulding a derrick. After the first ingame video try to save and the game will crash. It seems this bug was introduced with revision 6081. The output hints toward a problem with the tagfile. I have attached the relevant part of the debug=all output and the warzone2100.gdmp. -- Ticket URL: http://developer.wz2100.net/ticket/81 Warzone 2100 Trac http://wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[Warzone-dev] [Warzone 2100 Trac] #82: Stuck units
#82: Stuck units --+- Reporter: NewTiberian|Type: defect Status: new|Priority: major Milestone: | Component: other Version: svn/trunk |Keywords: Operating_system: Microsoft Windows | --+- recently (somewhere in the last 100 revisions or so) i have been encountering this very annoying problem of units becoming randomly stuck. I have attached a video, since the sticking is not preserved in a savegame -- Ticket URL: http://developer.wz2100.net/ticket/82 Warzone 2100 Trac http://wz2100.net/ The Warzone 2100 Resurrection Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
