However the thing that bothers me more than 'nut' failing, is the fact
that it is _not_ selected in my .config. What would be causing it to build?
If I uninstall the package (./scripts/feeds uninstall nut) my build succeeds
fine.
I think that the reason is badly implemented nut support in
It is really annoying that dev.openwrt.org frequently gives 504 Gateway
Time-out or 502 Bad Gateway errors. During the last few days it seems that
the bug tracker is unreachable half of the time.
Typical error is just:
502 Bad Gateway
nginx/1.1.19
Is there some problem connectivity problem
ping
On Mon, Feb 24, 2014 at 1:28 AM, Catalin Patulea c...@vv.carleton.ca wrote:
From: hnyman
Sending this in for hnyman, from issue #15070:
https://dev.openwrt.org/ticket/15070
Should fix that issue.
Signed-off-by: Catalin Patulea c...@vv.carleton.ca
---
ping
On Mon, Feb 24, 2014 at 1:02 AM, Catalin Patulea c...@vv.carleton.ca wrote:
Upstream changelog:
https://matt.ucc.asn.au/dropbear/CHANGES
This adds elliptic curve cryptography (ECC) support as an option, disabled
by default.
dropbear mips 34kc uClibc binary size:
before: 161,672 bytes
Well, the patch in the bug from anonymous was not from me.
I checked your patch and wonder if network_get_device Interface part is right.
Anonymous had left that with small caps, but your patch changed also that to
Interface.
Should that line be instead this way?
[ -n ${Interface} ]
On Sat, Mar 1, 2014 at 4:25 AM, Hannu Nyman hannu.ny...@iki.fi wrote:
Should that line be instead this way?
[ -n ${Interface} ] network_get_device interface ${Interface}
I think the only place where interface is used is on the following line:
- append_ports ${interface} ${Port}
+
