00:45.41 | *** join/#pet BZFlag (~timr@proxyle01.ext.ti.com) |
00:46.21 | *** mode/#pet [+o BZFlag] by ChanServ |
03:23.19 | *** join/#pet TimRiker (~timr@proxyle01.ext.ti.com) |
03:23.39 | *** mode/#pet [+o TimRiker] by ChanServ |
03:29.35 | *** part/#pet ReleaseBZFlag (~timr@proxyle01.ext.ti.com) |
13:42.05 | *** join/#pet a-atwood_windows (~XF009976@proxyle02.ext.ti.com) |
13:43.22 | *** join/#pet bmw_3 (~xf013426@proxyle01.ext.ti.com) |
13:49.20 | *** join/#pet a-atwood (~xf009976@proxyle01.ext.ti.com) |
14:35.39 | Neo|Work | yay, have thunderbird up and running and configured correctly |
14:48.16 | *** join/#pet dez (~dez@proxyle02.ext.ti.com) |
15:59.11 | a-atwood | marvelous. checkin of ~ 2.7GB of code goes from < 90 min with the old harvest to 102 min with the new patch |
15:59.50 | a-atwood | er, not code. backupfiles. stuff already tarred. |
16:09.50 | dez | How many tumbles could a tumbleweed weed if a tumbleweed could weed tumbles? |
17:16.57 | *** join/#pet bryanw (~xf012502@proxyle02.ext.ti.com) |
17:21.49 | *** join/#pet richardw (~richardw@proxyle01.ext.ti.com) |
17:34.35 | *** join/#pet TimRiker (~timr@proxyle02.ext.ti.com) |
17:34.35 | *** mode/#pet [+o TimRiker] by ChanServ |
18:08.15 | TimRiker | ~gpl |
18:08.17 | | i guess gpl is an awful and terrible license. you know stallman wants to do away with the LGPL entirely also |
18:08.22 | TimRiker | ~lgpl |
18:08.41 | TimRiker | hmm... /me was looking for a gnu.org or fsf.org url. |
18:27.43 | TimRiker | ~lgpl is the Lesser General Public License, see http://www.gnu.org/copyleft/lesser.txt or http://www.fsf.org/licenses/lgpl.txt |
18:27.44 | | TimRiker: okay |
18:27.50 | TimRiker | both of which seem to be down |
20:04.42 | *** join/#pet bmw_3 (~xf013426@proxyle02.ext.ti.com) |
20:16.28 | dez | bmw_3: the 12:30pm build is only 1.5MB instead of 20.5MB. |
20:17.01 | bmw_3 | dez: starting research now... |
20:17.19 | TimRiker | ooh. nice compression. ;-) |
20:17.32 | bmw_3 | we aim to please ;) |
20:19.24 | dez | bmw_3: fyi, you may wish to link "latest.tar.bz2" to the latest build after it's been verified rather than beforehand. |
20:31.15 | *** join/#pet kergoth (kergoth@zelda.tuxnami.org) |
20:31.15 | *** mode/#pet [+o kergoth] by ChanServ |
20:31.26 | bmw_3 | dez: only the tar was messed up, the build was fine. You want a full rebuild or just a retar? |
20:36.07 | bmw_3 | Never mind, I am re-running the build just to make sure... |
20:37.38 | dez | bmw_3: I only brought this up because a CUPDD wanted to update his Linux machine with the newest tiapps build, and it didn't work. |
20:38.09 | dez | bmw_3: How ever you get it to work is fine by me. |
20:39.04 | *** join/#pet a-atwood (~xf009976@proxyle02.ext.ti.com) |
20:40.07 | bmw_3 | dez: The way latest... gets updated is during the build process. My understanding is that it truely means "latest," not "latest reasonable" or "latest good." If they want something that is known to work, they/we should modify the process so they can pull one that has been verified. Thoughts? |
21:32.56 | TimRiker | kergoth: list of components? please? |
21:34.51 | kergoth | oh, right, k |
22:18.00 | *** join/#pet kergoth (kergoth@zelda.tuxnami.org) [NETSPLIT VICTIM] |
22:18.00 | *** join/#pet TimRiker (~timr@proxyle02.ext.ti.com) |
22:18.00 | *** join/#pet ChanServ (ChanServ@services.) |
22:18.01 | *** join/#pet Neo|Work (~neotron@proxyle02.ext.ti.com) [NETSPLIT VICTIM] |
22:18.01 | *** join/#pet mindfunk (~mindfunk@adsl-216-61-82-82.dsl.rcsntx.swbell.net) [NETSPLIT VICTIM] |
22:18.01 | *** mode/#pet [+oooo kergoth TimRiker ChanServ mindfunk] by tolkien.freenode.net |
22:20.05 | Neo|Work | QWSServer::mouseHandler()->calibrate(&m_goodCalData); |
22:20.05 | Neo|Work | <PROTECTED> |
22:20.05 | Neo|Work | nice |
22:20.36 | kergoth | heh, that cant be good |
22:29.12 | Neo|Work | so time to debug the calibration method |
22:32.29 | Neo|Work | wait a second, it's your code. :P |
22:33.46 | kergoth | heh, its technically theirs. i didnt modify the bits to take your coords and stuff them into pointercal |
22:33.49 | Neo|Work | why did you override it? |
22:34.01 | kergoth | remember, we arent a qcalibratedmousehandler |
22:34.02 | Neo|Work | is it at all different? |
22:34.05 | Neo|Work | we aren't? |
22:34.09 | Neo|Work | oh |
22:34.11 | Neo|Work | ok |
22:34.13 | Neo|Work | never mind :-) |
22:34.17 | kergoth | iirc we arent, so yes we need those methods |
22:34.18 | kergoth | heh |
22:34.31 | Neo|Work | I can't see how this could cause an abort |
22:36.32 | Neo|Work | stat64("/etc/pointercal", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 |
22:36.32 | Neo|Work | open("/etc/pointercal", O_RDONLY) = 20 |
22:36.32 | Neo|Work | read(20, "", 200) = 0 |
22:36.32 | Neo|Work | --- SIGSEGV (Segmentation fault) --- |
22:36.38 | Neo|Work | that's in tslib I believe |
22:36.51 | Neo|Work | 8293 0 -1351120 0 -5885 22604775 65536 |
22:36.56 | Neo|Work | that's /etc/pointercal |
22:37.32 | Neo|Work | so openTS dies |
22:45.33 | Neo|Work | aha |
22:46.18 | Neo|Work | bug in tslib |
22:46.29 | Neo|Work | triggered by bug in qwsmouse |
22:47.31 | Neo|Work | QFile foo(..); .. write to file; closets /opents |
22:47.38 | Neo|Work | => /etc/pointercal is empty |
22:47.43 | Neo|Work | this causes tslib to crash |
22:47.50 | Neo|Work | flush it and voila, works |
22:48.53 | kergoth | ahh |
22:48.54 | kergoth | nice |
22:54.19 | Neo|Work | Cannot access the Hardware Clock via any known method. |
22:54.19 | Neo|Work | Use the --debug option to see the details of our search for an access method. |
22:54.20 | Neo|Work | hrm |
22:58.22 | Neo|Work | root@156.117.109.203:/device.arm# /sbin/hwclock |
22:58.22 | Neo|Work | Cannot access the Hardware Clock via any known method. |
22:58.22 | Neo|Work | Use the --debug option to see the details of our search for an access method. |
22:58.29 | Neo|Work | ok, so it's hwclock that has the issue |
22:59.31 | Neo|Work | open("/dev/rtc", O_RDONLY|O_LARGEFILE) = 104044 |
22:59.31 | Neo|Work | pid 228 stray syscall exit |
22:59.31 | Neo|Work | ) = 104044 |
22:59.31 | Neo|Work | pid 228 stray syscall exit |
22:59.31 | Neo|Work | ) = -1 ENODEV (No such device) |
22:59.42 | kergoth | what methodology does that qtopia use for managing the alarms.. atd? |
23:00.15 | Neo|Work | dunno. we have no alarms. :P |
23:00.21 | kergoth | hehe |
23:00.53 | Neo|Work | but yes, it uses atd |
23:08.49 | Neo|Work | kergoth: know who I should bug about hardware clock? |
23:09.01 | Neo|Work | or lack of /dev/rtc or whatever the issue is |
23:09.08 | kergoth | dunno off the top of my head |
23:09.24 | Neo|Work | wonder if I'm just missing the module for it |
23:57.34 | *** join/#pet a-atwood (~xf009976@proxyle02.ext.ti.com) |