| 00:19.07 | TD-Linux | since when does dolphin use openmp? |
| 00:52.56 | *** join/#bzflag Gnurdux (~gnurdux@c-24-6-185-47.hsd1.ca.comcast.net) |
| 02:43.03 | *** join/#bzflag bryjen (~bryjen@76.92.85.169) |
| 02:43.04 | *** mode/#bzflag [+v bryjen] by ChanServ |
| 02:45.08 | CIA-5 | BZFlag: 03Sigonasr2 07http://my.bzflag.org * r7796 10/w/Bz_ePlayerPausedEvent: Some fixes to what the event's members actually are. Also name clarity. |
| 06:23.50 | *** join/#bzflag Marzipan- (~Marzipan@p5B222C75.dip.t-dialin.net) |
| 06:24.48 | *** join/#bzflag Marzipan (~Marzipan@bzflag/player/Marzipan) |
| 08:19.48 | *** join/#bzflag fahadsadah (fahad@unaffiliated/fahadsadah) |
| 08:22.35 | *** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org) |
| 09:30.43 | *** join/#bzflag MindstormsKid_ (~msk@Wikipedia/MindstormsKid) |
| 09:33.30 | *** part/#bzflag MindstormsKid_ (~msk@Wikipedia/MindstormsKid) |
| 10:48.31 | *** join/#bzflag saxotest (~chatzilla@216.252.79.92) |
| 10:57.59 | saxotest | hi all, can someone help me, bzflag (2.0.16) makes my new system "unstable" (not sure how to describe it)... |
| 10:58.47 | saxotest | i got the message "Nvidia OpenGL driver lost connection with display driver... Application must close." |
| 11:03.47 | saxotest | i can play bzflag for a short time but after that it will always freeze the system completely (i.e. mouse cursor stuck, cant turn on caps lock, etc) |
| 11:07.30 | saxotest | sometimes it "unfreezes" after a while, and all tanks are [nr] |
| 11:07.47 | saxotest | one time i got the above message |
| 11:12.02 | joevano | saxotest: that is not bzflag... probably the video driver |
| 11:12.43 | saxotest | :( |
| 11:12.44 | joevano | do you have the most recent driver from the NVidia web site? |
| 11:12.58 | saxotest | i updated it yesterday though |
| 11:13.04 | saxotest | nyes |
| 11:18.24 | Constitution | should the config upgrade feature possibly skip over the "directory" option, since the listing could be (is probably) incompatible with newer versions? |
| 11:20.55 | saxotest | i just noticed in bzflag the msg "OpenGL Driver: GT430/PCI/SSE2" |
| 11:27.01 | Constitution | also, mac rc3 build is posted |
| 12:10.29 | *** join/#bzflag saxotest (~chatzilla@216.252.79.92) |
| 13:56.50 | trepan | OT: http://tauday.com/ - apparently i'm not the only one who feels that a plethora of '2's have died in vain |
| 14:50.51 | *** join/#bzflag bier (~bier@p54A5B575.dip.t-dialin.net) |
| 14:51.09 | *** join/#bzflag bier|tp (~bier@p54A5B575.dip.t-dialin.net) |
| 14:52.08 | blast007 | Constitution: hmm, yeah, it probably should |
| 14:53.55 | *** join/#bzflag QuantumBeep (~QuantumB@cpe-76-186-97-233.tx.res.rr.com) |
| 15:08.17 | *** join/#bzflag JeffM (~JeffM@unaffiliated/jeffm2501) |
| 15:08.17 | *** mode/#bzflag [+v JeffM] by ChanServ |
| 15:08.49 | *** join/#bzflag AAA_awright (~a3@ip24-251-157-63.ph.ph.cox.net) |
| 15:13.20 | *** mode/#bzflag [+o JeffM] by ChanServ |
| 15:13.52 | *** topic/#bzflag by JeffM -> http://my.BZFlag.org || http://cia.vc/stats/project/BZFlag || http://my.BZFlag.org/w/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4 release is nigh! || The PLAN http://my.bzflag.org/w/Development_RoadMap |
| 15:28.56 | *** join/#bzflag Constitution (~const@bzflag/developer/Constitution) |
| 15:32.21 | *** join/#bzflag DTRemenak (~DTRemenak@76-227-151-154.lightspeed.irvnca.sbcglobal.net) |
| 15:49.49 | *** join/#bzflag moiree (~moiree@dslb-084-059-059-231.pools.arcor-ip.net) |
| 15:54.53 | *** join/#bzflag moiree (~moiree@dslb-084-059-059-231.pools.arcor-ip.net) |
| 15:58.08 | moiree | ~seen CIA-5 |
| 15:58.12 | ibot | cia-5 is currently on #bzflag. Has said a total of 97 messages. Is idling for 13h 13m 4s, last said: 'BZFlag: 03Sigonasr2 07http://my.bzflag.org * r7796 10/w/Bz_ePlayerPausedEvent: Some fixes to what the event's members actually are. Also name clarity.'. |
| 16:02.48 | BulletCatcher | hugs CIA-5 |
| 16:02.49 | CIA-5 | hugs BulletCatcher |
| 16:04.35 | JeffM | we ready to do this? |
| 16:11.11 | BulletCatcher | I can't see a reason to wait unless we want blast007 and/or Constitution here in real time. |
| 16:11.27 | JeffM | you want to do the checklist? |
| 16:11.31 | JeffM | you are good at checklists |
| 16:11.38 | BulletCatcher | :-) ok |
| 16:11.45 | blast007 | and I'm here |
| 16:11.48 | BulletCatcher | yay |
| 16:11.53 | *** topic/#bzflag by JeffM -> http://my.BZFlag.org || http://cia.vc/stats/project/BZFlag || http://my.BZFlag.org/w/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || 2.4 release is nigh! where nigh == now|| The PLAN http://my.bzflag.org/w/Development_RoadMap |
| 16:13.01 | BulletCatcher | Do we want to put anything in the NEWS file? |
| 16:14.03 | JeffM | it's one line |
| 16:14.47 | delusional | make sure publickey is mentioned prominently... especially on the forum |
| 16:15.00 | delusional | the forum thread says 2.99 still |
| 16:15.19 | blast007 | it's in the upgrade doc on the wiki, and bzfs will nag you if you don't include it |
| 16:15.20 | JeffM | the news file points to the change log |
| 16:15.32 | BulletCatcher | If that's all we have to say then we could just delete NEWS, but first I want to see whether it is "required" by GNU standards. |
| 16:15.53 | JeffM | I think thats the only reason it si there, GNU or debian need it |
| 16:15.58 | delusional | what about the web-access manpage |
| 16:16.07 | blast007 | delusional: hmm? |
| 16:16.07 | BulletCatcher | Yep. autogen.sh wants it to be there. |
| 16:16.37 | BulletCatcher | I see no reason to change it. |
| 16:16.53 | JeffM | we will mention the key again in the release announcment too |
| 16:16.55 | BulletCatcher | "Wake the Dead" is the name? |
| 16:17.02 | JeffM | sure |
| 16:17.57 | delusional | still comes up blank... http://my.bzflag.org/bzfman.cgi?bzw.5.in is it bzw.6.in ? |
| 16:18.12 | blast007 | delusional: none of the man pages for that work |
| 16:18.53 | JeffM | post the windows htmls |
| 16:20.05 | blast007 | it's just pointing to the wrong URL right now in the script |
| 16:20.22 | blast007 | I figure after we release 2.4.0 I'll point it to the v2_4 branch files |
| 16:21.51 | BulletCatcher | About the v2_4 branch: I would rather see 2.4 development continue on trunk for now so we don't have to double-commit for 2.6. |
| 16:21.52 | BulletCatcher | This would require us to refrain from doing 2.6 for awhile. |
| 16:26.19 | BulletCatcher | But the tagged copy of 2.4.0 should be stable. |
| 16:27.12 | JeffM | yes all we do is tag this time |
| 16:27.23 | JeffM | the roadmap does not say to start 2.6 yet |
| 16:27.46 | BulletCatcher | The roadmap will say whatever we want it to say. :-) |
| 16:27.49 | JeffM | I expect 2.4 to be trunk for 4-6 months |
| 16:27.54 | JeffM | true |
| 16:28.09 | JeffM | there is still much we have left to do in 2.4 |
| 16:28.16 | CIA-5 | BZFlag: 03bullet_catcher * r22050 10/trunk/bzflag/ChangeLog: |
| 16:28.16 | CIA-5 | BZFlag: Set 2.4.0 release name and date. |
| 16:28.16 | CIA-5 | BZFlag: Fix a spelling error and improve grammar. |
| 16:30.33 | BulletCatcher | Bah. bzfs_conf.html does not support openFFA. |
| 16:31.08 | JeffM | we can fix that in a point release if nobody wants to do it right now |
| 16:32.31 | BulletCatcher | That should be fine. It gets used, but not a lot. |
| 16:32.42 | blast007 | I never liked that |
| 16:32.51 | blast007 | it makes it easy for people to make invalid configurations |
| 16:33.02 | BulletCatcher | then fix it :-) |
| 16:33.03 | blast007 | and then they don't know why it's broken because they have this massive configuration |
| 16:33.20 | blast007 | my "fix" would be getting rid of it ;) |
| 16:33.39 | blast007 | replace it with a link to the BZFS man page :P |
| 16:34.54 | JeffM | maybe link to the wiki and provide some more samples |
| 16:35.01 | JeffM | but yes they really should know whats in there |
| 16:35.32 | BulletCatcher | You're the title.png expert, JeffM. It is time for 2.4.0. |
| 16:35.56 | JeffM | expert no.. have a license of photoshop.. yes |
| 16:36.05 | BulletCatcher | close enough :-) |
| 16:36.41 | BulletCatcher | I'll make a note to play with it in GIMP some time. |
| 16:37.11 | JeffM | doubt the source art will open cleanly in gimp |
| 16:37.17 | JeffM | it uses an layer effect |
| 16:37.41 | CIA-5 | BZFlag: 03JeffM2501 * r22051 10/trunk/bzflag/ (data/title.png misc/art/title.psd): update to 2.4.0 |
| 16:39.17 | BulletCatcher | A quick look seems to confirm that. |
| 16:39.33 | JeffM | is not a fan of the gimp |
| 16:39.51 | *** join/#bzflag randomparticle (~randompar@about/essy/snick/randomparticle) |
| 16:39.54 | BulletCatcher | Set BZ_BUILD_TYPE to STABLE or MAINT ? |
| 16:40.17 | JeffM | stable |
| 16:40.23 | JeffM | 4.2.2 will be maint |
| 16:40.30 | BulletCatcher | k |
| 16:40.44 | JeffM | tho personaly I'd just change em to "RELEASE" |
| 16:40.48 | JeffM | and combine em |
| 16:41.06 | BulletCatcher | Maybe later. |
| 16:41.19 | JeffM | mayhaps |
| 16:42.04 | BulletCatcher | 0221 is the next proto number. Do we want to use a more interesting value? |
| 16:42.24 | JeffM | it's just a number |
| 16:43.02 | BulletCatcher | We haven't made any real changes since RC3, so there wouldn't be any real harm in letting RC3 clients play on 2.4 servers. |
| 16:43.31 | JeffM | i'd still bump it just to be consistent |
| 16:43.39 | BulletCatcher | 0221 it is, then |
| 16:43.40 | JeffM | the few servers will update and be fine |
| 16:47.14 | BulletCatcher | Just remembered: should we discard the -directory setting from version 3 client config files? |
| 16:47.46 | JeffM | for the client? |
| 16:48.09 | BulletCatcher | Yes, since any previous setting will probably be wrong for 2.4. |
| 16:48.37 | JeffM | well if they use it then our defalut will be wrong too |
| 16:48.44 | JeffM | so ignoring it won't fix anything |
| 16:53.18 | JeffM | I'd leave it cus there is a non zero chance they will install the new bzflag into the same location and it will be right |
| 16:53.42 | BulletCatcher | k |
| 16:54.20 | JeffM | cus really it's only for nixies |
| 16:56.30 | trepan | could check for $USER/treads.png and $DEFAULT/treads.png, and emit an appropriate message (or just do the switch) |
| 16:57.12 | *** join/#bzflag mdskpr (6c199168@gateway/web/freenode/ip.108.25.145.104) |
| 16:59.58 | *** join/#bzflag AAA_awright (~a3@ip24-251-157-63.ph.ph.cox.net) |
| 17:01.30 | BulletCatcher | Let's just leave it as is, and let the help desk deal with the customer calls about it. |
| 17:02.44 | BulletCatcher | Last chance before I commit the new version number... |
| 17:03.12 | JeffM | go for i |
| 17:03.14 | JeffM | it |
| 17:04.44 | CIA-5 | BZFlag: 03bullet_catcher * r22052 10/trunk/bzflag/ (8 files in 5 dirs): |
| 17:04.44 | CIA-5 | BZFlag: Update version number to 2.4.0 for release. |
| 17:04.44 | CIA-5 | BZFlag: Congratulations to the developers for a job well done. |
| 17:05.37 | mdskpr | :D |
| 17:05.40 | BulletCatcher | Please recompile, everyone, to ensure that it still works. |
| 17:08.44 | blast007 | at least the server builds fine on linux :) |
| 17:09.51 | *** join/#bzflag Anxuiz (~Anxuiz@50-46-121-138.evrt.wa.frontiernet.net) |
| 17:09.51 | *** join/#bzflag Anxuiz (~Anxuiz@unaffiliated/anxuiz) |
| 17:10.56 | JeffM | 64 bit installer is done, building 32 |
| 17:12.44 | blast007 | and I should be able to do 64-bit bins in the future. reinstalled VS with that enabled from the start ;) |
| 17:12.55 | JeffM | coo |
| 17:17.47 | JeffM | 32's done |
| 17:20.28 | BulletCatcher | Glad it works. |
| 17:20.31 | BulletCatcher | It probably isn't critical, but DEVINFO does say to build the uploaded binaries from a source tarball that is generated from the tagged copy. |
| 17:21.23 | JeffM | yeah yeah yeah, I never do that :) |
| 17:21.29 | BulletCatcher | :-p |
| 17:22.10 | JeffM | those instructions were by tim for linux builds |
| 17:22.18 | BulletCatcher | My Linux build is successful. |
| 17:24.14 | BulletCatcher | I am now compiling on the Mac. |
| 17:28.35 | *** join/#bzflag AAA_awright (~a3@ip24-251-157-63.ph.ph.cox.net) |
| 17:33.24 | *** join/#bzflag QuantumBeep (~QuantumB@cpe-76-186-97-233.tx.res.rr.com) |
| 17:35.20 | BulletCatcher | Happy Mac. |
| 17:35.25 | *** join/#bzflag allejo (~allejo@cpe-76-95-144-121.socal.res.rr.com) |
| 17:35.53 | BulletCatcher | I'm ready to do the tagged copy, now. |
| 17:36.03 | allejo | any bzexcess admins here? come to brl.arpa.net:5165 |
| 17:36.27 | BulletCatcher | That's my server. I'll be right there. |
| 17:36.58 | allejo | mind getting rid of spermbobspoogepants? |
| 17:37.49 | QuantumBeep | if I was rich I'd get a lawyer and sue that dude |
| 17:37.56 | QuantumBeep | for being the biggest darn wart on the game |
| 17:38.31 | allejo | thanks blast007 and BulletCatcher :) |
| 17:38.44 | BulletCatcher | Democracy saved the day before we got there. |
| 17:39.10 | BulletCatcher | My mistake. It was blast007. |
| 17:39.31 | BulletCatcher | Yay for pillbox. |
| 17:40.05 | BulletCatcher | Anyone having 2.4.0 build problems? |
| 17:43.00 | allejo | not here on a mac :) |
| 17:43.34 | moiree | Yes, but is it bzflag related? |
| 17:43.37 | moiree | g++-4.6.real: error: /usr/lib/gcc/i486-linux-gnu/4.6.1/crtbeginS.o: No such file or directory |
| 17:43.40 | moiree | g++-4.6.real: error: /usr/lib/gcc/i486-linux-gnu/4.6.1/crtendS.o: No such file or directory |
| 17:44.27 | BulletCatcher | I think you are missing one of the gcc packages, moiree. |
| 17:44.44 | BulletCatcher | What is your distro? |
| 17:45.06 | moiree | debian broken^Wtesting |
| 17:45.44 | moiree | Well, it worked before I updated g++ today :) |
| 17:45.56 | trepan | .real? |
| 17:47.04 | BulletCatcher | Did you update gcc, too? |
| 17:51.38 | CIA-5 | BZFlag: 03bullet_catcher * r22053 10/tags/v2_4_0/: Tagged copy of r22052, BZFlag version 2.4.0. |
| 17:54.51 | BulletCatcher | That didn't quite work as I expected, but it is close enough. |
| 17:55.59 | blast007 | yeah, think you normally have to create the directory structure first, and then copy into it with a second commit |
| 17:56.03 | blast007 | it's weird |
| 18:01.44 | BulletCatcher | The bzflag subdirectory does not appear in the svn export. The usual files are directly under v2_4_0. |
| 18:02.08 | blast007 | yeah, you'd have to had created that before the svn copy |
| 18:04.07 | *** join/#bzflag bryjen (~bryjen@76.92.85.169) |
| 18:04.07 | *** mode/#bzflag [+v bryjen] by ChanServ |
| 18:10.59 | moiree | It seems they forgot to symlink /usr/lib/i386-linux-gnu/gcc/i486-linux-gnu/4.6.1 to /usr/lib/gcc/i486-linux-gnu/4.6.1 |
| 18:14.42 | BulletCatcher | I have the source tarballs built, I just need to test building from them. |
| 18:15.22 | mdskpr | where are they? |
| 18:15.43 | BulletCatcher | On my computer, still. They will be uploaded to SourceForge soon. |
| 18:17.30 | *** join/#bzflag AAA_awright_ (~a3@ip24-251-157-63.ph.ph.cox.net) |
| 18:23.35 | BulletCatcher | JeffM: Feel free to upload your Windows binaries to SourceForge. |
| 18:23.45 | JeffM | heh, dude I did that an hour ago |
| 18:23.52 | BulletCatcher | :-) |
| 18:24.40 | BulletCatcher | Can we rename? I don't see a need for the date in the file names. |
| 18:24.52 | JeffM | I do |
| 18:24.57 | BulletCatcher | k |
| 18:24.57 | JeffM | in case we have to update them |
| 18:25.09 | JeffM | I'd rather keep it consistent |
| 18:25.24 | JeffM | then if we have to change them, like repackage 2.4.0 for some reason people know what they have |
| 18:25.30 | BulletCatcher | Should I put dates in the source file names? |
| 18:25.37 | JeffM | yeah |
| 18:25.48 | JeffM | just in case we have to bump something in the tag and repack |
| 18:25.49 | BulletCatcher | k |
| 18:26.10 | JeffM | Id rather have the date and not need it then not have it and wish we did |
| 18:28.32 | Pimpinella | guess i can make svn snapshot packages for debian stable and unstable and ubuntu LTS |
| 18:28.43 | delusional | i'm not getting groups right now |
| 18:30.31 | *** join/#bzflag meeba (~lamer@c-71-196-238-53.hsd1.co.comcast.net) |
| 18:31.10 | BulletCatcher | saturates his upstream bandwidth |
| 18:32.04 | blast007 | ;) |
| 18:32.38 | blast007 | delusional: what do you mean? |
| 18:33.20 | delusional | my group file loaded... not getting @ |
| 18:33.28 | delusional | this is on my home connection |
| 18:33.32 | JeffM | bets someone didn't use his public key |
| 18:33.46 | delusional | cant do anything withot publickey |
| 18:33.47 | blast007 | he's on the list |
| 18:36.53 | BulletCatcher | 2.4.0 sources are now up at SourceForge |
| 18:37.48 | Pimpinella | delusional: did you read this? |
| 18:37.51 | Pimpinella | http://my.bzflag.org/w/BZFS_2.4_Upgrade#Server_Groups |
| 18:38.10 | delusional | ahh, thanks pimpi |
| 18:38.28 | delusional | bzfs says that it loaded |
| 18:38.53 | CIA-5 | BZFlag: 03bullet_catcher * r22054 10/trunk/bzflag/ (3 files in 3 dirs): Bump version to 2.4.1 for the next phase of development. |
| 18:38.58 | Pimpinella | not sure if the changes could mess up your settings that much though |
| 18:40.25 | Pimpinella | delusional: yes, it still loads, but in some cases the results of parsing a groupdb file can be different |
| 18:40.51 | BulletCatcher | It took 2 1/2 hours to do that release. |
| 18:40.53 | BulletCatcher | It could have been faster, but I was being careful. |
| 18:41.18 | BulletCatcher | Thanks to all who contributed in any way. |
| 18:41.50 | blast007 | BulletCatcher: and thanks for getting a plan started that enabled us to get to this point :) |
| 18:42.15 | BulletCatcher | You're welcome. |
| 18:45.09 | Constitution | ~celebrate |
| 18:45.09 | ibot | ACTION lights off 3 tons of fireworks |
| 18:45.22 | delusional | 2 days early |
| 18:45.28 | BulletCatcher | You still have work to do, Constitution. :-) |
| 18:45.48 | Constitution | whistles peacefully |
| 18:48.49 | JeffM | plan together love |
| 18:52.02 | JeffM | goes back to trying to understand how UDP works |
| 18:54.28 | Pimpinella | hands JeffM his "Stevens" copy |
| 18:55.07 | JeffM | mostly I just want to know if there is one socket per connection or just one enpoint |
| 18:55.41 | bryjen | udp is connection less |
| 18:56.14 | JeffM | so the socket may or may not be reused |
| 18:56.53 | JeffM | how does the sender listen back for packets back from the server? does it's socket it used to send just stay open for a bit? |
| 18:57.04 | JeffM | cus I don't think I can do a listener on the client side |
| 18:57.35 | bryjen | i'd think it silly if you had to open/close the socket for each message... |
| 18:57.43 | JeffM | as do I |
| 18:57.56 | JeffM | do they just time out if nothing gets sent in a while? |
| 18:58.10 | BulletCatcher | Not necessarily. |
| 18:58.34 | BulletCatcher | Servers may keep UDP ports open indefinitely. |
| 18:58.43 | JeffM | what about clients? |
| 18:58.51 | BulletCatcher | They can, too. |
| 18:58.58 | JeffM | ok |
| 18:59.11 | JeffM | so as long as I have an endpoint back to the client I should be able to send data |
| 18:59.20 | JeffM | and as long as they have a socket to me they can send data |
| 18:59.33 | bryjen | there's no connection to timeout. tcp is like a phone call. udp is like exchaning a series of postcards. |
| 18:59.34 | JeffM | but it looks like multiple endpoints can come into the server over the same socket |
| 18:59.40 | JeffM | since it's connectionless |
| 18:59.53 | BulletCatcher | yup |
| 18:59.54 | JeffM | yeah I guess I see the socket "connect" as doing somthing |
| 18:59.57 | JeffM | but it isn't |
| 19:00.20 | JeffM | just trying to see how it all would have to fit in with TCP |
| 19:00.38 | blast007 | ooo, or do you not have a blank line at the end of the file? |
| 19:00.41 | blast007 | ww |
| 19:00.54 | trepan | JeffM: something else to consider, http://en.wikipedia.org/wiki/UDP_hole_punching |
| 19:01.23 | JeffM | ahh I was wondering how it all worked with nat |
| 19:01.54 | bryjen | not very well really. that an issue with nat |
| 19:02.08 | JeffM | looks like sending a heartbeat packet helps |
| 19:04.52 | JeffM | now wonders how busy costco will be today |
| 19:15.33 | delusional | maaaaaannnnn ... that groups wiki page makes me more confused than when i started... it tells me a bunch of things I should not do... not much about what i should do. |
| 19:16.57 | delusional | one example has + and * in front of the permissions, the other does not |
| 19:17.40 | blast007 | + isn't needed afaik, as it should be implied when you have a permission |
| 19:17.52 | blast007 | * is not used for permissions, it is used for referencing another group |
| 19:21.53 | *** join/#bzflag DTRemenak (~DTRemenak@76-227-151-154.lightspeed.irvnca.sbcglobal.net) |
| 19:22.40 | *** join/#bzflag TD-Linux (~thomas@about/essy/indecisive/TD-Linux) |
| 19:25.24 | Pimpinella | another GM bug :( |
| 19:25.46 | blast007 | ? |
| 19:26.10 | Pimpinella | if you lock on a tank, then that tank gets ST the brackets remain |
| 19:26.11 | CIA-5 | BZFlag: 03bullet_catcher * r22055 10/trunk/bzflag/src/bzflag/motd.cxx: Remove redundant #include of bzregex.h or regex.h. |
| 19:27.12 | Pimpinella | stupid i never tried that |
| 19:27.54 | blast007 | oh well |
| 19:28.06 | BulletCatcher | Does the GM itself stay locked? |
| 19:28.09 | Pimpinella | lets see if it homes |
| 19:28.10 | blast007 | yes |
| 19:28.12 | blast007 | it does |
| 19:28.16 | Pimpinella | nwas about to try |
| 19:28.27 | blast007 | if you lock on a tank and do not fire, it will remain locked |
| 19:28.47 | blast007 | it only unlocks when the a shot ends and it is the last active shot |
| 19:29.23 | Pimpinella | yep, the brackets go away after you fired |
| 19:29.46 | blast007 | not a huge issue, really |
| 19:30.01 | blast007 | and servers can always _forbidMarkers |
| 19:30.52 | BulletCatcher | Let me restate my question: If you lock your GM on a tank that then grabs ST, will the missile still track the stealthed tank? |
| 19:31.09 | Pimpinella | yes, i guess so |
| 19:31.17 | Pimpinella | testing |
| 19:31.43 | Pimpinella | ppl left |
| 19:31.46 | Constitution | call it a feature |
| 19:31.52 | Pimpinella | he |
| 19:33.41 | blast007 | BulletCatcher: yes |
| 19:33.43 | Pimpinella | they will, throughout the whole lifetime of 2.4 |
| 19:34.00 | blast007 | BulletCatcher: you could lock onto a player, they could grab ST, and you could wait 5 minutes before firing at them and still be locked ;) |
| 19:34.21 | blast007 | been that way for as long as I can remember |
| 19:34.37 | Pimpinella | so, leave it? fix it? |
| 19:34.43 | blast007 | leave it |
| 19:34.48 | blast007 | it's too late for 2.4.x |
| 19:34.50 | Pimpinella | imho it's unexpected behavior |
| 19:34.58 | blast007 | if we want to change that, we can fix it in 2.6.0 |
| 19:35.08 | blast007 | oh well |
| 19:35.12 | BulletCatcher | If it is not a regression then I am ok to leave it. |
| 19:35.22 | blast007 | it's been that way probably even in 1.7 |
| 19:35.29 | blast007 | and probably before that :) |
| 19:36.29 | Pimpinella | ok then |
| 19:36.50 | BulletCatcher | Our goal for 2.4 was not to fix every bug in 2.0. |
| 19:37.38 | Pimpinella | it just becomes obvious now, like the other occasions when the target was not reset when it should |
| 19:37.48 | Pimpinella | it's a feature then |
| 19:37.53 | BulletCatcher | yup |
| 19:38.29 | blast007 | I've used that "feature" in the past :) |
| 19:38.35 | BulletCatcher | hax! |
| 19:38.56 | blast007 | lock on a target, but don't fire, and do a spin jump around an obstacle and hit them where you normally couldn't get a lock on |
| 19:39.13 | blast007 | a lock on in time* |
| 19:39.30 | blast007 | or through a teleporter ;) |
| 19:39.45 | blast007 | lock on, turn around, fire into a teleporter at close range |
| 19:40.06 | BulletCatcher | I often use the GM through the telporter trick on MW. |
| 19:40.50 | *** join/#bzflag QuantumBeep (~QuantumB@cpe-76-186-97-233.tx.res.rr.com) |
| 19:41.11 | BulletCatcher | I'm just glad we don't have to release 2.6 already. :-) |
| 19:41.56 | blast007 | if anything we'd have just released 2.4.2 with _forbidMarkers defaulting to 1 ;) |
| 19:42.11 | BulletCatcher | That would do it. |
| 19:42.22 | BulletCatcher | Someone ought to udate the topic. |
| 19:42.33 | *** mode/#bzflag [+o blast007] by ChanServ |
| 19:42.57 | *** topic/#bzflag by blast007 -> http://my.BZFlag.org || http://cia.vc/stats/project/BZFlag || http://my.BZFlag.org/w/Getting_Help || Channel Logs: http://ibot.rikers.org/%23bzflag/ || BZFlag 2.4.0 has been released! || The PLAN http://my.bzflag.org/w/Development_RoadMap |
| 19:46.44 | trepan | hm, forgot to add the _forbid's to the ChangeLog |
| 19:58.34 | Pimpinella | just tried, GM won't home on the stealthened tank, even though the marker remains |
| 19:58.48 | blast007 | Pimpinella: let me come try with you |
| 19:59.03 | Pimpinella | yours MW2? |
| 19:59.23 | blast007 | sure |
| 20:00.39 | *** join/#bzflag tupone (~tupone@gentoo/developer/tupone) |
| 20:00.39 | *** mode/#bzflag [+v tupone] by ChanServ |
| 20:03.44 | Pimpinella | blast007: it GM doesn't home we can safly remove the brackets on the stealthened tank in .2 |
| 20:04.02 | blast007 | maybe |
| 20:04.07 | blast007 | it changes the client behavior |
| 20:05.34 | Pimpinella | but it's not consistent now |
| 20:05.47 | Pimpinella | lets see |
| 20:05.51 | blast007 | we'll have to think about it |
| 20:05.56 | Pimpinella | yep |
| 20:06.02 | blast007 | because then it would not be consistent between 2.4.x versions |
| 20:06.15 | blast007 | if we leave it, it's at least consistently wrong ;) |
| 20:07.13 | blast007 | and if we remove it, some people will keep running 2.4.0, and then people will start banning 2.4.0 users, etc |
| 20:07.30 | Pimpinella | yep, that happened in 2.0 |
| 20:07.38 | blast007 | full screen radar ;) |
| 20:07.39 | Pimpinella | don't remember what the bug was |
| 20:08.03 | blast007 | that was the big one that made people stick with older versions.. we clamped the maximum radar size in a future release |
| 20:08.28 | Pimpinella | there was something else iirc |
| 20:08.33 | blast007 | in 2.0.0? |
| 20:08.57 | Pimpinella | until 2.0.2 probably |
| 20:09.07 | blast007 | yeah |
| 20:09.14 | blast007 | 2.0.0 was pretty buggy :) |
| 20:09.25 | blast007 | are you thinking of the spin inversion thing? |
| 20:09.34 | Pimpinella | full scren radar could still enabled by editing the config file |
| 20:09.45 | Pimpinella | ahm yes! |
| 20:10.30 | Pimpinella | i had long discussions with players wether it was allowed to use that since it was in an official client |
| 20:10.48 | Pimpinella | and they called it a feature ;) |
| 20:11.12 | Pimpinella | but this is not that much a serious bug |
| 20:11.34 | blast007 | right, so no reason to fix it ;) |
| 20:11.39 | *** mode/#bzflag [-o blast007] by blast007 |
| 20:12.24 | Pimpinella | or no reason not to remove it, but i really can live with it either way |
| 20:13.33 | Pimpinella | i just bite my ass of finding a bug RIGHT after release ;) |
| 20:13.36 | JeffM | there are all kinds of logical problems with GM and locking |
| 20:13.44 | JeffM | have been for a while |
| 20:14.04 | Pimpinella | yep, i fixed a couple of them |
| 20:14.12 | JeffM | like you only send GM updates when you have the flag, so on a shot limited server your last shot never tracks |
| 20:14.22 | JeffM | the entire thing needs to move to the server |
| 20:14.46 | Pimpinella | sure |
| 20:15.51 | JeffM | at some point we have to decide if the GM "flag" represents a load of missles, or that and the lockon hardware |
| 20:16.19 | Pimpinella | uh? |
| 20:16.26 | tupone | may I ask why the source release tar ball name now include the date suffix? Is it something wanted? |
| 20:16.28 | Pimpinella | guess i didn't understand that |
| 20:16.49 | JeffM | tupone, we went to 4 numbers to make repackages easier if we screw up |
| 20:17.10 | JeffM | and so the source matches all the bins |
| 20:17.25 | blast007 | unless the OSX bin doesn't get released today ;) |
| 20:17.49 | JeffM | he can name it based on the source package he built from |
| 20:17.57 | blast007 | true |
| 20:18.19 | blast007 | already had one PPC user ask about 2.4 |
| 20:18.40 | JeffM | did you tell him that even apple dosn't love him anymore? |
| 20:18.45 | blast007 | lol |
| 20:19.03 | blast007 | I said something to the effect of "use a mac from the last 5 years ..." |
| 20:19.04 | tupone | That was if you called the release 2.4.0.20110703 But that has been called 2.4.0-20110703 |
| 20:19.08 | blast007 | they were on an eMac |
| 20:19.26 | JeffM | tupone, yeah I was expecting a . not a - but BulletCatcher did the naming |
| 20:19.31 | JeffM | I would prefer a . |
| 20:19.48 | Pimpinella | JeffM: could you point out " at some point we have to decide if the GM "flag" represents a load of missles, or that and the lockon hardware" some more? |
| 20:20.18 | blast007 | Pimpinella: think he means "if the flag drops, should the locks stop as well" |
| 20:20.19 | JeffM | Pimpinella, from a gameplay standpoint should you be able to lock and guide missies while you have GM shots in flight, or just while you have the flag |
| 20:20.21 | blast007 | or something like that |
| 20:20.51 | JeffM | personaly I think it should be while any are in flight, then the GM flag is just the ability to fire the missle, the guidance is always with the tank |
| 20:21.03 | blast007 | if anything, the markers have indicated some flaws in the game logic for us :) |
| 20:21.08 | JeffM | indeed |
| 20:21.12 | JeffM | since they are just showing existing data |
| 20:21.19 | tupone | with the - I need to (or someone need) to change the instruction to build bzflag in gentoo, and maybe in other distro as well. With the . only the change to the whole file name will do the right thing |
| 20:21.24 | KTL | The following NEW packages will be installed: |
| 20:21.24 | KTL | <PROTECTED> |
| 20:21.31 | KTL | debian is up to date there |
| 20:21.35 | JeffM | tupone, ok then we will change it to a . |
| 20:22.17 | KTL | ow no ... the new bzflag package is ... 2.0.16.20100405 ??? |
| 20:22.20 | JeffM | well can't rename so time to uplaod |
| 20:22.24 | JeffM | KTL, yup |
| 20:22.37 | JeffM | can someone do the sources, I'll do the winbins |
| 20:22.37 | KTL | shouldnt it be 2.4 ... ?? |
| 20:22.38 | blast007 | can't from FTP either? |
| 20:23.06 | JeffM | sorry yeah 2.4.0.20110703 |
| 20:23.09 | Pimpinella | IMHO the missile should home on whichever target it was fired on, so logic should be per missile |
| 20:23.20 | JeffM | Pimpinella, you can relock during flight |
| 20:23.26 | JeffM | but that also is something we should discuss |
| 20:23.34 | JeffM | does the last missie just go to the last target and no relocks |
| 20:23.39 | Pimpinella | ah, yes |
| 20:23.42 | JeffM | these are all the things I think we need to decide on |
| 20:24.01 | Pimpinella | hmm, well |
| 20:24.06 | trepan | no relocking - but maybe allow unlocking (to avoid team kills) |
| 20:24.08 | JeffM | but not till later :) |
| 20:24.16 | JeffM | perhaps |
| 20:24.17 | blast007 | trepan: but then that's not consistent ;) |
| 20:24.21 | JeffM | all valid ideas |
| 20:24.28 | blast007 | if you can remotely unlock a missile, why can't you lock it onto something else? |
| 20:24.42 | trepan | cheap electronics, of course :) |
| 20:24.52 | Pimpinella | i think we want to keep it be able to lock in flight |
| 20:25.03 | trepan | need the big machine housed in the tank to calc the firing solution |
| 20:25.11 | blast007 | trepan: then maybe we should make the jump jets on the tank randomly explode when used :P |
| 20:25.36 | trepan | always gets a kick out of that in the movies, mucho calc firing solutions |
| 20:26.01 | JeffM | this is why for consistency we need to decide what the flag itself does to the tank :) |
| 20:26.12 | JeffM | uploads some more packages |
| 20:26.50 | trepan | blast007: a little randomness in the height might be neat |
| 20:27.06 | blast007 | JeffM: I can get the source ones if nobody else is doing it right now |
| 20:27.14 | JeffM | go for it |
| 20:27.32 | BulletCatcher | The version number of this release is 2.4.0 . Its sources are distributed in files named bzflag-2.4.0-20110703.* . |
| 20:28.00 | JeffM | BulletCatcher, we went to a 4 digit number system reemmber |
| 20:28.14 | JeffM | I'd make the date be the build number |
| 20:28.22 | JeffM | it'll always get bigger ;) |
| 20:28.25 | blast007 | okay, but is the fourth number a datestamp, or a 0-based incrementing number? |
| 20:28.34 | JeffM | I say datestamp |
| 20:28.36 | BulletCatcher | We should be good with 2.4.0 until there is a need for 2.4.0.1 . |
| 20:28.41 | trepan | SVN rev |
| 20:28.46 | JeffM | or svn rev |
| 20:28.54 | JeffM | svn rev is probably best |
| 20:29.23 | tupone | I need to have a way to get the file name from the release number |
| 20:29.41 | JeffM | the third number should be a number not something with a - |
| 20:30.05 | blast007 | tupone: so what exactly are you needing then? |
| 20:30.13 | BulletCatcher | Then we can just upload more copies to SourceForge with the date string stripped from the file names. |
| 20:30.28 | blast007 | tupone: you're saying that gentoo can't handle a datestamp or an svn rev in the filename of the source package? |
| 20:30.36 | JeffM | if the date is not part of the version it dosn't need to be in the file name, sf keeps the uplaod date |
| 20:30.47 | JeffM | blast007, I don't think it can handle the - as it sits now |
| 20:31.21 | blast007 | so should we just do them as bzflag-2.4.0.whatever for now? |
| 20:31.27 | JeffM | yes |
| 20:31.32 | blast007 | whateverextension, I mean |
| 20:31.38 | BulletCatcher | bzflag-2.4.0.zip, etc. |
| 20:31.42 | JeffM | the question is what is the whatever, date, incremental build, or svn |
| 20:31.43 | tupone | blast007, not that. I need to get a file name from the release number. Release number is something like x.y.z.u.v |
| 20:31.44 | JeffM | I say svn |
| 20:31.52 | blast007 | and if we do a 2.4.0.1, we'll just include the fourth number |
| 20:32.19 | JeffM | yes |
| 20:32.27 | blast007 | doing the SVN rev makes it a bit more.. complicated |
| 20:32.35 | JeffM | then incrmeental it is |
| 20:32.41 | JeffM | so this release is 2.4.0.0 |
| 20:32.42 | blast007 | since isn't the source archives built from an SVN export? |
| 20:33.05 | BulletCatcher | The top-level directory in the tarballs is named bzflag-2.4.0 . |
| 20:33.35 | blast007 | buildDate.cxx also doesn't have anything to define a fourth number |
| 20:33.38 | JeffM | BulletCatcher, yeah but if I find that I have to rebuild the windows installers cus I included a bad component I need to name it something |
| 20:33.47 | JeffM | blast007, yes because the 4th is JUST package changes |
| 20:33.50 | blast007 | k |
| 20:33.53 | JeffM | not code changes |
| 20:34.17 | JeffM | like if I messed up a shortcut, or someone forgot a file in the distro build |
| 20:34.31 | JeffM | just some way to let people know that one download is different then another |
| 20:34.41 | blast007 | so should the fourth number just be left off UNLESS we are doing a package rebuild? |
| 20:34.43 | BulletCatcher | I assume we will change BZ_REV to "0.1" when if we release 2.4.0.1. |
| 20:34.53 | JeffM | I'd keep it in there for consitency |
| 20:34.59 | JeffM | BulletCatcher, nope |
| 20:35.06 | tupone | If the top level directory is named after the release is better (2.0.16 followed that). Otherwise I have to code the top level naming rules |
| 20:35.08 | JeffM | that'd be for 2.4.1 |
| 20:35.31 | JeffM | the game itslef dosn't care about the package version cus package changes do not change any compiled code |
| 20:35.44 | BulletCatcher | If we do 2.4.0.1 we'll have to make a branch for it. |
| 20:35.50 | JeffM | a tag |
| 20:35.51 | blast007 | tag* |
| 20:35.58 | JeffM | or we'll update the existing tag |
| 20:36.05 | JeffM | that's what we've done in the past when we screw up :) |
| 20:36.14 | BulletCatcher | k |
| 20:36.25 | blast007 | SVN isn't the best for tagging.. |
| 20:36.36 | blast007 | even CVS was better at doing tags, no? |
| 20:36.40 | JeffM | sice there sould be no reason for anyone to go and need to build 2.4.0.0 |
| 20:36.47 | JeffM | tags are branches in SVN |
| 20:36.49 | JeffM | they work fine |
| 20:36.59 | JeffM | you can commit to a tag, merge to a tag |
| 20:37.02 | blast007 | by some definitions of fine |
| 20:37.09 | JeffM | I've never had a problem with them |
| 20:37.17 | JeffM | CVS always ate tehm |
| 20:37.18 | BulletCatcher | tupone: If I re-upload the existing files with -20110703 removed from their names will that work for you? |
| 20:37.32 | blast007 | BulletCatcher: and I can do that here myself too |
| 20:37.35 | blast007 | I have them downloaded |
| 20:37.40 | JeffM | put a .0 on em |
| 20:37.43 | BulletCatcher | no |
| 20:37.47 | JeffM | yes |
| 20:37.57 | BulletCatcher | The top-level directory has to match the file name too. |
| 20:38.03 | blast007 | BulletCatcher: ah.. |
| 20:38.10 | JeffM | then people will know to EXPECT a 4th and it won't be a shock |
| 20:38.21 | blast007 | the top level dir is 2.4.0, BulletCatcher |
| 20:38.26 | JeffM | yes the top level is for the CURRENT version of packages |
| 20:38.31 | JeffM | they don't have to nor should match |
| 20:38.42 | BulletCatcher | RPM expects it to match. |
| 20:38.56 | tupone | BulletCatcher, it is a step ahead. I can test it, then |
| 20:38.57 | blast007 | we're talking about in the archive, JeffM |
| 20:39.11 | JeffM | there is a folder in the archive? |
| 20:39.19 | blast007 | yeah, bzflag-2.4.0 |
| 20:39.28 | JeffM | oh then yeah I don't care about that :) |
| 20:39.45 | JeffM | make that be "bzflag i use linux and am sad.0.0" :) |
| 20:39.47 | blast007 | BulletCatcher: based on that, the source archives shouldn't have the date in them, right? :) |
| 20:39.59 | BulletCatcher | Right. |
| 20:39.59 | JeffM | I'd REALLY like the 4th number in the file we produce |
| 20:40.01 | blast007 | should just be bzflag-2.4.0.tar.gz |
| 20:40.08 | BulletCatcher | JeffM: It is too late for 2.4.0. |
| 20:40.22 | blast007 | we'll just do it like firefox does and not include it until we need it :P |
| 20:40.29 | JeffM | ok, then scrap .0 and we'll do 2.4.2.0 today |
| 20:40.35 | JeffM | I want us to be consistent |
| 20:40.58 | JeffM | I don't see why it's "too late" |
| 20:41.02 | JeffM | we haven't announced anything |
| 20:41.06 | blast007 | I did ;) |
| 20:41.10 | JeffM | then delete it |
| 20:41.32 | JeffM | cus the moment we have to do 2.4.0.1 tupone is going to be back here saying the same thing |
| 20:42.14 | BulletCatcher | We'll cross that bridge when we come to it. |
| 20:42.25 | JeffM | also if we are removing zeroes why is it not just 2.4? |
| 20:42.39 | BulletCatcher | Good question, but 2.4.0 is done. |
| 20:42.41 | blast007 | because the client/server is 2.4.0 |
| 20:43.08 | JeffM | and the package is 2.4.0.0 |
| 20:43.27 | tupone | if you do 2.4.0.1 we have to change virtually nothing if you call the tar ball bzflag-2.4.0.1.tar.bz2 and the top level directory is called bzflag-2.4.0.1 |
| 20:43.48 | trepan | 2.4:: |
| 20:43.50 | blast007 | tupone: it wouldn't be |
| 20:43.59 | blast007 | our 'make dist' probably only uses three numbers |
| 20:43.59 | BulletCatcher | lol @trepan |
| 20:44.09 | blast007 | trepan: hehe |
| 20:44.16 | JeffM | then we should fix that, cus with 2.4 we changed the version docs |
| 20:44.28 | JeffM | I guess we wern't ready to release after all |
| 20:44.54 | BulletCatcher | We don't have a procedure to practice all of the release steps. |
| 20:45.04 | JeffM | I guess not |
| 20:45.19 | JeffM | the entire point of moving 2.1 to 3.0 was to get another number for package changes. |
| 20:45.41 | JeffM | when you didn't want 3.0 from 2.0 code we said we can do 2.4 if we used a 4th number |
| 20:45.48 | JeffM | I thought that was the date |
| 20:49.51 | blast007 | so what should I do? pull the announcement or not? |
| 20:50.13 | JeffM | why is it so hard to just fix the packages? |
| 20:50.27 | JeffM | does it require major changes to the RPM maker? |
| 20:50.39 | BulletCatcher | I recommend uploading new Windows .exe files that work, and uploading renamed source files. Nothing more. |
| 20:51.12 | JeffM | it sounds like the debian, gentoo, and rpm package systems are not ready to use 4 numbers, is that correct? |
| 20:51.26 | JeffM | the windows installers have always worked ;) |
| 20:51.32 | BulletCatcher | They are, but we didn't release 2.4.0 that way. |
| 20:52.03 | JeffM | then what is the problem with just making a package that is 2.4.0.0? |
| 20:52.14 | JeffM | just the fact that you happend to have uploaded to SF? |
| 20:52.39 | JeffM | but we can just do 3 for now and try to do 4 for 2.4.2 |
| 20:52.53 | JeffM | since it seems we are not all on the same page about it |
| 20:52.56 | JeffM | and what the needs are |
| 20:53.36 | BulletCatcher | At this point, I don't see a real advantage to complicating things by releasing 2.4.0.0 that is identical to 2.4.0 . |
| 20:53.54 | BulletCatcher | But, yeah, we should get on the same page before the next release. |
| 20:54.01 | JeffM | I know you don't see it, so we'll just hope nobody screws up a bin package |
| 20:54.12 | JeffM | so just take the date out and upload |
| 20:54.35 | BulletCatcher | The bzflag-2.4.0.1 RPM will properly supersede the bzflag-2.4.0 RPM if/when the time comes. |
| 20:55.25 | JeffM | wonders how many linux players actualy use the bins |
| 20:56.28 | BulletCatcher | blast007: go ahead and upload the renamed files, please. You probably have better bandwidth. |
| 20:56.35 | JeffM | at least on the mac we can label the .app with _x86, _ppc, and _uni |
| 20:56.47 | JeffM | cus I know we will have more then one mac package |
| 20:56.57 | JeffM | but in the end we ill only need a single |
| 20:57.21 | blast007 | BulletCatcher: in the bzflag-2.4.0.extension format? |
| 20:57.51 | JeffM | Constitution, you plan on doing 32 and 64 bit in your OSX86 .app? |
| 20:59.01 | blast007 | BulletCatcher: they're uploading now |
| 21:00.30 | blast007 | or I should say they're maybe uploading - one failed already ;) |
| 21:01.17 | JeffM | blast007, you'll need to update the links in the post too |
| 21:01.29 | blast007 | I linked to the directory, not each file |
| 21:01.34 | blast007 | oh, for the exes |
| 21:01.35 | JeffM | ok good |
| 21:01.55 | JeffM | no.. no you did the files |
| 21:01.57 | JeffM | yeah |
| 21:02.07 | JeffM | 32 bit is still uploading |
| 21:02.43 | Thumper_ | is back and reads up on the backlog |
| 21:03.55 | blast007 | links updated |
| 21:04.00 | JeffM | blast007, or BulletCatcher ether of you want to notify the mainling list? |
| 21:04.49 | blast007 | do you have to be on the list to send to it? ;) |
| 21:04.58 | JeffM | probably |
| 21:06.24 | JeffM | at some point I'd like to cleanup our SF folders too, I don't think we need a folder for each package since the packages can all just exist in the same folder |
| 21:06.31 | JeffM | even the sources |
| 21:07.03 | JeffM | just a folder for each product, then foder for each major/minor/rev |
| 21:07.38 | blast007 | renamed source is up now |
| 21:07.55 | blast007 | yeah, we should just have a "bzflag" folder |
| 21:08.29 | blast007 | then we could just link to bzflag/2.4.whatever instead of each file/directory ;) |
| 21:08.37 | JeffM | yeah |
| 21:09.06 | JeffM | also the main page sends you to the top dir and that's just confusing |
| 21:09.07 | blast007 | oh, and I think we CAN renamed the files on the site ;D |
| 21:09.13 | JeffM | how? |
| 21:09.29 | blast007 | if you hit the (i) icon on the file line, it drops down an info panel |
| 21:09.36 | blast007 | and the filename is a text field |
| 21:09.47 | JeffM | ahh |
| 21:09.55 | blast007 | doesn't look like you can MOVE files though |
| 21:10.23 | JeffM | wonder if you can from ssh |
| 21:11.09 | blast007 | not sure |
| 21:11.12 | blast007 | we could ask SF |
| 21:11.30 | blast007 | if we can move from SSH, we'd probably lose stats |
| 21:11.40 | JeffM | possibly |
| 21:11.40 | blast007 | but maybe they could use some super powers to do it |
| 21:12.19 | JeffM | or we could move off of SF :) |
| 21:12.23 | blast007 | or that :) |
| 21:12.34 | blast007 | I could finish my badass release system and use that |
| 21:12.41 | JeffM | there ya go |
| 21:12.55 | JeffM | hook it into a cheap content distro system :) |
| 21:12.59 | blast007 | tupone: is that new sourec archive what you need? |
| 21:13.00 | blast007 | yeah |
| 21:13.15 | blast007 | or even just send the files to a few of our servers via SCFTP |
| 21:13.17 | blast007 | SFTP* |
| 21:13.26 | JeffM | yeah and round robbin it |
| 21:13.46 | blast007 | be better to have each with their own domain |
| 21:13.51 | blast007 | so you could pick a specific one |
| 21:14.00 | JeffM | yeah I don't mean round robbin DNS |
| 21:14.02 | blast007 | k |
| 21:14.11 | JeffM | I mean have the site pick a random one for a link each time |
| 21:14.14 | JeffM | to spread the load |
| 21:14.15 | blast007 | yeah |
| 21:14.22 | JeffM | and maybe also show a list of mirrors |
| 21:14.55 | blast007 | geoip them and find the "closest" one ;) |
| 21:15.08 | JeffM | I'll leave that to you |
| 21:15.25 | blast007 | http://bzexcess.com/geolist/ ;) |
| 21:15.49 | blast007 | 'course, some areas don't have very good geoip info |
| 21:16.08 | JeffM | "Germany" |
| 21:16.16 | blast007 | ;) |
| 21:16.30 | JeffM | maybe germany isn't that big |
| 21:17.19 | blast007 | for people in germany, it says the german servers are 0km from them ;) |
| 21:17.26 | JeffM | nice |
| 21:17.36 | JeffM | so germany is like one city then |
| 21:17.46 | blast007 | They're in the ceiling!! |
| 21:17.56 | blast007 | pew pew pew |
| 21:18.10 | JeffM | they would NEVER shoot anyone |
| 21:18.11 | JeffM | ever |
| 21:18.40 | blast007 | that was a weak Aliens reference |
| 21:18.41 | blast007 | ;) |
| 21:19.55 | JeffM | heh, looks like I accidentaly supported IPv6 with my networking tests, dns returned a bunch of colons for "localhost" and it didn't crap out untill I tried to open a socket to that |
| 21:20.30 | blast007 | :) |
| 21:21.06 | trepan | blast007: http://bzexcess.com/geolist/ -- cool |
| 21:21.44 | blast007 | trepan: source code is linked at the bottom too |
| 21:22.09 | blast007 | (also needs mvcish, my other project) |
| 21:23.09 | trepan | my link sucks so hard that a server 100km from me would be unusable |
| 21:23.40 | blast007 | heh |
| 21:24.22 | trepan | let alone: 16607km Warrane, Australia (~110ms round trip min) |
| 21:25.44 | trepan | could add that as a column, celeritas hardfloor :) |
| 21:28.19 | *** join/#bzflag Anxuiz (~Anxuiz@50-46-121-138.evrt.wa.frontiernet.net) |
| 21:28.19 | *** join/#bzflag Anxuiz (~Anxuiz@unaffiliated/anxuiz) |
| 21:42.25 | *** join/#bzflag Think_Differentl (~Think_Dif@bzflag/player/ThinkDifferent) |
| 22:14.57 | *** join/#bzflag saxotest (~chatzilla@216.252.79.92) |
| 22:24.49 | *** join/#bzflag Pimpi (~frank@gondolin.pimpi.org) |
| 22:58.27 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7797 10/w/BZFlag_2.3: we be done son. |
| 22:59.20 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7798 10/w/BZFlag_2.0.16: no longer current release |
| 23:05.37 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7799 10/w/BZFlag_2.4: love it when a plan comes together. |
| 23:07.56 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7800 10/w/Download: 2.0.16 sucks |
| 23:08.37 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7801 10/w/Getting_Started: /* Windows */ |
| 23:09.44 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7802 10/w/Getting_Started: /* Mac OSX */ note done yet. |
| 23:11.17 | JeffM | blast007, you shoudl shadow the release announcement into News and Announcements so that it shows when you click on "News" on the main page |
| 23:11.24 | blast007 | k |
| 23:13.19 | blast007 | how would I shadow it? move it and say to leave a shadow behind? assuming that "copy topic" would make a separate copy of the topic, not a shadow |
| 23:13.30 | JeffM | yeah |
| 23:14.05 | CIA-5 | BZFlag: 03JeffM2501 07http://my.bzflag.org * r7803 10/w/Development_RoadMap: |
| 23:14.41 | blast007 | there :) |
| 23:33.48 | mdskpr | blast007: did you update motd? |
| 23:33.58 | blast007 | not yet |
| 23:35.51 | *** join/#bzflag Anxuiz (~Anxuiz@unaffiliated/anxuiz) |
| 23:38.18 | blast007 | mdskpr: now I did :) |
| 23:38.30 | blast007 | not doing the automatic update for Windows yet though |
| 23:39.00 | mdskpr | thanks :), yeah that would be better when there are more people on the 2.4 servers |
| 23:39.13 | blast007 | yep |
| 23:39.37 | blast007 | though with Windows they'd still have both versions.. but I'd rather not nag people every time they launch 2.0.x ;) |
| 23:40.47 | trepan | why not? :) |
| 23:41.26 | blast007 | :P |
| 23:43.00 | KTL | "wake the dead" lol |
| 23:56.24 | BulletCatcher | You have to dig! |