**** BEGIN LOGGING AT Sun Feb 08 02:59:58 2015
Feb 08 04:03:44 <builder> build #914 of brcm63xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/914
Feb 08 04:33:23 <Zero_Chaos> can anyone double check that I did this PR right? https://github.com/ZeroChaos-/packages/pull/1
Feb 08 04:33:37 <Zero_Chaos> looks kinda wrong with that link at all.
Feb 08 04:33:46 <Zero_Chaos> looks like I sent myself a PR somehow
Feb 08 04:38:15 <Zero_Chaos> there we go, that looks a lot better now: https://github.com/openwrt/packages/pull/879
Feb 08 04:39:50 <Zero_Chaos> DonkeyHotei: it looks like you correctly addressed the only concerns mentioned in the PR.
Feb 08 05:05:41 <DonkeyHotei> Zero_Chaos: there were other comments in my pr that seem to have disappeared
Feb 08 05:07:29 <Zero_Chaos> DonkeyHotei: not sure what to tell you about that :-)
Feb 08 05:22:43 <Zero_Chaos> I don't see a maintainer listed here: https://github.com/openwrt-mirror/openwrt/blob/master/package/system/zram-swap/Makefile
Feb 08 05:23:02 <Zero_Chaos> and it doesn't look like pull requests are accepted against the github mirror...
Feb 08 05:23:25 <Zero_Chaos> so what is the proper process for fixing this stuff? for instance, this is missing a dep on kmod-lib-lz4
Feb 08 05:23:33 <DonkeyHotei> the mailing list
Feb 08 05:23:53 <Zero_Chaos> DonkeyHotei: I really have to join another mailing list? :-(
Feb 08 05:24:08 <DonkeyHotei> use git-format-patch to send to it
Feb 08 05:25:07 <Zero_Chaos> DonkeyHotei: I hate git, and I hate github, but even I have to admit that the process of sending a PR is much easier than the mailing list.
Feb 08 05:27:20 <DonkeyHotei> Zero_Chaos: http://patchwork.ozlabs.org/project/openwrt/list/
Feb 08 05:28:09 <Zero_Chaos> DonkeyHotei: at least it's reasonably low traffic :-)
Feb 08 05:31:33 <Zero_Chaos> DonkeyHotei: it's pretty late here, I suppose I'll fix git-send-email tomorrow. Have a good night man. thanks.
Feb 08 05:31:49 <DonkeyHotei> gn
Feb 08 06:27:31 <builder> build #288 of omap is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/omap/builds/288
Feb 08 10:49:54 <ifdm_> Hi, I wonder to know how safe it is to use a compat wireless driver from the linux-firmware git repo, and later a kernel version from the linux kernel archives
Feb 08 10:50:25 <ifdm_> how is known which version to use?
Feb 08 11:08:42 <plntyk> ifdm_: these drivers dont interfere in boot process it you can use them - but you might have bugs depending on the integration of all OpenWrt specific patches
Feb 08 11:09:03 <plntyk> /it/so
Feb 08 11:10:06 <plntyk> the compat-wireless has a date - as does the backports release version ("backports-20150108")
Feb 08 11:36:14 <builder> build #203 of lantiq.xrx200 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq.xrx200/builds/203
Feb 08 12:04:14 <OpenWrt-Commits> luka r44318 trunk/ (8 files in 2 dirs) * kernel: update 3.18 to 3.18.6
Feb 08 12:04:16 <OpenWrt-Commits> luka r44319 trunk/target/ linux/kirkwood/config-3.18 linux/kirkwood/config-3.14 * kirkwood: refresh kernel config
Feb 08 12:30:24 <builder> build #243 of brcm47xx.legacy is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/243
Feb 08 13:36:07 <builder> build #878 of orion is complete: Failure [failed compile_1]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/878
Feb 08 14:24:00 <DonkeyHotei> [Sat 2015-02-07 09:44:02 AM PST]  <DonkeyHotei> cyrusff: removing that line did not fix the issue
Feb 08 14:31:05 <builder> build #63 of ramips.mt7620 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7620/builds/63
Feb 08 14:37:10 <builder> build #63 of ramips.mt7621 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7621/builds/63
Feb 08 14:39:49 <builder> build #331 of pxa is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/331
Feb 08 14:58:15 <jow_laptop> Zero_Chaos: looks sane so far
Feb 08 15:00:36 <builder> build #64 of ramips.mt7628 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7628/builds/64
Feb 08 15:00:59 <builder> build #876 of lantiq is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/876
Feb 08 15:12:22 <OpenWrt-Commits> luka r44320 trunk/target/ (10 files) * lantiq: fix patches after 3.14.32 bump
Feb 08 15:14:37 <DonkeyHotei> the luci module for ddns has been broken for a while
Feb 08 15:17:40 <jow_laptop> broken how?
Feb 08 15:17:51 <jow_laptop> I do not maintain it, maybe its author would be interested
Feb 08 15:18:14 <DonkeyHotei> keeps saying i must update ddns-scripts
Feb 08 15:18:56 <DonkeyHotei> but ddns-scripts is newer than the luci module
Feb 08 15:34:02 <OpenWrt-Commits> luka r44321 trunk/target/linux/x86/config-3.14 * x86: refresh kernel config
Feb 08 15:36:50 <OpenWrt-Commits> nico r44322 trunk/target/linux/sunxi/profiles/a20-olinuxino.mk * linux/sunxi: rename A20-OLinuXino-Lime profile
Feb 08 15:36:57 <OpenWrt-Commits> nico r44323 trunk/target/ linux/generic/config-3.19 linux/generic/config-3.14 linux/generic/config-3.18 * linux/generic: add missing config symbols
Feb 08 15:37:57 <__trine> my VPN link keeps breaking
Feb 08 15:37:58 <__trine> Sun Feb  8 15:30:09 2015 daemon.notice openvpn(vpn)[9885]: Initialization Sequence Completed
Feb 08 15:37:58 <__trine> Sun Feb  8 15:30:09 2015 daemon.notice netifd: Network device 'tun0' link is down
Feb 08 15:38:20 <__trine> it seems this has been an ongoing problem
Feb 08 15:40:51 <builder> build #217 of ramips.rt3883 is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/217
Feb 08 15:45:19 <OpenWrt-Commits> luka r44324 trunk/target/linux/ramips/ (9 files) * ramips: fix patches after 3.14.32 bump
Feb 08 16:20:55 <_trine> jow_laptop, I found out what was causing my opevpn problem it was what appears to be a luci bug
Feb 08 16:21:40 <_trine> _trine, ducks and waits for the flack
Feb 08 16:26:42 <jow_laptop> details?
Feb 08 16:27:07 <_trine> ok
Feb 08 16:29:21 <_trine> when I am in luci and I have a guest AP if I tick vpn to add to bridge to it luci adds option type 'bridge' to the /etc/config/network
Feb 08 16:29:50 <_trine> when I am in luci and I have a guest AP if I tick vpn to add a bridge to it luci adds option type 'bridge' to the /etc/config/network
Feb 08 16:30:00 <_trine> sorray about the grammar
Feb 08 16:30:28 <_trine> which is correct the action for luci
Feb 08 16:30:54 <_trine> then if I again use luci to untick the box for vpn
Feb 08 16:31:18 <_trine> luci does not remove what it added to /etc/config/network
Feb 08 16:31:39 <jow_laptop> what was added which is not removed?
Feb 08 16:32:16 <_trine> ie the /etc/config/network/option type 'bridge'
Feb 08 16:32:36 <_trine> it is still there after the box was unticked
Feb 08 16:36:12 <_trine> just tried a couple times more and it is still doing the same thing
Feb 08 16:37:08 <_trine> and even though option type 'bridge' is still in my /etc/config/network files luci does not show it
Feb 08 16:38:15 <_trine> this is under the config interface 'vpn'
Feb 08 16:39:24 <jow_laptop> ok
Feb 08 19:57:27 <OpenWrt-Commits> nico r44325 packages/libs/lttng-ust * lttng-ust: moved to github
Feb 08 19:57:30 <OpenWrt-Commits> nico r44326 packages/devel/lttng-tools * lttng-tools: moved to github
Feb 08 22:23:15 <OpenWrt-Commits> jow r44327 trunk/package/network/ipv6/ 6in4/Makefile 6in4/files/6in4.sh * 6in4: fix update timeout
Feb 08 22:25:49 <swalker> jow_laptop: I've had the same proposed cmake.mk change in my tree for awhile now, http://pastebin.com/raw.php?i=nKdK4hp5
Feb 08 22:30:32 <jow_laptop> swalker: so I guess I cna push it right away
Feb 08 22:31:44 <swalker> jow_laptop: I also have a 001-no-rpath.patch for libreadline, still looking for others
Feb 08 22:32:11 <Zero_Chaos> I'm getting this error, pretty much context free even when I "make -j1 V=s"
Feb 08 22:32:14 <Zero_Chaos>  * opkg_install_cmd: Cannot install package 2013-03-R1b.
Feb 08 22:32:27 <Zero_Chaos> based on the versoin tag, it's kismet related, but not sure how to narrow it down.
Feb 08 22:33:36 <jow_laptop> Zero_Chaos: does it have a space in the filename?
Feb 08 22:37:12 <jow_laptop> Zero_Chaos: you can also edit  package/Makefile
Feb 08 22:37:24 <jow_laptop> find the line  @$(FIND) `sed -e 's|.*|$(PACKAGE_DIR)$(if $(CONFIG_PER_FEED_REPO),/*)/&_*.ipk|' $(PACKAGE_INSTALL_FILES)` | sort -u | $(OPKG) install
Feb 08 22:37:31 <jow_laptop> remove the "| $(OPKG) install"
Feb 08 22:37:46 <jow_laptop> run  make package/install V=s
Feb 08 22:37:55 <jow_laptop> and see if it spits out paths with space or other funny chars
Feb 08 22:38:14 <jow_laptop> (\r ?)
Feb 08 22:46:00 <_trine> can aircrack crack anything other than WEP these days
Feb 08 22:55:42 <Fishman> _trine: aircrack-ng has been able to crack WPA for a long time now.  it doesn't bruteforce not terribly efficiently...
Feb 08 22:56:01 <_trine> or not at all
Feb 08 22:56:53 <OpenWrt-Commits> jow r44328 trunk/include/cmake.mk * include: cmake: prevent inclusion of rpath in binaries
Feb 08 22:56:55 * Fishman grumbles.  ignore that "not"
Feb 08 22:56:56 <OpenWrt-Commits> jow r44329 trunk/include/toplevel.mk * include: remove SDK specific target from toplevel.mk
Feb 08 22:57:03 <_trine> I can brute force as deficiently with an abacus
Feb 08 22:57:09 <OpenWrt-Commits> jow r44330 trunk/target/ sdk/files/Makefile sdk/Makefile sdk/files/include sdk/files/include/prepare.mk * sdk: use prepare target to initialize git snapshot
Feb 09 02:02:13 <Zero_Chaos> _trine: did you have to modify mdk3 to make it work at all?
Feb 09 02:04:30 <Zero_Chaos> jow_laptop: after I change that line it seems to not actually be installing, and I also can't seem to figure out how to tell it to install just kismet
Feb 09 02:04:59 <Zero_Chaos> jow_laptop: make feeds/packages/net/kismet/install V=s <-- does not work, no rule to make target feeds/packages/net/kismet/install
Feb 09 02:09:51 <Zero_Chaos> jow_laptop: btw, "make -j8 -O V=s" works amazingly well, don't seem to need -j1 anymore to read my errors.
Feb 09 02:11:52 <stintel> what is -O doing ?
Feb 09 02:12:48 <Zero_Chaos> stintel: -O is a flag for make 4.0 that organizes the output sanely while still building in parallel
Feb 09 02:13:06 <stintel> right, stupid question, I should have man make :)
Feb 09 02:13:22 <stintel> but interesting, I'll have to keep it in mind
Feb 09 02:13:56 <Zero_Chaos> stintel: it's insanely helpful, but I'm not sure how many distros have make 4.0 default. I should hope all of them by now, but now sure
Feb 09 02:14:36 <Zero_Chaos> not sure*
Feb 09 02:16:08 <Zero_Chaos> jow_laptop: also of note, not sure what's wrong with with kismet and why it won't install, but looks like l7-protocols has the same issue
Feb 09 02:17:36 <Zero_Chaos> yikes, and libbz2
Feb 09 02:18:51 <stintel> Zero_Chaos: should it not be "make package/kismet/install" ?
Feb 09 02:19:40 <Zero_Chaos> stintel: you say that like I know what I'm going, that's cute
Feb 09 02:19:44 <stintel> =)
Feb 09 02:19:49 <Zero_Chaos> stintel: I did it your way, no error
Feb 09 02:19:53 <stintel> well I'm not sure either, but try like that
Feb 09 02:20:11 <Zero_Chaos> stintel: doesn't look like that calls opkg at all though, I think opkg only get's called when the image is being made
Feb 09 02:20:14 <stintel> usually it is make package/whateverpkgname/{clean,compile} V=s what I do
Feb 09 02:20:56 <stintel> actually the ipk should be created in bin/arch/packages
Feb 09 02:21:07 <Zero_Chaos> stintel: just for fun, I'll do it -j1 and show what is going on.
Feb 09 02:21:14 <Zero_Chaos> might take a min though
Feb 09 02:23:29 <Zero_Chaos> http://pastebin.com/wH4y9rwr
Feb 09 02:23:46 <Zero_Chaos> that's what I get, the "2013-03-R1b" is the kismet version number
Feb 09 02:23:51 <Zero_Chaos> looks like something got messed up
Feb 09 02:25:50 <stintel> looks like the package name got lost somehow
Feb 09 02:27:08 <stintel> can I see the Makefile ?
**** ENDING LOGGING AT Mon Feb 09 02:59:58 2015