**** BEGIN LOGGING AT Tue Jun 03 02:59:58 2014 Jun 03 05:51:10 blogic r40992 trunk/package/kernel/linux/modules/usb.mk * kernel: fix kernel build for chipidea w/o usb-gadget Jun 03 06:54:22 blogic r40993 trunk/package/base-files/files/etc/rc.button/power * base-files: /etc/rc.button/power should be executable Jun 03 11:32:10 package maintainers, please read: https://lists.openwrt.org/pipermail/openwrt-devel/2014-June/025810.html Jun 03 11:38:04 any idea of the buildbot time improvements from not building packages/? Jun 03 11:39:21 cyrusff: will the upcoming BB then be based on what's in that new feed? Jun 03 11:39:38 probably yes, depends on how much we can get moved Jun 03 11:40:15 ok, will try and get my existing packages into pulls then. Jun 03 11:40:29 how close is BB? weeks or months? Jun 03 11:40:47 we were thinking about maybe building the "old" packages feed as well but in a different opkg repository so you have to manually uncomment it Jun 03 11:41:09 thanks to swalker's nice tool its easy to spot the horrible state of some of the packages there Jun 03 11:41:17 e.g. don't look at those CVE's to closely Jun 03 11:42:11 karlp: well a release needs much testing Jun 03 11:42:20 swalker: not sure actually on the impact Jun 03 11:42:33 we will see how it turns out Jun 03 11:42:59 just hoping to get a "real soon now" version of a package in :) Jun 03 11:43:19 he btw. Jun 03 11:43:26 do you have commit access to packages? Jun 03 11:43:41 i don't have the list here ;) Jun 03 11:43:45 no, I'd _like_ to have access to mosquitto at least Jun 03 11:44:06 I've sent requests for access a couple of times in the past, but it always seems to fall through the cracks somewhere Jun 03 11:45:16 we maintain a tree here: https://github.com/remakeelectric/owrt_pub_feeds and the "more important" packages I have been sending to openwrt-devel for inclusion once they're tested out and tidied up Jun 03 11:45:58 ok, well yeah i admit we were a bit bureaucratic with packaged access Jun 03 11:46:10 it generally all worked out in the end :) Jun 03 11:46:19 he Jun 03 11:46:42 well i see that you already submitted some patches and at least 18 of them got merged Jun 03 11:47:29 where will luci-apps go in this? I'd in the past tried sending them to trac, but I never saw any of them go in. I've always kept the luci support separate from the uci support and application packaging Jun 03 11:47:44 luci stays in its own feed Jun 03 11:48:25 sounds like it's heading towards EOL anyway, from the progress being made on luci2 Jun 03 11:48:36 yeah Jun 03 11:49:19 if you like tell me your github handle if you have one and i will see what i can do about feed access ;) Jun 03 11:49:45 karlp Jun 03 11:49:49 that was easy ;) Jun 03 11:50:11 ok will get back to you later Jun 03 11:50:45 no rush, I'll send a couple of pulls with the packages I've been looking after, hopefully later today Jun 03 11:52:38 so, one question then, the README in the new repo says PKG_MAINTAINER Jun 03 11:53:03 but the existing packages often have a MAINTAINER field in the Packge/ section, not a top level PKG_xxx variable? Jun 03 11:53:43 that is fine Jun 03 11:53:44 do you want both or only one or the other going forward? Jun 03 11:53:58 i'll change the readme Jun 03 12:00:52 I've updated the "creating packages" page a little on the wiki too Jun 03 12:01:01 ok thanks Jun 03 13:17:32 cyrozap, oh my gosh! You are moving stuff to github =) ! Jun 03 13:18:07 cyrusff, ^ Jun 03 13:33:37 txomon|fon: there's been openwrt mirrors on github for ages Jun 03 13:33:50 but they don't take pulls there for the main repo :) Jun 03 13:36:16 txomon|fon: we are only moving all the non-core packages to github (so all the unmaintained crap), the base system stays with svn Jun 03 13:36:54 unmaintained crap and externally maintained packages Jun 03 13:36:57 jow_laptop: arrow.gif doesn't seem to be used anymore? would you like a cascade.css entry that lets you put the arrow on a text button? or should we just remove the .gif altogether? Jun 03 13:41:58 one interesting feature would be to provide package usage statistics =) Jun 03 13:42:07 all the systems have them Jun 03 13:42:53 that way you would know which packages are relevant to be maintained =) Jun 03 13:44:17 not everyone opts into popcon Jun 03 13:44:31 and that would completely miss the point when you build packages into images Jun 03 13:44:48 it's not the same as apt-get/yum knowing how many things are installed and so on. Jun 03 13:45:09 karlp, well, you don't really need to do usage statistics Jun 03 13:45:25 you can just have a ping to a usage server there Jun 03 13:45:44 so that each time compilations occur, you know it has used those packages Jun 03 13:45:53 and you have at least some measure Jun 03 13:46:14 a usual wget request would be enought Jun 03 13:46:58 you filter usage by IP, and there you know how many different people have been working with those packages Jun 03 13:47:58 karlp: let me check Jun 03 13:48:35 ah indeed Jun 03 13:48:49 I guess we can drop it Jun 03 13:51:13 (I naively tried using "cbi-input-arrow" and it didn't work ;) Jun 03 13:51:38 txomon|fon: counting IPs as people/users has been disproven even in the courts :) Jun 03 13:51:53 also, less spying on people please :) Jun 03 14:01:01 nbd r40994 trunk/package/kernel/mac80211/patches/603-rt2x00-introduce-rt2x00eeprom.patch * mac80211: refresh patch Jun 03 14:01:18 nbd r40995 trunk/package/kernel/mac80211/patches/300-pending_work.patch * mac80211: backport a powersave related fix Jun 03 14:06:08 hi all! Jun 03 14:06:38 nbd did you had time to review de V2 patch about 802.1ad vlan ? Jun 03 16:25:20 karlp, you can do it voluntary Jun 03 17:32:33 can anyone tell me how to generate a uboot flagged filesystem? Jun 03 17:32:38 the output should be output/images/rootfs.cpio.uboot: u-boot legacy uImage, , Linux/ARM, RAMDisk Image (Not compressed), 937029 bytes, Sun Jun 1 15:29:07 2014, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x26F8BC81, Data CRC: 0x13935EC8 Jun 03 17:33:04 I can't find it in the rootfs options Jun 03 17:39:30 you mean a uImage? Jun 03 17:40:01 <5EXAA8SU8> build #584 of rb532 is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/584 Jun 03 17:40:45 <5EXAA8SU8> build #553 of sibyte is complete: Failure [failed shell shell_10 shell_15] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/553 Jun 03 17:40:49 <5EXAA8SU8> build #584 of ppc44x is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/584 Jun 03 17:41:07 <5EXAA8SU8> build #640 of brcm47xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/640 Jun 03 17:42:59 <5EXAA8SU8> build #491 of iop32x is complete: Failure [failed shell_10 shell_15] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/491 Jun 03 17:44:33 <5EXAA8SU8> build #490 of ep93xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/490 Jun 03 17:44:56 <5EXAA8SU8> build #173 of mvebu is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/173 Jun 03 17:45:37 <5EXAA8SU8> build #294 of mpc85xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/294 Jun 03 17:46:00 <5EXAA8SU8> build #479 of mcs814x is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/479 Jun 03 17:46:41 <5EXAA8SU8> build #483 of adm5120 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/483 Jun 03 17:47:04 <5EXAA8SU8> build #462 of mpc52xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/462 Jun 03 17:47:45 <5EXAA8SU8> build #96 of sunxi is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/sunxi/builds/96 Jun 03 17:48:10 <5EXAA8SU8> build #441 of octeon is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/441 Jun 03 17:48:49 <5EXAA8SU8> build #79 of pxa is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/79 Jun 03 17:49:14 <5EXAA8SU8> build #82 of cns21xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/82 Jun 03 17:49:53 <5EXAA8SU8> build #80 of mpc83xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/80 Jun 03 17:50:18 <5EXAA8SU8> build #81 of bcm53xx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/81 Jun 03 17:50:57 <5EXAA8SU8> build #79 of brcm2708 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/79 Jun 03 17:51:23 <5EXAA8SU8> build #81 of realview is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/realview/builds/81 Jun 03 17:52:02 <5EXAA8SU8> build #78 of omap is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/78 Jun 03 17:52:28 <5EXAA8SU8> build #79 of adm8668 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/79 Jun 03 17:53:07 <5EXAA8SU8> build #79 of malta is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/malta/builds/79 Jun 03 17:53:34 <5EXAA8SU8> build #79 of cns3xxx is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/79 Jun 03 17:54:12 <5EXAA8SU8> build #80 of x86_64 is complete: Failure [failed svn compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/x86_64/builds/80 Jun 03 18:38:06 <5EXAA8SU8> build #519 of au1000 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/519 Jun 03 19:02:55 <5EXAA8SU8> build #624 of cobalt is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/624 Jun 03 19:05:14 <5EXAA8SU8> build #630 of orion is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/630 Jun 03 19:10:43 <5EXAA8SU8> build #595 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/595 Jun 03 19:18:07 <5EXAA8SU8> build #660 of brcm63xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/660 Jun 03 19:29:15 <5EXAA8SU8> build #190 of imx6 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/190 Jun 03 19:32:36 wtf Jun 03 19:40:53 heffer Jun 03 19:40:55 no, I need the rootfs Jun 03 19:41:54 anyone can tell me how to get the rootfs marked that way? Jun 03 19:42:04 output/images/rootfs.cpio.uboot: u-boot legacy uImage, , Linux/ARM, RAMDisk Image (Not compressed), 937029 bytes, Sun Jun 1 15:29:07 2014, Load Address: 0x00000000, Entry Point: 0x00000000, Header CRC: 0x26F8BC81, Data CRC: 0x13935EC8 Jun 03 19:42:11 that doesn't make sense. the rootfs usually isn't in uimage format Jun 03 19:42:31 no, it's the rootfs marked with uboot Jun 03 19:42:33 that looks like initramfs uimage Jun 03 19:42:55 http://www.wiki.xilinx.com/Build+and+Modify+a+Rootfs Jun 03 19:48:30 Hauke: hellow Jun 03 19:48:57 Hauke: just wanted to give u some explanation about brcm47xx Jun 03 19:49:19 as you noticed, there is b43 dependency (on bcma/ssb), that has to be handled carefully Jun 03 19:49:37 Hauke: so for now I re-sumitted (without RFC this time) only the first sugtarget-related patch Jun 03 19:49:58 Hauke: i'll work on the rest, once you or nbd push my mac80211: b43: patches Jun 03 19:50:08 Hauke: but I still plan to work on subtargets for brcm47xx Jun 03 19:50:41 Hauke: and I hope my last patch (2nd one in the RFC patchset) shows my plan in a pretty clear way Jun 03 19:51:00 Hauke: so I hope this first brcm47xx patch (adding "generic" subtarget) can be accepted Jun 03 19:51:17 just wanted you to know why I dropped second patch for now Jun 03 19:52:01 heffer, ^ ( http://www.wiki.xilinx.com/Build+and+Modify+a+Rootfs ) Jun 03 19:52:59 txomon|home: yeah, looks like what you are trying to do. adding the uboot header seems to be the last step in that guide Jun 03 19:53:08 yep Jun 03 19:53:17 so, any idea on how to do that in openwrt? Jun 03 19:53:55 the mkimage command should be available in the host tools section of the build system Jun 03 19:54:19 so basically you should be able to use it as shown in the guide Jun 03 19:54:27 so you say to do a package that does that Jun 03 19:54:44 or should I put that as an extra in the target/*/image/Makefile ? Jun 03 19:55:02 moreover, where do I take the rootfs from? Jun 03 19:55:23 because I have seen how to generate the kernel and the u-boot, but have no idea where the rootfs is generated.. Jun 03 19:55:24 what is it that you are trying to achieve? Jun 03 19:56:29 to generate a running image for the zedboard Jun 03 19:56:37 I have achieved everything but that last part Jun 03 19:56:39 the rootfs Jun 03 19:56:57 You can fetch sources on github.com/txomon/openwrt -> integration/xilinx Jun 03 19:57:06 integration/xilinx-zynq Jun 03 19:58:03 i'll have a look Jun 03 19:59:56 I have just today the card here in my hands, so if you/we achieve something, I can test it =) Jun 03 20:04:06 ah i guess i know what your problem is Jun 03 20:05:12 zedboard does not have flash so you need to have all the stuff in a initramfs image Jun 03 20:06:29 in the build config that can be achieved by enabling Target Images -> ramdisk Jun 03 20:06:53 I'm encountering a build error on trunk (just syncd up from being a couple of months out of date): cp: cannot overwrite non-directory '/usr/src/openwrt/gw-trunk-bump/trunk/staging_dir/target-arm_cortex-a9+neon_uClibc-0.9.33.2_eabi/host/bin' with directory '/usr/src/openwrt/gw-trunk-bump/trunk/tmp/stage-uclibc++/host/bin' Jun 03 20:06:57 note that you need to have that implemented in your image makefile as well. you can look how it's done in the other target's makefile Jun 03 20:07:09 tharvey: make dirclean Jun 03 20:07:22 heffer, oki Jun 03 20:07:25 it was clean Jun 03 20:07:27 but I have that Jun 03 20:07:32 tharvey: if your tree is months out of sync i'm afraid you can't go without dirclean Jun 03 20:07:45 ohhh ok Jun 03 20:07:49 I was in a clean dir Jun 03 20:07:56 so I have the ramdisk part missing in the image ? Jun 03 20:08:01 image/Makefile* Jun 03 20:08:05 txomon|home: i guess so Jun 03 20:08:30 staging_dir/target-arm_cortex-a9+neon_uClibc-0.9.33.2_eabi/host/bin appears to be libusb-config so it looks like libusb-config is trying to install to staging before there is a dir Jun 03 20:09:04 heffer: my point is, I don't know when the issue started occuring as I haven't built trunk in a couple of months Jun 03 20:10:50 heffer, so I don't need anything in the "Target Images" but the ramdisk? Jun 03 20:11:34 txomon|home: yes that should be correct Jun 03 20:12:24 tharvey: so you started off with a freshly cloned openwrt tree and it threw that error? Jun 03 20:13:37 heffer: yes... clean directory Jun 03 20:15:11 package libusb-compat Build/InstallDev is running before staging/.../host/bin dir is created Jun 03 20:15:47 Build/InstallDev should always be doing a mkdir before CP correct? Jun 03 20:16:31 then it might well be a bug in the package Jun 03 20:17:01 ya... libusb-compat Build/InstallDev needs a $(INSTALL_DIR) $(1)/bin Jun 03 20:17:04 I'll post a patch Jun 03 20:18:53 thanks Jun 03 20:20:55 http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=1e9ae4ea5212588094928995c9f727ffdc61cd3c was the breakage Jun 03 20:21:57 heffer, ramdisk != initramfs Jun 03 20:21:58 ? Jun 03 20:23:28 zajec: hi Jun 03 20:23:38 yes nice patches and thanks for the info Jun 03 20:24:36 Hauke: i'm going to add B43_PHY_G (have it locally), but John stopped merging patches for now (merge window) Jun 03 20:24:42 so this will have to wait a bit Jun 03 20:25:59 i also hoped to get 5 GHz for 3.16 :( Jun 03 20:26:08 that doesn't really hurt OpenWrt release ofc Jun 03 20:26:09 just saying Jun 03 20:26:27 that sounds nice Jun 03 20:26:58 txomon|home: initramfs is a type of ramdisk Jun 03 20:27:55 txomon|home: it's a ramdisk that can be used by the init system to boot a linux system using the ramdisk as rootfs Jun 03 20:30:10 heffer, so I want that Jun 03 20:30:18 yes Jun 03 20:30:19 well, I really don't need it Jun 03 20:30:28 I can flash the sd card with the file system Jun 03 20:31:10 but, then, how may I choose to give the user the option to dd a .img to a partition, or to copy the initramfs? Jun 03 20:32:37 and is the initramfs compressed? Jun 03 20:36:18 <5EXAA8SU8> build #564 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/564 Jun 03 20:38:28 this is hell TT Jun 03 20:38:44 I can't understand where are all those files going nor what each of them do Jun 03 20:44:05 so, after reading the other image/Makefiles and the xilinx doc, in theory, I should repack the cpiogz generated by openwrt's CONFIG_TARGET_ROOTFS_CPIOGZ and use it with mkimage? Jun 03 20:54:54 heffer, in the xilinx doc, they specify two methods, first one, use the initrd, which I don't know which to map onto owrt, and the second one, the initramfs one, that look more to me like a cpio build Jun 03 20:54:59 + mkimage Jun 03 20:59:51 humm I think I have succeeded... Jun 03 20:59:54 I need to check now Jun 03 21:01:13 it works!! Nearlyt Jun 03 21:01:19 I have now the following output: Jun 03 21:01:52 http://pastebin.com/KKmDFeTq Jun 03 21:09:06 ok, now gets one line ahead Jun 03 21:09:10 stuck when loading the kernel Jun 03 21:09:16 Loading Kernel Image ... Jun 03 21:09:22 but still in u-boot Jun 03 21:10:58 hummm I will try not using any compression... Jun 03 21:11:07 on the initramfs Jun 03 21:18:05 cyrusff: there are almost certainly more packages with cves as I only have cpe strings for 380 and I'm not handling multiple cpe strings per package Jun 03 21:25:03 Swalker: ok yeah. Even more arguments for a "reboot" of the packages-feed Jun 03 21:28:35 * txomon|home is almost booting the zedboard... just has to get the rootfs compressed in the correct format... Jun 03 21:31:55 ok, I think the problem comes with some of the patches applied to 3.13.7 .... :( Jun 03 21:32:00 I have no idea on how to debug that... Jun 03 21:41:49 so, someone can help me debugging what is wrong with the kernel? Jun 03 22:02:40 <[florian]> txomon|home: enable earlyprintk to see what's going wrong with the kernel low-level initialization Jun 03 22:05:02 tripolar r40996 packages/net/tor/Makefile * [packages] tor: update to 0.2.4.22 Jun 03 22:44:52 [florian], same thing, I think it's not related Jun 03 22:45:12 I need to go bed now (00:44 and tomorrow I need to work) Jun 03 22:45:31 I think it's something on the way the image is getting generated Jun 03 22:45:41 I must be doing something wrong Jun 04 02:41:18 <5EXAA8SU8> build #629 of atheros is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/629 Jun 04 02:42:54 Is there a fix for archerc7? https://dev.openwrt.org/ticket/16589 **** ENDING LOGGING AT Wed Jun 04 02:59:58 2014