**** BEGIN LOGGING AT Sat Jul 25 02:59:58 2015 Jul 25 03:17:22 build #66 of au1000 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/66 Jul 25 03:48:45 build #67 of ramips.mt7620 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7620/builds/67 Jul 25 04:15:38 build #67 of ramips.rt305x is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt305x/builds/67 Jul 25 05:07:47 build #67 of brcm63xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/67 Jul 25 05:13:02 build #67 of brcm47xx.legacy is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/67 Jul 25 05:14:40 build #65 of mpc83xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/65 Jul 25 05:19:50 build #65 of ep93xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/65 Jul 25 05:29:13 build #67 of brcm47xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/67 Jul 25 05:41:08 build #67 of ramips.mt7628 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7628/builds/67 Jul 25 05:56:49 build #65 of at91 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/65 Jul 25 06:29:29 i'm trying to create a patch for a package with the sdk, after confirming the patch with quilt diff and quilt refresh, i go back to the sdk dir and run make package//update V=s, but it failed, saying recipe for ".quilt_checked" in that package dir failed. what might be the problem? Jul 25 06:38:06 nvm, run clean fixed it Jul 25 06:50:58 build #65 of brcm2708 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm2708/builds/65 Jul 25 07:06:38 build #66 of ath25 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ath25/builds/66 Jul 25 07:11:46 I think i found the problem. the quilt script in staging_dir/host/bin has hardcoded /home/buildbot/slave-local in the shebang path when trying to access bash, which doesn't exist in my machine. cc jow_laptop Jul 25 07:18:05 is the sdk provided in downloads.openwrt.org meant to be used by end users or i should always compile my own? Jul 25 07:32:20 build #65 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/65 Jul 25 07:34:12 build #65 of cns3xxx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/cns3xxx/builds/65 Jul 25 07:37:31 build #65 of mpc52xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/65 Jul 25 07:41:45 build #66 of adm8668 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/66 Jul 25 07:44:10 build #65 of ar71xx.mikrotik is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx.mikrotik/builds/65 Jul 25 08:03:34 build #65 of mvebu is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/65 Jul 25 08:06:46 build #67 of cobalt is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/67 Jul 25 08:09:50 build #67 of cns21xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/67 Jul 25 08:13:14 build #67 of orion is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/67 Jul 25 08:39:43 build #65 of mcs814x is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/65 Jul 25 08:49:17 build #66 of mpc85xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mpc85xx/builds/66 Jul 25 08:52:36 build #67 of pxa is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/67 Jul 25 09:24:10 build #68 of bcm53xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/68 Jul 25 09:53:01 build #65 of gemini is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/65 Jul 25 09:53:33 build #65 of adm5120 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/65 Jul 25 09:56:06 jogo r46485 trunk/target/linux/ generic/patches-4.0/259-regmap_dynamic.patch generic/patches-4.1/259-regmap_dynamic.patch generic/patches-3.18/259-regmap_dynamic.patch * kmod-regmap: make regmap-mmio user selectable Jul 25 10:03:14 jogo r46486 branches/chaos_calmer/target/linux/brcm63xx/dts/hg553.dts * CC: brcm63xx: HG553 buttons support Jul 25 10:03:18 jogo r46487 branches/ (12 files in 3 dirs) * CC: kernel: update 3.18 to 3.18.19 Jul 25 10:07:37 build #67 of ramips.mt7621 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7621/builds/67 Jul 25 10:17:01 build #67 of ramips.rt3883 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/67 Jul 25 10:19:46 build #67 of ppc40x is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/67 Jul 25 10:39:23 build #67 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/67 Jul 25 12:12:34 jogo r46488 trunk/scripts/redboot-script.pl * scripts: add tool for generating redboot scripts Jul 25 12:12:38 jogo r46489 trunk/target/linux/ brcm63xx/image/redbootscript.template brcm63xx/image/Makefile * brcm63xx: use new tool for generating redboot images Jul 25 12:12:42 jogo r46490 trunk/target/linux/brcm63xx/image/Makefile * brcm63xx: switch to new image building system Jul 25 12:12:59 jogo r46491 trunk/package/system/opkg/ Makefile files/customfeeds.conf files/20_migrate-feeds * opkg: ensure image provided feeds are available after sysupgrade Jul 25 12:24:38 build #67 of x86.64 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/x86.64/builds/67 Jul 25 12:51:22 dependson the end user... Jul 25 12:51:35 and what they want to build.. Jul 25 13:41:14 hauke r46492 trunk/package/kernel/mac80211/patches/020-backports-do-not-add-debugfs_create_devm_seqfile-on-.patch * mac80211: do not add debugfs_create_devm_seqfile() on recent kernel versions Jul 25 13:41:52 hauke r46493 trunk/target/linux/ generic/patches-4.1/190-cdc_ncm_add_support_for_moving_ndp_to_end_of_ncm_frame.patch generic/patches-3.18/190-cdc_ncm_add_support_for_moving_ndp_to_end_of_ncm_frame.patch generic/patches-4.0/190-cdc_ncm_add_support_for_moving_ndp_to_end_of_ncm_frame.patch * kernel: cdc_ncm: Add support for moving NDP to end of NCM frame Jul 25 13:43:19 any roadmap for openwrt, e.g. will systemd ever be adopted? which release will luci2 be supported? which release will nftable be replacing netfilter? those are all major items Jul 25 13:54:46 hauke r46494 branches/chaos_calmer/target/linux/ar71xx/patches-3.18/718-MIPS-ath79-add-EPG5000-support.patch * CC: ar71xx: EPG5000 requires ATH79_NVRAM Jul 25 14:49:50 ausjke: systemd will probably never been adopted Jul 25 14:50:00 pretty sure systemd is "never" given how much work they went into building procd, and how much else systemd exepcts Jul 25 14:50:06 there is no roadmap Jul 25 14:57:37 hopefully the kernel and many packages will still function when systemd is disabled, the trend does not look promising, distros without systemd support is becoming really scarce, sad reality Jul 25 14:58:00 ausjke: the deciding factors for (not) implementing something in openwrt are "is it benefical to openwrt", and "does anybody care enough to do it" Jul 25 16:37:28 ausjke: are you _really_ concerned that there will be a kernel that requires systemd? I don't think that's something you should care about Jul 25 17:04:01 i think it's more likely that more standard user space applications will be built with systemd in mind Jul 25 17:04:07 and even that is nothing we need to be concerned about Jul 25 17:04:38 isn't that more likely to be a concern than the kernel? Jul 25 17:04:57 I guess it depends how many more systemd features people start using. Jul 25 17:05:15 well, openwrt controls a large part of the user space infrastructure as well Jul 25 17:05:51 most of the things that are more likely to depend on systemd in the future are probably things that openwrt users wouldn't care about anyway Jul 25 17:08:32 I guess, there's a lot of things like "automatically starting services when the port is accessed" though that are nice, possibly even nicer on embedded where you don't want them all running all the time. Jul 25 17:13:05 i'm still not convinced that this is very useful Jul 25 17:13:21 for some corner cases it might potentially be useful, but in the common case it's probably completely unnecessary Jul 25 17:13:38 especially since it makes it harder to estimate the worst case memory usage on embedded devices Jul 25 17:14:00 I tend to agree, for most people having the process running but paged out asleep is good enough Jul 25 17:14:13 * karlp shrugs, time will tell. Jul 25 17:14:26 it's probably a bad idea to have many things configured and enabled (but only started on first access), only to find out later that connecting to a port will make the device go OOM Jul 25 17:14:47 OOM is so much fun. Jul 25 17:14:51 that's why i didn't add support for this stuff to procd yet Jul 25 17:15:13 I think more useful for procd would be to get the pid of a process started by procd :) Jul 25 17:15:42 feel free to send a patch Jul 25 17:15:48 this should be easy enough to add Jul 25 17:16:10 unlike various init approaches systemd is very intrusive, the desktop/server guys are making embedded linux even harder now with systemd, unless you adopt systemd and it's resource friendly Jul 25 17:16:34 ausjke: i don't think it's much of a problem for us Jul 25 17:16:48 and i don't see any sane way to adopt systemd Jul 25 17:16:54 ausjke: systemd's also not deaf, they've been doign work to make it more useful for embedded, Jul 25 17:16:54 aside from the fact that it's way too bloated Jul 25 17:17:06 but yeah, I think we can just ignore it for owrt for now :) Jul 25 17:17:10 systemd is also conceptually too different from what openwrt needs Jul 25 17:17:39 nbd: it would be nice to get pids so that commands like "reload" can send signals to the right things, and so that I can write out pid files for non procd monitoring things Jul 25 17:19:51 sending signals to service instances based on config file changes might be a useful addition to procd Jul 25 17:20:05 so that procd can tell the difference between having to restart a service and just sending a reload signal Jul 25 17:20:20 to make it work with its own native instance tracking as opposed to just doing it unconditionally from the init script Jul 25 17:30:07 they would both go together well, yes :) Jul 25 21:47:13 who's around to blacklist 'exam' from trac? Jul 25 21:47:31 Hi anyone here has experience with the VGV7519? I've got a KPN experiabox version, but I am unable to get the JTAG working as documented on the wiki: http://wiki.openwrt.org/toh/arcadyan/vgv7519 Jul 25 21:51:15 Since that page is written by a user named thelizard, is he still visiting this channel? Jul 25 21:51:32 build #69 of malta is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/malta/builds/69 Jul 26 02:13:00 build #66 of x86.xen_domu is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.xen_domu/builds/66 **** ENDING LOGGING AT Sun Jul 26 02:59:58 2015