**** BEGIN LOGGING AT Wed Nov 19 02:59:57 2008 Nov 19 04:16:58 xMff: how do you get past the part where it still tries to checkout from lci svn? Nov 19 04:17:06 Makefile:592: *** Download/default is missing the VERSION field.. Stop. Nov 19 04:19:26 (and BTW, the CLIENT_* stuff in fon/gdata is not fixed in this tarball either) Nov 19 04:36:15 To build luci from the source tarball, you need to replace: Nov 19 04:36:15 PKG_REV:=$(shell LC_ALL=C svn info ${PKG_SOURCE_URL} | sed -ne's/^Last Changed Rev: //p') Nov 19 04:36:50 with Nov 19 04:36:50 PKG_REV:=268 Nov 19 04:36:51 in packages/luci/luci/Makefile Nov 19 04:38:00 blogic: A suggestion for the next beta release - get a third party to build the binary from the tarball *before* releasing the binary. Nov 19 04:38:34 * rwhitby laments the change in open source practices where youtube videos, blogs, and binaries all preceed the actual buildable source code release ... Nov 19 05:08:00 ok, the build now completes successfully. Nov 19 08:49:33 rwhitby: yes Nov 19 08:49:38 rwhitby: you will do it next time :) Nov 19 10:35:43 blogic: I'll be happy to Nov 19 10:38:14 blogic: So I should just be able to copy the package dirs for bluez-libs and bluez-utils from latest openwrt into the fonera dir structure and select them in menuconfig, right? Nov 19 10:38:42 yes Nov 19 10:39:44 * rwhitby resumes work on bluetooth, now that he can replicate the existing firmware Nov 19 10:41:02 hehe Nov 19 10:43:37 Hmm - I should just be able to run ./scripts/feeds install blue-libs, right? Nov 19 10:43:46 rwhitby@oils-ubuntu:/home/fon/fonera2.0-beta2-sylvester.GPL/openwrt$ ./scripts/feeds list Nov 19 10:43:46 Ignoring feed 'packages' - index missing Nov 19 10:46:06 aha - update -i -a Nov 19 10:47:47 :) Nov 19 10:48:13 Hmm - it would have been much easier if the firmware had ipkg in it ... Nov 19 10:49:09 it has opkg Nov 19 10:49:18 it should ?!? Nov 19 10:52:53 does the feeds script have a way of installing all the dependencies of a package? Nov 19 10:53:10 (e.g. dbus for bluez-utils) Nov 19 10:53:28 ./scripts/feed updat -a Nov 19 10:53:33 ./scripts/feeds update -a Nov 19 10:53:45 ./scripts/feeds install -p packages bluez-utils Nov 19 10:56:32 So fon are forking openwrt just like openmoko forked openembedded? Nov 19 10:57:07 separate svn repo, for the same packages? Nov 19 10:57:07 fon is not forking openwrt :) Nov 19 10:57:26 or are only fon-specific packages going in the fon repo, and other things (like the kernel) come direct from openwrt repo? Nov 19 10:58:01 iurgi: if it's not the same repo, it's effectively a fork, no matter how much people promise that cross-merging will happen Nov 19 10:58:01 the problem is we wanted to get rid of the svn:externals Nov 19 10:58:05 they are the pain in the ase Nov 19 10:58:06 promise? Nov 19 10:58:06 as soon as you have the same named package in two repos, then it's a fork :-( Nov 19 10:58:22 hmm Nov 19 10:58:23 I don't think it's a fork, you can call it like that Nov 19 10:58:27 but it's definitelly not something worth a ":(" Nov 19 10:59:00 or is it? Nov 19 10:59:26 well, you tell me - is there the same named package in two different repos? Nov 19 10:59:35 indeed Nov 19 10:59:39 note that I'm not using fork in the hostile sense - I'm using it in the software configuration management sense Nov 19 10:59:40 ah, sorry, you put the :-( Nov 19 10:59:40 that's why I thought it was hostile Nov 19 10:59:40 and I would call it a 'branch' ;) Nov 19 10:59:41 we used to hacve the same repo as them Nov 19 10:59:42 as you could see in previous firmware releases Nov 19 10:59:54 it's a branch if it's in the same repo :-) Nov 19 11:00:07 but, unfortunately, it was a nightmare to manage the svn: externals Nov 19 11:00:07 as I said Nov 19 11:00:17 well, I insist ;) it was in the same repo Nov 19 11:00:26 have you followed what openmoko has done? Nov 19 11:00:34 we just took a tag of openwrt because it was just a nightmare Nov 19 11:01:01 not because we're taking a different direction than openwrt Nov 19 11:01:05 they "forked" from openembedded about six months ago, and they even employed someone who's sole job it was to maintain merging between openmoko and the official openembedded repo. Nov 19 11:01:14 actually, you can see we improve nopackages on our own way, but always in consistency with openwrt Nov 19 11:01:14 that person was an experienced openembedded developer, and even on the core team of openembedded. Nov 19 11:02:11 after six months, the merging had not kept up, and it was a true fork in all senses of the word. Nov 19 11:02:45 they now have decided that they want to go back to using a branch in the openembedded repo, and they have a very big job ahead of them. Nov 19 11:02:45 well Nov 19 11:03:02 we have three people from openwrt ;) Nov 19 11:03:02 The reason why I bring it up is cause I don't want fon to make the same mistake :-) Nov 19 11:03:02 the 3 main developers, for the sake Nov 19 11:03:06 and they work mainly in openwrt stuff Nov 19 11:03:07 not just fon specific stuff Nov 19 11:03:15 if you're in a different repo, you'll spend more time "catching up" and "merging" with the official openwrt repo, and less time making fon fantastic! Nov 19 11:03:24 in our minds (blogic, kaloz, nbd, iurgi and the rest of fon), fon is just a plugin over openwrt Nov 19 11:03:24 and it will keep like that Nov 19 11:03:30 we don't modify openwrt stuff in our repo Nov 19 11:03:30 excellent - if it stays like that there is no problem Nov 19 11:03:33 only fon stuff Nov 19 11:04:13 but if there are more than a few packages that have the same name in both repos, that's the sign of a fork rather than a plugin. Nov 19 11:04:13 actually, you can see that fon is set up as a "feed" in our repo as well Nov 19 11:04:38 wait Nov 19 11:04:50 yeah, it's the openwrt set of packages that I worry about, and divergence in them Nov 19 11:04:51 we only modify the packages that need modification for fon to work Nov 19 11:04:55 the rest, is if it's an improvement also for openwrt, it's merged into openwrt as well Nov 19 11:04:55 since you have 3 openwrt developers, it should be no problem to make sure that the official openwrt repo has packages that work perfectly for fon's requirements ... Nov 19 11:05:06 we are not forking Nov 19 11:05:16 we simply provide an aternate packages feed Nov 19 11:05:23 that has the lua stuff added Nov 19 11:05:31 blogic: that feeds script command didn't bring in the dependencies (dbus, expat) of bluez-utils Nov 19 11:05:44 blogic: ok, so the fon svn will not contain any packages that are in the openwrt svn? Nov 19 11:05:46 when 809 is done and our packages feed is done, it will be a simple entry in the feeds.conf Nov 19 11:06:02 we will have a install script Nov 19 11:06:13 (or very few for very temporary periods) Nov 19 11:06:38 atm we will tag 809, as nbd still needs to add the option for use to use a different madwifi and basefiles Nov 19 11:07:20 as soon as nbd added the feature, we will provide a mirror of 809 Nov 19 11:07:24 and a feed Nov 19 11:07:24 if it is the case that fon svn contents and openwrt svn contents are designed to be disjoint and non-overlapping, then I withdraw my concern and replace it with "good plan"! Nov 19 11:07:37 yes, thx :) Nov 19 11:07:50 ok, so any overlap is temporary startup transient Nov 19 11:09:21 blogic: did you have any luck with the fsg3? Nov 19 11:10:52 if you can get the switch in it to be able to use all four ports as a lan, then I'll be happy to switch mine over to openwrt/fon and help debug it :-) Nov 19 11:12:04 rwhitby ok Nov 19 11:12:13 overlap is startup Nov 19 11:14:25 rwhitby: whats the deal with the switch ? Nov 19 11:14:30 is it working at all ? Nov 19 11:16:29 it's one of those 4 port jobs where one port is wan and three are lan Nov 19 11:17:03 It's currently running Debian, and the three ports are running as lan, but I dunno how to switch the fourth to lan Nov 19 11:17:09 Hmm - dbus fails to build :-( Nov 19 11:18:27 ok, i will look into the fourth port Nov 19 11:20:23 rwhitby: bummer Nov 19 11:28:26 blogic: \o/ Nov 19 11:34:31 blogic: neither opkg or ipkg are in the firmware on my fon2 Nov 19 11:35:06 (and it's not built by default in the source tarball config) Nov 19 11:37:40 rwhitby: beta2 has it Nov 19 11:37:45 sylvester Nov 19 11:37:45 do you have that installed in your box? Nov 19 11:38:11 hmm - i see balloons on boot :-) Nov 19 11:38:32 then you don't Nov 19 11:38:41 yeah, I need to reflash :-) Nov 19 11:38:41 we only included opkg since sylvester Nov 19 11:39:14 yup Nov 19 11:40:17 in that case, I might as well flash the image I just built from source :-) Nov 19 11:40:41 I assume bin/openwrt-fonera.image is suitable for mtd write? Nov 19 11:41:48 should be Nov 19 11:42:10 mtd -r write image_name image Nov 19 11:42:11 I mean, the partition you need to flash on is "image" Nov 19 11:42:11 ;) Nov 19 11:42:11 much faster than using redboot and serial :-) Nov 19 11:42:12 yeah, I've used mtd write lots of times on this device :-) Nov 19 11:42:43 ah, ok Nov 19 11:42:43 :) Nov 19 13:01:32 Hi Nov 19 13:02:37 speak anybody german? Nov 19 13:02:41 ja Nov 19 13:03:19 ich habe ein problem undzwar ich habe die La Fonera 2.0 Nov 19 13:03:31 als Router mit PPPOE Nov 19 13:04:15 wenn ich per SSH vom LaFonera google anpinge funktioniert es wenn ich mich allerdings mit einen PC per Wlan oder Ethernet verbinde bekomme ich keinen Ping hin geschweige die Seite öffnet sich Nov 19 13:04:25 ? Nov 19 13:04:29 welche firmware ? Nov 19 13:04:55 bzw am anfang ging es Nov 19 13:05:11 dan hatte ich auf 2.1.0.2 nen upgrade gemacht und dann ging es nicht mehr Nov 19 13:05:34 ok Nov 19 13:05:40 ich schaue es mir gleich mal an Nov 19 13:05:58 also hab ich wieder 2.1.0.1 drauf gemacht und funktioniert trotzdem nicht Nov 19 13:06:55 so ist die für meine zwecke recht sinnlos Nov 19 13:07:04 ? Nov 19 13:07:12 geht auch mit 2.1.0.1 nicht ? Nov 19 13:07:13 wenn kein inet geht :) Nov 19 13:07:16 nein Nov 19 13:07:25 hmm Nov 19 13:07:30 ich probiere es gleich mal Nov 19 13:07:40 ok danke Nov 19 13:08:49 steht schon fest wann eine neue firmeware rauskommt? Nov 19 13:09:17 bald Nov 19 13:09:34 bekommst du die splash seite, ala "inet ist kaputt" Nov 19 13:10:01 ;-) Nov 19 13:11:11 manchmal Nov 19 13:15:07 manchmal ? Nov 19 13:15:12 sollte immer gehen Nov 19 13:15:15 ermm Nov 19 13:15:23 komisches dns setup aufm pc ? Nov 19 13:15:48 kannst du mal probieren das zu starten und wenn es nich t geht auf dem client pc ein ping 194.25.2.129 machen ? Nov 19 13:17:10 hab einmal kurz das internet gewechselt so kann ich nun auch mal direkt testen Nov 19 13:18:15 wenn du also was vom router brauchst sag bescheit kann dir per SSH alles raussuchen Nov 19 13:21:07 blogic: is http://downloads.openwrt.org/snapshots/fonera/ expected to exist? Nov 19 13:22:39 rwhitby: probably Nov 19 13:22:42 bbl Nov 19 13:25:11 Lazybone: mal das mit dem ping probiert ? Nov 19 13:25:27 also pc->fon->dsl->inet Nov 19 13:25:33 dann aufm pc ping 194.25.2.129 Nov 19 13:26:10 mom probier ich mal eben ich muss kurz die lafonera anschließen Nov 19 13:26:16 ok Nov 19 13:26:24 ich bestelle mir ne pizza Nov 19 13:26:40 ;-) Nov 19 13:32:53 jetzt muss ich nur hinbekommen das lafonera auch wieder inet hat Nov 19 13:33:14 was muss ich nochmal bei mtu eintragen Nov 19 13:38:55 also Nov 19 13:39:14 ping von LaFonera(SSH) zu 194.25.2.129 funktioniert Nov 19 13:39:14 ping von PC zu 194.25.2.129 funktioniert nicht Nov 19 13:45:06 blogic noch da? Nov 19 13:51:05 ja Nov 19 13:51:10 der pc hat ein dns ? Nov 19 13:51:14 jup Nov 19 13:51:15 also dhcp geht ? Nov 19 13:51:17 192.168.10.1 Nov 19 13:51:25 den fon kannst du pingen Nov 19 13:51:28 .1 ? Nov 19 13:51:32 ah ja Nov 19 13:51:33 ok Nov 19 13:51:41 ich schaue gleich nach Nov 19 13:51:41 jap komme auch aufs webinterface Nov 19 13:51:55 dann wird das ppp device nicht in der firewall eingetragen Nov 19 13:51:58 warum auch immer Nov 19 13:52:51 hmm wie mach ich das manuell? Nov 19 13:54:34 hmm Nov 19 13:54:42 nicht so ganz trivial Nov 19 13:54:53 ich glaube es ist ein bug in openwrt Nov 19 13:55:04 da war letzte woche ein commit zu dem thema Nov 19 13:55:09 ich schaue mal Nov 19 13:56:39 ok Nov 19 19:34:35 nabend Nov 19 19:44:01 hi there Nov 19 19:46:14 hi kazwo Nov 19 20:14:42 hi Nov 19 20:37:13 hello inouk Nov 19 21:35:48 hi **** ENDING LOGGING AT Thu Nov 20 02:59:56 2008