PRs ready for commit for www/node*

Howdy! I've got several patches pending for the www/node* ports (I'm the maintainer for these ports). One is a fix for several build failures that have been recently reported, one is to fix portlint warnings, and the others are version bumps to address security issues. Build fix: https://bugs.

Re: blanket portmgr approval vs. non-fixing changes

Baptiste Daroussin wrote: On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: And I do think we should, opposite to what you are proposing, make the committer spend extra time for high-profile ports that entail sweeping changes to chase down the breaking change to, say, a library p

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: blanket portmgr approval vs. non-fixing changes

+--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan wrote: | Baptiste Daroussin wrote: |> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: |>> |>> And I do think we should, opposite to what you are proposing, make the |>> committer spend extra time for high-profile ports that enta

Re: blanket portmgr approval vs. non-fixing changes

Mathieu Arnold wrote: +--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan wrote: | Baptiste Daroussin wrote: |> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: |>> |>> And I do think we should, opposite to what you are proposing, make the |>> committer spend extra time for high-

audio/csound6 endless loop and creates empty sound files

Hello, has anyone used audio/csound6 recently on FreeBSD? It compiles just fine, but it creates bogus output, AFAICS. Here's an example, simplified from Chapter 1 of The CSound Book: http://www.csounds.com/chapter1/ $ cat e1.orc sr = 44100 kr = 4410 ksmps = 10 nchnls = 1 instr 101 a1 os

Re: blanket portmgr approval vs. non-fixing changes

On Wed, Jun 29, 2016 at 06:35:46PM +0200, Michelle Sullivan wrote: > Mathieu Arnold wrote: > > +--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan > > wrote: > > | Baptiste Daroussin wrote: > > |> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: > > |>> > > |>> And I do think we sh

Re: Torch7 ports (Was: Wxlua / Zbstudio)

Hi all, I tried the Jan's git ports. However, I got 21 errors out of 127 torch tests. It said FFI can't point to some structures. Also, I can require nn even it was installed via luarocks. It said the tester suite is missing. Are the blas finding codes located at math/TH? Thanks. Raymond On Jun

python 3.4.5 update

Hi! I tried to update Python on my  10.3-RELEASE-p5 (akd64) and I got: ports/lang/python34/work/Python-3.4.5 ./python -E -m ensurepip  $ensurepip --root=/usr/ports/lang/python34/work/stage/ ;  fi /bin/rm -f /usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so # Upstream I

Re: Is there still broken lang/ruby23 ?

Hi, > On Tue, 28 Jun 2016 22:13:44 -0400 > Steve Wills said: Kazuhiko> Is there still broken lang/ruby23[1]. Or can build in latest Kazuhiko> 11.0-* ? Kazuhiko> [1] http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364 swills> Yes, I haven't looked at it yet, but if yo

Re: PRs ready for commit for www/node*

Hi! > I've got several patches pending for the www/node* ports [...] > I'd appreciate help from a willing and able committer to get these > in the tree, ideally before the next quarterly branch is cut. Done. -- p...@opsec.eu+49 171 3101372 4 years to go ! __

Re: PRs ready for commit for www/node*

> On 30 Jun 2016, at 08:28, Kurt Jaeger wrote: > > Hi! > >> I've got several patches pending for the www/node* ports [...] > >> I'd appreciate help from a willing and able committer to get these >> in the tree, ideally before the next quarterly branch is cut. > > Done. Thanks, Kurt. I apprec