Re: FreeBSD Port: phalcon-2.0.2

2015-06-21 Thread Daniel Lin
Hello, Rudd, https://github.com/phalcon/cphalcon/issues/10531#issuecomment-114001065 We could ignore the warning. Thanks. 2015-06-22 10:30 GMT+08:00 Daniel Lin : > Hello, Ruud, > > Thanks, I'll keep in mind. > > And I find 2.0.3 is out, will port it soon. > > Thanks.

Re: FreeBSD Port: phalcon-2.0.2

2015-06-21 Thread Daniel Lin
Hello, Ruud, Thanks, I'll keep in mind. And I find 2.0.3 is out, will port it soon. Thanks. 2015-06-19 22:36 GMT+08:00 Ruud Boon : > Hi Daniel, > > I saw some warnings while compiling Phalcon 2.0.2. In the end is works > fine but just want to let you know. > > Thnx for maintaining

Re: About Gxneur

2015-06-21 Thread RW via freebsd-ports
On Sun, 21 Jun 2015 16:48:39 -0400 kpn...@pobox.com wrote: > On Sat, Jun 20, 2015 at 11:33:08AM +0300, ??? ??? wrote: > > Hello! > > > > I apologize for my English, I use a translator. > > I noticed that when I install gxneur is one problem. Xneur > > installed and working properly. But g

Re: FreeBSD Port: ruby20-2.0.0.645,1 - reported as vulnerable while it isn't ?

2015-06-21 Thread Ing. Bretislav Kubesa
Hi, not sure if I can help further, but if I understand correctly, yes - ruby 2.0. is/was default. *pkg audit* (after forced upgrade) ruby-2.0.0.645,1 is vulnerable: Ruby -- OpenSSL Hostname Verification Vulnerability CVE: CVE-2015-1855 WWW: https://vuxml.FreeBSD.org/freebsd/d4379f59-3e9b-49eb-93

Re: FreeBSD Port: ruby20-2.0.0.645,1 - reported as vulnerable while it isn't ?

2015-06-21 Thread Steve Wills
Hi, Did you build your own ports where ruby 2.0 was default? I see the package name here is ruby-2.0.0.645,1, not ruby20-2.0.0.645,1. The entries in vuxml look like this: 3326 ruby20 3327 2.0.0.645,1 ... 3330 ruby 3331 2.1.6,1 So I think maybe it's matching

FreeBSD ports you maintain which are out of date

2015-06-21 Thread portscout
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