**** BEGIN LOGGING AT Fri May 13 23:59:56 2005 May 14 00:53:43 morning all May 14 00:54:04 Morning RP May 14 01:08:50 Luke-Jr: I really don't know why the microphone doesn't work... May 14 01:58:48 good morning all May 14 01:58:59 morning koen|away May 14 01:59:09 hey RP May 14 02:46:43 ~spitz May 14 02:46:45 well, spitz is the Sharp SL-C3000, or a dog May 14 03:00:45 hello all May 14 03:02:37 hi bluelightning May 14 03:02:43 hey RP May 14 03:27:46 hi is oe supposed to work unattended cos I got an interactive prompt today trying to check out from savannah.nongnu.org May 14 03:28:03 it timed out cos I wasn't paying attention May 14 03:28:20 struggling along with 256Mb RAM on a headless machine May 14 03:40:04 is there a mailing list for bitbakeng? May 14 03:43:16 cxm: yes: bitbake-dev@lists.berlios.de May 14 03:43:48 thanks rp. I will take a look. I am interested in the parser and the use of lua May 14 05:09:21 afternoon May 14 05:36:47 good morning boys and gals May 14 05:39:13 morning May 14 05:39:50 moin mickeyl May 14 05:39:59 i can hardly walk May 14 05:40:05 2 hours squash is too much for an old man like me May 14 06:31:07 morning mickey|newspaper, BigAl May 14 06:31:29 hey RP May 14 06:34:27 morning May 14 06:37:15 RP: still there ? May 14 06:37:23 uv1: yes May 14 06:37:30 hi zecke May 14 06:38:47 RP: Another issue with 2.6.11 from yesterday. If you have a nearly full battery and replug power, you get the opie message "battery level is very critical". Do you think thats opie, or is it the kernel ? May 14 06:39:34 uv1: I've seen that message and wondered about that myself May 14 06:39:39 unknow :-/ May 14 06:39:41 unknown May 14 06:40:00 Anyone here from opie ? May 14 06:41:41 yupp May 14 06:41:44 we aks APM May 14 06:42:12 maybe the PM chip is just slow recognizing the power plug was inserted May 14 06:42:35 and the current from the battery just dropped and the AD wondered why the current is so low.. May 14 06:43:26 zecke: How far has it to drop then ? May 14 06:43:43 I know the corgi power code better than anyone and I really have no idea if it can mess the readings up :-/ May 14 06:43:44 uv1: dunno, I don't know the Sharp device and how battery measurement is done May 14 06:44:07 zecke, RP: Any chance to do some kind of debugging ? May 14 06:44:32 uv1: from a user point perspective put a qWarning into libqpe May 14 06:44:46 uv1: and let it print whenever someone asks for the battery status May 14 06:45:06 uv1: You could enable the DPRINK statement in corgi_battery.c in the kernel May 14 06:45:30 zecke: Which module ? May 14 06:45:30 See what it does when you insert AC power and if it leaks any information May 14 06:45:48 I'd suspect a kernel problem as te corgi_battery code is full of bugs May 14 06:46:04 uv1: (userspace)library/battery.cpp May 14 06:46:09 uv1: power.cpp even May 14 06:46:15 The code is mostly sharp leftovers and needs an urgent rewrite May 14 06:46:56 uv1: line 135 onwards May 14 06:47:39 zecke: Will check the kernel stuff first. If thats OK, will test libqpe ... May 14 06:47:43 uv1: or even line 64 May 14 06:48:14 * zecke hopes libqpe doesn't use the eightball to make the pm numbers up May 14 06:49:27 uv1: now send your opie-player2 package to oe@handhelds.org ;) May 14 06:49:49 uv1: and you probably don't need PACKAGE = "${PN}" May 14 06:50:48 zecke: Should I remove the PACKAGE entry first ? May 14 06:52:54 RP: enable DEBUG or set msglevel somehow ? May 14 06:53:01 uv1: no, you do not even need to send it to oe (but in the future please do) May 14 06:53:05 uv1: Just be warned that the kernel code is extremely ugly and in need of a rewrite May 14 06:53:05 uv1: I'll push it later May 14 06:53:16 uv1: enabling DEBUG should do it May 14 06:56:41 RP: Where wil I find the info ? logread ? May 14 06:57:07 uv1: probably dmesg May 14 06:57:31 Its extrememly verbose if I remember rightly May 14 06:59:38 RP: so mic is a known problem, then? May 14 07:01:27 is booting the battery DEBUG kernel ... May 14 07:08:47 zecke: Bad news, the kernel seems to be OK. May 14 07:09:16 I doubt it ;) May 14 07:09:42 so the APM bios does not say Charging level is critical? May 14 07:10:08 what hex value does critical have, and you really don't see it? May 14 07:10:26 ;) May 14 07:10:35 Luke-Jr: Yes, I've heard people mention it before May 14 07:10:53 Luke-Jr: I don't know what the problem is... May 14 07:11:19 zecke: All I can see is the kernel printout (Volt and Percentage). This shows up every 1-2 secs. The percentage stays at 100%. May 14 07:11:51 ok but critical is not made up out of the percentage May 14 07:12:30 zecke: Where does critical come from then ? May 14 07:13:21 Can't we ask the proc fs ? May 14 07:14:11 uv1: cat /proc/apm May 14 07:15:32 zecke: "1.13 1.2 0x02 0x01 0x03 0x08 -1% -1 ?" ? May 14 07:16:11 zecke: "1.13 1.2 0x02 0x01 0x03 0x08 100% -1 ?" if disconnected. Maybe thats it ? May 14 07:17:08 RP, zecke: "1.13 1.2 0x02 0x00 0x00 0x01 100% -1 ?" if disconnected. Sorry the last went out too quick. Maybe the -1% ? In this case it is the kernel! May 14 07:18:00 uv1: look at the userspace file I've mentioned May 14 07:18:05 uv1: it explains what each value mean May 14 07:18:16 I don't have much time know, (uni stuff) May 14 07:18:49 zecke: Poor guy, thats behind me since 10 years now. Exams ? May 14 07:19:37 uv1: no thanks to the Bachelor stuff even Diploma students have to do a lot of regular excercises May 14 07:19:52 uv1: ok it is the -1 -> goes to 0 percent May 14 07:20:03 oh wait May 14 07:20:20 uv1: core/launcher/serverapp.cpp May 14 07:20:26 uv1: line 390 May 14 07:20:40 uv1: if pc < minimalPower May 14 07:20:53 uv1: you see the Critical Message you currently see May 14 07:21:25 uv1: but powerstatus is PowerStatus::Online we return... May 14 07:22:47 zecke: where is "userspace". I assume its not libqpe-opie ? May 14 07:23:00 uv1: opie/library/power.cpp May 14 07:23:07 uv1: opie/core/launcher/serverapp.cpp May 14 07:23:21 uv1: in power.cpp you see the parser for /proc/apm May 14 07:29:32 zecke: s/opie/opie-taskbar/ ? May 14 07:30:15 (someone please fix the 'holding down the right arrow key for 3 secs == turns off') May 14 07:31:44 uv1: I talk about the opie-cvs May 14 07:32:05 subdue: what device? Beagle? May 14 07:32:18 5500 collie 64-0 May 14 07:32:40 pressing the right arrow key and holding it down == it shuts itself off May 14 07:32:45 (in console) May 14 07:32:51 (actually in vi) May 14 07:34:28 consistently too May 14 07:35:23 subdue: probably no one can help you here May 14 07:35:39 np. just complaining :) May 14 07:35:53 I'm told it's a known bug May 14 07:35:57 but thanks May 14 07:36:16 subdue: never heard it before but your information is too vague to even categorize it May 14 07:37:13 I'm using a SL5500. I flashed it with collie, 64-0. When I'm in console, and using vi, if I hold down the right arrow key for 3 seconds it will shut off the 5500 May 14 07:37:18 that's basically it May 14 07:37:35 only way to turn it on at that point is to do a hard reset May 14 07:37:57 subdue: and it is still incomplete May 14 07:38:08 sorry, what info is needed? May 14 07:38:10 subdue: collie64-0 is just a kernel, I doubt it had vi built in May 14 07:38:14 RP: so mic works for you, then? May 14 07:38:55 sorry, more info won't improve the situation. we need someone diving into the kernel to look what exactly is happening here May 14 07:38:59 http://www.openzaurus.org/official/unstable/3.5.3/sl5000,sl5500/ May 14 07:39:01 the problem is known May 14 07:39:17 zecke: But I must it find in my work dir as well, right ? May 14 07:39:33 opie-image-collie-20050407173817.rootfs.jffs2 May 14 07:39:35 uv1: yes then libqpe-opie and opie-taskbar May 14 07:39:55 zImage-collie-64-0-20050407102515.bin May 14 07:39:56 mickey|newspaper: oh I've never heard it before May 14 07:40:28 Luke-Jr: I've never tried a mic with the Zaurus. I doubt it would work though May 14 07:40:28 mickey|newspaper: ok May 14 07:40:29 zecke: we seem to have that problem since a couple of releases on collie. no one really wants to thoroughly debug that since it involves 2.4.18-embedix May 14 07:40:40 mickey|newspaper: thanks May 14 07:40:42 np May 14 07:40:47 sorry i don't have better news May 14 07:41:00 but i don't think anyone of us will fix it. May 14 07:41:00 that's ok. I was worried for a moment. thought it was my Z May 14 07:41:31 Hi to all! May 14 07:43:28 I got a problem with last donwload of openembedded, is anyoune who can help me? May 14 07:43:35 mickey|newspaper: if you are finished with the newspaper, could you push the latest cfu1 sources to OE from here: http://siliconium.net/cfu1-driver.tar.gz , thanx. May 14 07:44:15 B0Ti: will do. it'll help to sometimes sync with upstream, btw. May 14 07:44:23 zecke: So it is definitely the -1%. RP where does that come from ? New kernel feature ? May 14 07:44:26 mickey|newspaper: What's there of new in the world? May 14 07:44:50 dunno yet, i need to leave the PC to actually continue reading it May 14 07:44:51 heh May 14 07:44:51 bbl May 14 07:44:57 mickey|newspaper: :) May 14 07:45:06 zecke: BTW on my SL5500, the apm message shows a drop of the percentage, if replugged to power (as you assumed before). May 14 07:45:36 mickey|newspaper: I just prepared a kernel patch against 2.6.12-rc4-mm1 available here: http://siliconium.net/sl811_cs.diff . Will mail it to linux-usb@ May 14 07:45:37 uv1: The code says: // charging now, so can not get battery percentage. May 14 07:45:37 info->battery_life = -1; May 14 07:45:54 B0Ti: ok, good. but i meant OE May 14 07:46:16 That is fair comment really so opie needs to deal with that... May 14 07:46:17 B0Ti: sometimes we make changes to improve consistency with other .bb's etc May 14 07:49:49 I dont' know if this is the right place but I report this two lines: May 14 07:49:51 | 5 out of 7 hunks FAILED -- rejects in file config.guess May 14 07:49:51 | Patch config-guess-uclibc.patch does not apply (enforce with -f) May 14 07:50:17 2 days ago all was fine... May 14 07:50:34 mickey|newspaper: I'm not sure what I could sync with from OE in this case. May 14 07:52:03 RP: oh well, We don't get confused about the -1 May 14 07:52:18 * france is back (gone 09:03:48) May 14 07:52:32 RP: we should happily ignore it if we get said that power is online May 14 07:55:16 zecke: So you're saying the kernel's "ac online" signal is lagging behind its battery_life=-1 notification? May 14 07:55:46 RP: No I'm too uneducated for it May 14 07:56:12 RP: it is either power.cpp wrong (Opie bug) or AC online is lagging May 14 07:56:36 I'd not expect the AC online to be lagging May 14 07:58:37 can somebody please send me any email? May 14 07:59:19 mithro: which address? May 14 08:13:07 Uff, "battery critical" problem while charging seems with the images from this morning. At least I cannot reproduce for testing. Sorry to bother you. May 14 08:16:40 uv1: I've also seen it before... May 14 08:31:13 Bye for today ... May 14 08:46:46 RP: I've made a couple of better patches for spitz support, one for detection and one for the base files. May 14 08:57:33 Hmm, I'm still having issues with the bitbake builds. Could someone tell me how to check out known good version of openembedded using the opensource bitkeeper client? May 14 09:08:26 I have the same problem as iw3skw, with the config-uclib.path not applying..... full details here: http://www.oesf.org/forums/index.php?showtopic=12564&view=findpost&p=79710 May 14 09:08:48 I guess I can assume it's not a configuration issue but something in the source archive itself May 14 09:08:54 ? May 14 09:09:21 I shall file a bug with the OE tracker... May 14 09:11:55 bugs.openembedded.org does not let me login as guest/guest May 14 09:16:58 http://bugs.openembedded.org/show_bug.cgi?id=2 has been created May 14 09:31:12 BigAl: Do you have a url? May 14 09:34:28 A little offtopic. Do you know if on a wireless network can coexist clients with different data rates? May 14 09:39:12 SirFred: my linksys ap at home does May 14 09:41:19 offroadgeek: Thanks. May 14 10:11:15 whee, frantic packing May 14 10:13:34 kergoth: hey ... May 14 10:13:41 hey May 14 10:13:56 * chouimat abused a little last night ... again 12 beers (pint) May 14 10:14:25 kergoth: but was fun May 14 10:14:30 9hehe May 14 10:14:58 hey kergoth May 14 10:19:03 any exciting bb/OE news? May 14 10:19:19 * RP exercises the delete key in the corgi power code May 14 10:19:25 very good May 14 10:19:28 less code, less bugs May 14 10:20:42 ~lart irssi resize bug May 14 10:20:42 * ibot slaps a compatible dib on irssi resize bug's head May 14 10:21:04 I really don't understand half of it. Some of it appears to be totally useless now, although maybe is once has a use before I last hacked at it... May 14 10:21:29 Its 1500 lines of code that should be about 300 :-/ May 14 10:23:34 Oh yuk. If we have a power problem, it doesn't re suspend the power but sits in a while loop flashing the power led because sharp were too cheap to include led flashing in hardware :-/ May 14 10:24:38 RP: it would be funny, if it weren't such a problem May 14 10:25:58 Personally, I'd prefer the device to go back to sleep. Who cares about telling the user... :) May 14 10:26:34 and all this code uses return 1 as an error.... May 14 10:26:35 LEDs are fetish items for EE people May 14 10:28:55 kergoth: Don't want to be too annoying but what about the data_delegate patch? May 14 10:29:20 kergoth: I would like to use RPs plan to get data_delegate and create copy in fast May 14 10:29:33 i would like to get everything in May 14 10:29:37 kergoth: to do a release, switch OpenEmbedded May 14 10:29:41 tag that thing as 1.2, then integrate everything May 14 10:29:49 (same for the OE tree) May 14 10:29:50 kergoth: and then do the more drastic changes May 14 10:31:00 mickeyl, zecke: Did you find the ASSUME_PROVIDED problem? May 14 10:31:05 ya, i found it May 14 10:31:10 What was it? May 14 10:31:15 it's a bug in bitbake and i wondered how that ever worked May 14 10:31:28 Another one :) May 14 10:31:29 __ignored_dependencies is written to without statement 'global' May 14 10:31:39 hence it was a function local variable May 14 10:31:48 i added a global statement May 14 10:31:54 and inserted a missing Set( ignore.split() ) May 14 10:31:58 Nice find :) May 14 10:31:59 and then it worked May 14 10:32:11 this one had already been fixed in my OO tree May 14 10:32:25 where we don't use module globals any longer May 14 10:32:29 but class variables May 14 10:32:40 i'm looking forward to patch that as soon as zecke's changes are in May 14 10:32:52 this OO refactoring is necessary for my bitbake shell May 14 10:33:07 I think we should go for the interface changes/fixes (but not the new functionality), release a bitbake/oe with them May 14 10:33:16 The look to the new functionality May 14 10:33:47 That way, we'll have a fallback release which will work with oe if any problems with zecke's new functionality is found May 14 10:34:09 RP: We can make data_delegates not too drastich May 14 10:34:22 zecke: That was the idea May 14 10:34:24 force only to use bb.data.init()... May 14 10:34:58 Just put the obvious fixes like mickeyl's find and move the deepcopy into the data class May 14 10:35:18 and forcing the use of init() May 14 10:35:53 RP: I could do a slimmed down data_delegate.patch but I could do mistakes as well ;) May 14 10:36:08 :) May 14 10:36:28 The alternative is we just throw all the patches in :) May 14 10:36:39 That'll get any bugs fixed :) May 14 10:41:24 ya May 14 10:41:27 in with it :) May 14 10:43:44 mickeyl: I don't know anything about QA May 14 10:43:50 mickeyl: but that does not sound right(tm) May 14 10:43:59 we neither May 14 10:44:03 heh May 14 10:44:18 we're too small to do branching and stuff May 14 10:44:20 imo May 14 10:44:28 zecke: My suggestion would give some kind of QA :) May 14 10:44:30 without branches May 14 10:44:47 but its needs the patch to be split carefully and someone to do the releases May 14 10:45:01 I have no idea about tagging and releasing a version of bitbake... May 14 10:45:27 RP: I'm currently doing something else (important) (besides needing uni stuff to finish) May 14 10:46:49 zecke: That's fine, I appreciate the time problem (I suffer from it myself) May 14 10:47:08 RP: but data_delegate.patch is almost bullet proof May 14 10:47:08 where can I buy some time? May 14 10:47:22 koen: at your local Cofee Shop May 14 10:47:34 zecke: heh May 14 10:48:48 Ok to summarize May 14 10:49:03 1.) Put all patches into trunk and make OpenEmbedded dependant on trunk May 14 10:49:45 2.) Put half of the patches into trunk (createCopy,keys..) do a release and make OpenEmbedded dependant on this release May 14 10:50:23 3.) split up patches even more, no data restructuring and do a release... May 14 10:50:58 kergoth please decide or raise a number 4. to n. May 14 10:51:32 * mickeyl votes for 2 and 1, in this order May 14 10:51:53 i agree with mickeyl. 2, then 1, sounds good to me May 14 10:52:28 I also say 2, then 1 May 14 10:54:18 RP: I though you were for 3.) May 14 10:55:35 zecke: Somewhere between 2 and 3 :) May 14 10:55:46 I'm happy with 2 May 14 10:56:03 It just depends how paranoid we want to be May 14 10:56:13 We don't have the time/people to be paranoid May 14 10:56:43 not about being paranoid, but I know I write perfect, bugfree code :} May 14 10:57:04 zecke: with lot's of unexpected features? May 14 10:57:16 koen: yeah but all within the spec May 14 10:57:32 i'd prefer a branch for the intrusive code to work out its kinks, but we really dont have the manpower for that May 14 10:58:35 I don't mind developing in trunk or branch May 14 11:00:10 The thing is, users are in great need of the memory patch so everyone is going to use the code branch we put it on anyway May 14 11:00:19 So we may as well do it on the trunk... May 14 11:00:27 yeah May 14 11:02:40 We can only switch OE over if we've a 'stable' release of bitbake May 14 11:03:26 yep May 14 11:04:13 I think we all agree on a direction. Can we agree a timescale? I realise kergoth has other things to do atm :-/ May 14 11:04:52 well, i'll add zecke to the project on berlios so at least i'm not a blocking issue May 14 11:04:52 heh May 14 11:05:19 kergoth: Are you ok with zecke going ahead and doing this? May 14 11:05:31 its fine with me, yeah May 14 11:05:51 kergoth: ok, get zecke added then ;-) May 14 11:06:12 zecke123 May 14 11:06:25 I even remembered my password... unbelievable May 14 11:06:47 to be frank, i'm tired of the python codebase anyway, it doesn't really interest me from a development perspective. so someone else guiding this effort makes perfect sense. May 14 11:08:42 hoefully this mess with my move is done soon May 14 11:08:51 kergoth: Perhaps this is the best way forward then... May 14 11:09:14 kergoth: we all hope things go well May 14 11:09:41 RP: i'd say the best route is mickey and zecke and whoemever else working on the incremental bitbake improvements going forward, and i'll head up the -ng efforts as a parallel effort. May 14 11:10:19 kergoth: sounds good to me. I also don't mind helping with the bitbake improvements May 14 11:10:42 Once I know a bit about bitbake, only then can I be of use to bitbake-ng :) May 14 11:10:47 * kergoth nods May 14 11:10:50 kergoth: If you've tasks for bitbake-ng just shoot May 14 11:10:59 will do. after the move May 14 11:12:01 when i left it last, the bitbake persistant metadata supplementary library was ready to roll, and the next step was laying out the api for the recipe loading modules, and writing the first one (likely bbp molded into shape) May 14 11:12:55 kergoth, did you see the patches I posted to the list? May 14 11:13:07 i havent checked my mailing list email in weeks May 14 11:13:11 its gonna take ages to get caught up May 14 11:13:13 koen: OT: do you know a dutch discount airline flying to and from germany? May 14 11:13:14 heh May 14 11:13:21 oh well May 14 11:13:39 I will just keep poking people here then May 14 11:13:56 good plan May 14 11:14:01 yeah May 14 11:14:09 zecke: I'll ask my mom on monday, she works for a German firm May 14 11:14:16 hehe May 14 11:14:18 thanks May 14 11:15:44 hmmm, it looks like my attempt at posting the rather large patch to the list went rhough May 14 11:15:57 I thought I had cancelled it when it stuck for moderatoin May 14 11:38:23 * chouimat is away: food May 14 11:42:17 Crofton: +DEPENDS = omniorb from omnievents May 14 11:42:22 Crofton: do not ommit the "" please May 14 11:42:50 ${STAGING_LIBDIR}/../usr May 14 11:42:56 looks weird May 14 11:43:28 normally we've unified diffs May 14 11:44:15 ombiorb-native, probably inherit native and do it like the other native packages May 14 11:44:24 include the original (non-native) file May 14 11:46:16 for the kernel stuff there is something like COMPATIBLE_HOST use that instead of anonymous python method May 14 11:46:31 and use ${PV} more often May 14 11:46:47 Crofton: linux-omap1_2.6.12_rc2.bb should probably be inux-omap1_2.6.12-rc2.bb May 14 12:51:49 * chouimat is back. May 14 13:06:36 evening all May 14 13:10:27 pb_: you said the evil works (autoconf) May 14 13:10:49 pb_: but yes such things could be tested with it (visibility) May 14 13:11:19 pb_: but if TARGET_FPU influences softfloat or the configuration of gcc is a matter of point of view May 14 13:12:40 zecke: softfloat is intimately bound up with the configuration of gcc; I'm not sure it makes much sense to think of them independently. May 14 13:13:08 as I said it is a matter of point of view May 14 13:13:22 with TARGET_FPU you force gcc to build softfloat May 14 13:13:37 right May 14 13:13:37 the other view gcc forces softfloat as a matter of preferred_provider May 14 13:13:46 actually it us USE = "softfloat openssl" May 14 13:14:13 and my point was to unify such things (as you proposed as well) May 14 13:14:32 I'm not sure I understand what you're saying about preferred_provider. May 14 13:15:50 pb_: sorry May 14 13:16:59 although you're right that, conceptually, you could express everything about the target system with USE, I don't really think it makes sense to do so. Toggling things like soft-float and uclibc will produce binaries that are fundamentally incompatible, which seems like a different thing to turning SSL support on and off. May 14 13:17:34 pb_: ok good argument May 14 13:17:56 or, to put it another way, openssl is something that I might legitimately want to control on a per-package basis, whereas soft-float and C library selection must match for all packages in order to have a working system. May 14 13:34:19 mickey|dinner: my framework runs, now it is time to implement the xxxx May 14 13:59:36 damn thing why wont you push May 14 15:18:21 hey. it booted. Nice. May 14 15:18:52 no space left on device to create /etc/configured. that's too bad. May 14 15:28:09 f... .. ..... ..... May 14 15:28:14 push damn you May 14 15:28:18 hmm i wonder May 14 15:28:36 isn't that what they say when they are trying to make the baby come out? May 14 15:29:17 or when your trying to still push bb changes May 14 15:33:33 weirdness. I set it for Honolulu time, but it insists on it being 10 in the morning May 14 15:34:20 I guess they must think we have dst May 14 15:34:38 kergoth: when and where is base.bbclass included? May 14 15:56:20 'night all May 14 16:00:43 cya May 14 16:02:39 damn +2000 packages are a lot May 14 16:26:36 mickey|dinner: my tool already discovered two bugs May 14 16:45:31 stupid question on BK: If I want to apply the cowbb patches to the OE classes, I need to "bk edit" to edit them (don't I?) but then, when doing bk commit, it of course asks me to allow publishing change info to openlogging. Should I do it? Because these are private changes (ie only in my repository) May 14 16:47:24 zecke: what should I do in this kind of situation? May 14 16:48:06 you don't have a big choiche ;) May 14 16:48:34 I mean what is the correct way to proceed for changes only to the local repo May 14 16:49:43 bk takepatch May 14 16:49:56 and yes if you commit it has to go to openlogging May 14 16:50:02 alternatively use the Free Client May 14 16:50:54 zecke: I don't mind it going to openlogging. All I mean is, that has nothing to do with the "official" repo, doesn't it? May 14 16:51:08 So going to openlogging doesn't mean anything in particular, right? May 14 16:54:37 marcan: everything is local until you do bk push May 14 16:55:11 OK :) May 14 17:03:39 samba binaries are crazy big. 1.7 for smbpasswd? 0.7 mb for smbcontrol? May 14 17:38:09 mickey|dinner: ping? May 14 18:19:07 good nite May 14 18:19:46 night May 14 18:46:57 03zecke 07 * r1.3290 10openembedded/packages/lirc/ (3 files): May 14 18:46:57 LIRC Kernel Modules: May 14 18:46:57 Setting TOPDIR this way will occur in a infinite loop May 14 18:46:57 when bb.data.getVar(..,d,True) (expanding). May 14 18:46:57 I don't know why TOPDIR is needed, when I found out May 14 18:46:58 something else will be done... May 14 18:46:59 03zecke 07 * r1.3289 10openembedded/conf/distro/opensimpad-0.9.0.conf: May 14 18:47:02 OpenSIMpad: May 14 18:47:04 Include OpenZaurus 3.5.4 for the 0.9.0 release ;) May 14 18:47:06 (whenever that will be) May 14 18:50:21 03zecke 07 * r1.3291 10openembedded/packages/aliens/aliens_1.0.0.bb: May 14 18:50:21 Aliens has moved the server ftp://ftp.sonic.net/pub/users/nbs/unix/agenda/aliens/src/README.txt May 14 18:50:21 update the SRC_URI to match the new location May 14 18:52:07 autofs4.1.3 is now autofs4.1.4, our version of apt does not exist either May 14 19:28:02 1;2c1;2c1;2c1;21;21;2c1;2c1;2c1;2c1;2c1;21;21;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2 May 14 19:28:09 [?1;2c[?1;2c?1;2c May 14 19:28:10 1;2c1;2c May 14 19:28:13 ?1;2c?1;2c May 14 19:28:32 yikes May 14 19:28:44 (sorry) May 14 20:33:54 <[g2]-away> Hey CosmicPenguin May 14 20:41:34 This is annoying. I really need to invest some time in learning bitkeeper better if I'm going to keep working with this project. Only I expect bitkeeper to go away Any Day Now, so I feel bad about investing time on it. May 14 20:42:13 bitkeeper probably wont be going away for at least a month May 14 20:42:20 probably more like 2 May 14 20:42:36 Hmm. Two months is long enough. May 14 20:57:19 sup treke May 14 21:23:05 Pendalar: yo May 14 21:33:39 =-) May 14 21:57:06 Hia! can anyone tell me how I would get my fb.modes file installed into the rootfs? I tried putting it into base-files/base-files/local/fb.modes May 14 21:57:32 it has to go in /etc **** ENDING LOGGING AT Sat May 14 23:59:56 2005