**** BEGIN LOGGING AT Fri Jul 04 02:59:58 2014 Jul 04 03:03:23 build #683 of at91 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/683 Jul 04 03:16:55 build #585 of xburst is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/585 Jul 04 03:17:47 build #691 of brcm63xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/691 Jul 04 03:44:20 build #644 of ramips is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/644 Jul 04 06:09:47 nbd r41503 branches/attitude_adjustment/package/hotplug2/Makefile * AA: hotplug2: use source hosted by OpenWrt as the original source is down Jul 04 06:25:58 nbd r41504 trunk/include/package.mk * build: temporarily disable PKG_CHECK_FORMAT_SECURITY until after the release Jul 04 06:35:01 blogic r41505 trunk/target/linux/ar71xx/patches-3.10/616-MIPS-rc32434-fix-broken-pci-init.patch * ar71xx: MIPS: RC32434: fix broken PCI resource initialization Jul 04 07:26:24 build #109 of brcm2708 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/109 Jul 04 07:38:49 <_trine> Trunk isn't compiling http://pastebin.com/seXqyZfs Jul 04 07:58:58 _trine: http://paste.debian.net/108082/ Jul 04 08:00:07 <_trine> plntyk, thanks but we need the fix applying for all Jul 04 08:00:42 <_trine> it needs committing Jul 04 08:02:12 Hello, I try to follow http://wiki.openwrt.org/doc/devel/patches, but I fail with /example/ = iodine Jul 04 08:02:27 make package/iodine/clean V=s QUILT=1 reports: No rule to make target `package/iodine/clean'. Stop. Jul 04 08:02:35 ditto for net/iodine. Jul 04 08:02:41 What am I doing wrong? Jul 04 08:04:51 is it in some feed ? Jul 04 08:05:21 make package/feeds/packages/iodine/clean V=s Jul 04 08:05:34 using clean with QUILT=1 does not make sense Jul 04 08:05:49 did you include the package.mk file in iodine Makefile ? Jul 04 08:06:32 package/iodine/clean is correct if the package name is iodine, these targets always use the package name and not the actual path Jul 04 08:07:47 _trine: thats why i have a dirty packages feeds where I fix these things instead of using the official packages feeds - sure other devs are doing similar things Jul 04 08:07:59 neoraider: both should work Jul 04 08:08:21 Oh, ok Jul 04 08:08:34 _trine: and since the last commit temporary changes the default there should be no more format-security failures now Jul 04 08:08:58 neoraider: I used the path variant for ages before I found out that I can also just use the package name ;) Jul 04 08:09:15 make package/feeds/packages/iodine/clean V=s also fails Jul 04 08:09:32 * ukleinek has "src-link packages /home/ukleinek/openwrt/src/packages" in feeds.conf Jul 04 08:09:35 is the package actually installed into your buildroot? Jul 04 08:09:42 ukleinek, is the package installed correctly using scripts/feeds ? Jul 04 08:09:43 ah thx neoraider KanjiMonster learned sth new :) Jul 04 08:09:43 ./scripts/feeds install iodine Jul 04 08:10:09 jow_laptop: \o/ Jul 04 08:10:29 * ukleinek was sure having done install -a before Jul 04 08:14:00 ukleinek: install -a only installs the present packages, so if you updated your checkout later then any new packages won't be installed until you run install -a again Jul 04 08:25:20 jogo r41506 trunk/target/linux/ brcm63xx/config-3.10 brcm63xx/config-3.14 * brcm63xx: disable AUDIT Jul 04 08:30:41 blogic r41507 trunk/target/linux/ ar71xx/patches-3.10/616-MIPS-rc32434-fix-broken-pci-init.patch rb532/patches-3.10/003-MIPS-rc32434-fix-broken-pci-init.patch * ar71xx/rb532: move rc32434-fix-broken-pci.patch to the correct target Jul 04 08:55:27 <_trine> cd .. Jul 04 09:10:59 build #324 of mpc85xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/324 Jul 04 09:43:07 build #126 of sunxi is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/126 Jul 04 09:57:15 nbd r41508 trunk/package/network/services/samba36/Makefile * samba36: do not pick up libattr as a dependency Jul 04 10:11:19 anyone know how to make chormium behave after switching form cgi luci to sgi-uhttpd luci? firefox is working after clearing cache, deleting cache in chromium and it's all still busted. Jul 04 10:29:31 build #6 of ramips.rt3883 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/6 Jul 04 10:35:56 build #5 of ar71xx.nand is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.nand/builds/5 Jul 04 10:41:36 build #5 of brcm63xx.smp is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx.smp/builds/5 Jul 04 10:43:25 is uhttpd still being developed, or is uhttpd2 designed to replace it? Jul 04 10:45:39 http://paste.fedoraproject.org/115549/14044706/ wouldn't hurt if it it's still being developed (documentation only) Jul 04 11:11:41 karlp: uhttpd is no longer being developed Jul 04 11:12:42 I see that in the commit log at least :) so is uhttpd2 meant to be a drop in for it in BB? or something else? Jul 04 11:13:26 also, would it be possible for you to put a link on http://nbd.name that takes you to gitweb? I can never remeber the url syntax into gitweb, and I have to ask google for it. Jul 04 11:14:09 i developed uhttpd2 as a replacement for uhttpd because i consider the old one broken by design Jul 04 11:14:24 i plan on eventually moving the openwrt related repos on nbd.name to git.openwrt.org Jul 04 11:15:17 added a link Jul 04 11:22:46 thanks. Jul 04 11:26:58 ah great, the google will also pickup your repos there Jul 04 11:27:11 whenever I google for ubus/ubox functions I end up in the dd-wrt repo Jul 04 11:44:58 nbd r41509 trunk/package/network/services/samba36/Makefile * samba36: disable acl support to avoid picking up a dependency on libacl (#16988) Jul 04 11:53:22 build #471 of octeon is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/471 Jul 04 12:13:41 nbd r41510 trunk/scripts/abs2rel.pl * scripts/abs2rel.pl: remove, it is unused Jul 04 12:23:36 hrm, jow_laptop any ideas why chromium would give "Failed to load resource" using luci-sgi-uhttpd, instead of the cgi? works very well in firefox, but totally fails anything ajaxy in chromium Jul 04 13:11:26 build #108 of omap is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/108 Jul 04 13:25:46 karlp: check the debug console? Jul 04 13:32:13 yeah, just says that, "Failed to load resource" Jul 04 13:32:40 web seems to indicate potentially content-type or content-length problems, but not real clear. Jul 04 13:45:00 build #5 of ar71xx.mikrotik is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.mikrotik/builds/5 Jul 04 13:54:55 karlp: what about curl? is it complaining? Jul 04 13:56:20 good idea, will look. Jul 04 13:56:43 firebug on firefox has the option to export a request as curl command Jul 04 13:56:47 useful to replay ajax requests Jul 04 13:57:39 in the network tab, right click on the request and "Copy as cURL" Jul 04 13:58:24 you could also try turning off http keepalive in /e/c/uhttpd Jul 04 14:00:48 build #5 of lantiq.xrx200 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq.xrx200/builds/5 Jul 04 14:06:19 curl: (18) transfer closed with outstanding read data remaining Jul 04 14:06:34 I guess chromium might be upset about that? Jul 04 14:06:48 very likely Jul 04 14:07:23 related to a bad content-length Jul 04 14:07:37 but since the responses are sent chunked its probably a chunk encoding problem Jul 04 14:08:50 can you get a pcap? Jul 04 14:09:32 the error above can happen if the final \r\n0\r\n\r\n is missing Jul 04 14:09:48 yeah, sure, you want want from firefox and one from chromium? Jul 04 14:09:54 yes Jul 04 14:19:04 http://palmtree.beeroclock.net/~karlp/luci-sgi-uhttpd/ Jul 04 14:19:29 (this is on AA, if that matters for uhttpd and luci) Jul 04 14:20:30 yep it matters Jul 04 14:20:36 the final chunk is encoded wrongly Jul 04 14:21:45 why doesn't it show up with luci as a cgi? I've only seen this now that i'm trying the mod-lua Jul 04 14:28:21 could be any numbero f reasons Jul 04 14:29:27 so, it this just a fixed problem in uhttpd in BB, or in the sgi in BB, or in mod-lua in BB? Jul 04 14:30:02 I'm not sure if it fixed in BB Jul 04 14:30:05 need to test there Jul 04 14:30:31 is this original AA or AA branch? Jul 04 14:30:53 AA branch Jul 04 14:31:06 ah Jul 04 14:31:10 Powered by LuCI 0.11 Branch (0.11+svn10457) Jul 04 14:31:13 AA is on uhttpd v1 still Jul 04 14:31:26 entirely different codebase Jul 04 14:32:05 ok, so I guess it's "stick with cgi" or "move to BB" then :) Jul 04 14:32:21 let me check Jul 04 14:35:57 try this: http://pastebin.com/05rSwe7E Jul 04 14:36:07 (Usr/lib/lua/luci/sgi/uhttpd.lua) Jul 04 14:36:16 and restart uhttpd after modifying the script Jul 04 14:38:32 beautiful, working fine again :) Jul 04 14:41:02 committed it to luci-0.11 Jul 04 14:41:23 don't think the error applies to AA or later since its a different web server codebase and a vastly different uhttpd.lua Jul 04 14:43:07 where did you see that in the pcaps? I did "follow tcp stream" and looked at the end of each of them, and both looked the same, or were they actually both wrong, just that firefox was accepting it? Jul 04 14:43:24 both are wrong and ff simply eats it Jul 04 14:44:08 if you do the same now after the fix you should see a "\r\n0\r\n\r\n" near the end Jul 04 14:44:20 or rather directly at the end Jul 04 14:44:56 leaving the office now. bbl Jul 04 14:45:00 thanks muchly! Jul 04 14:45:03 have a good weekend Jul 04 15:12:12 jow_laptop: hello :) saw your commits Jul 04 15:12:21 jow_laptop: what do u think about my wireless configuration? Jul 04 17:40:56 build #615 of ppc44x is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/615 Jul 04 17:41:51 build #615 of rb532 is complete: Failure [failed shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/615 Jul 04 17:44:25 build #584 of sibyte is complete: Failure [failed shell shell_9] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/584 Jul 04 18:26:33 build #655 of cobalt is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/655 Jul 04 18:30:09 build #113 of cns21xx is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/113 Jul 04 18:38:06 build #595 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/595 Jul 04 18:49:37 build #661 of orion is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/661 Jul 04 18:56:00 build #110 of pxa is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/110 Jul 04 19:13:01 build #626 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/626 **** ENDING LOGGING AT Sat Jul 05 02:59:59 2014