Re: NetBeans garbage output problem report

2015-12-02 Thread Jack J. Woehr
Scott Walters wrote: I'm now unable to create a project in NetBeans. Picking New Project -> Java -> Next, I get this screen ("Finding Feature" with the Next button greyed out), and it sits for at least hours for me From my experience this is probably NB throwing memory allocation errors. Did yo

[UDPATE] security/burpsuite

2015-12-02 Thread Remi Pointel
Hi attached is the diff to update burpsuite to 1.6.31. Ok? Cheers, Remi. Index: Makefile === RCS file: /cvs/ports/security/burpsuite/Makefile,v retrieving revision 1.6 diff -u -p -u -p -r1.6 Makefile --- Makefile 23 Nov 2015 16:01

Re: NetBeans garbage output problem report

2015-12-02 Thread Scott Walters
On 11/24/15, Rafael Sadowski wrote: > On Sat Nov 14, 2015 at 03:36:36PM -0700, Scott Walters wrote: >> Hopefully this is going to the correct place. > > Hi Scott, > > could you or maybe other netbeans user test/run the current state of: > > https://github.com/jasperla/openbsd-wip/tree/master/devel

lang/expect: one more memcpy straggler

2015-12-02 Thread Ryan Freeman
I found one more crash in expect (I exercise it TONS), it seems it could only be the one I changed to memmove in the below patch. FWIW, I've never received a mail from Don Libes of nist.gov in regards to my first memcpy->memmove patch from 6 or so months ago, not sure if I ever will :( I've been

update devel/py-test

2015-12-02 Thread Daniel Jakots
Hi, This update needs the update of devel/py-py which is still on ports@. On HOMEPAGE they only talk about 2.8.2 but on [1] I saw 2.8.3 which is 2 weeks old according to their GH page [2] so I went for it. [1]: https://pypi.python.org/pypi/pytest [2]: https://github.com/pytest-dev/pytest/releases

Re: update devel/py-py

2015-12-02 Thread Daniel Jakots
On Wed, 2 Dec 2015 20:15:06 +, Stuart Henderson wrote: > > > Dont remove the ${MODPY_COMMENT} lines from PLIST as they're used > > > for py3 FLAVOR. > > > > Ok, I'm still trying to figure out when to trust make update-plist > > and when to not to :) > > For python ports that have a pyth

Re: update devel/py-py

2015-12-02 Thread Stuart Henderson
On 2015/12/02 20:55, Daniel Jakots wrote: > On Tue, 1 Dec 2015 22:51:21 +0100, Landry Breuil > wrote: > > > On Tue, Dec 01, 2015 at 10:17:46PM +0100, Daniel Jakots wrote: > > > Hi Eric, > > > > > > I tried to update devel/py-py. I didn't want to spend too much time > > > on it because I thought

Re: update devel/py-py

2015-12-02 Thread Daniel Jakots
On Tue, 1 Dec 2015 22:51:21 +0100, Landry Breuil wrote: > On Tue, Dec 01, 2015 at 10:17:46PM +0100, Daniel Jakots wrote: > > Hi Eric, > > > > I tried to update devel/py-py. I didn't want to spend too much time > > on it because I thought you might already have worked on it. > > Dont remove th

Re: Make nginx reload fail

2015-12-02 Thread Martijn van Duren
On 12/02/15 10:15, Antoine Jacoutot wrote: On Wed, Dec 02, 2015 at 10:12:56AM +0100, Martijn van Duren wrote: Hello ports@, currently when nginx is issued a reload command it simply sends a dumb SIGHUP, but without checking if the reload is loaded correctly. Since nginx keeps running one might

Re: Make nginx reload fail

2015-12-02 Thread Stuart Henderson
On 2015/12/02 10:15, Antoine Jacoutot wrote: > On Wed, Dec 02, 2015 at 10:12:56AM +0100, Martijn van Duren wrote: > > Hello ports@, > > > > currently when nginx is issued a reload command it simply sends a dumb > > SIGHUP, but without checking if the reload is loaded correctly. Since nginx > > kee

Make nginx reload fail

2015-12-02 Thread Martijn van Duren
Hello ports@, currently when nginx is issued a reload command it simply sends a dumb SIGHUP, but without checking if the reload is loaded correctly. Since nginx keeps running one might get the impression that the reload was successful. Would it make sense to check the validity of the configu

Re: Make nginx reload fail

2015-12-02 Thread Antoine Jacoutot
On Wed, Dec 02, 2015 at 10:12:56AM +0100, Martijn van Duren wrote: > Hello ports@, > > currently when nginx is issued a reload command it simply sends a dumb > SIGHUP, but without checking if the reload is loaded correctly. Since nginx > keeps running one might get the impression that the reload w