Re: [OpenWrt-Devel] Adding host Java support to the buildbots

2017-01-02 Thread Ralph Sennhauser
On Fri, 30 Dec 2016 06:52:32 -0800 Dana Myers wrote: > On 12/29/2016 11:50 PM, Ralph Sennhauser wrote: > > Hi Dana > > > > On Thu, 29 Dec 2016 12:30:37 -0800 > > Dana Myers wrote: > > > >> In reference to https://github.com/openwrt/packages/pull/3686 > >> > >> We've added OpenWRT support for:

[OpenWrt-Devel] Bug in ipkg?

2017-01-02 Thread Philip Prindeville
I just saw something bizarre. I had a Perl module (CGI v4.35) which contained the following: my $appease_cpants_kwalitee = q/ use strict; use warnings; #/; which is just a quoted string containing the lines that some sanity checking code expects to see (albeit as actual code, and not embedded a

Re: [OpenWrt-Devel] [LEDE-DEV] Bug in ipkg?

2017-01-02 Thread Philip Prindeville
> On Jan 2, 2017, at 9:32 PM, Philip Prindeville > wrote: > > I just saw something bizarre. > > I had a Perl module (CGI v4.35) which contained the following: > > my $appease_cpants_kwalitee = q/ > use strict; > use warnings; > #/; > > which is just a quoted string containing the lines that

Re: [OpenWrt-Devel] [LEDE-DEV] Bug in ipkg?

2017-01-02 Thread Philip Prindeville
> On Jan 2, 2017, at 9:59 PM, Philip Prindeville > wrote: > > >> On Jan 2, 2017, at 9:32 PM, Philip Prindeville >> wrote: >> >> I just saw something bizarre. >> >> I had a Perl module (CGI v4.35) which contained the following: >> >> my $appease_cpants_kwalitee = q/ >> use strict; >> use w

Re: [OpenWrt-Devel] [LEDE-DEV] Bug in ipkg?

2017-01-02 Thread Philip Prindeville
> On Jan 2, 2017, at 10:08 PM, Philip Prindeville > wrote: > > Okay, resolved…. I needed to change the Package/perl-cgi/install macro in > the Makefile to invoke perlmod/Install/NoStrip instead of perlmod/Install. > Sigh. > > Would it be reasonable to add a global variable which disables t

[OpenWrt-Devel] [PATCH] ubus: ubus_free: clear pending timers before freeing context

2017-01-02 Thread Abhimanyu V
From: Abhimanyu Vishwakarma If a synchronous operation is executed on a ubus context after uloop_done() has been called, the context's pending_timer may remain in uloop's list of timeouts. This leads to undefined behaviour during next execution of uloop code, as it may be referring to unavailable