FreeBSD Port: php56-5.6.8

2015-05-21 Thread M. Zoon
Please upgrade php56 port to latest release. Regards, Michael ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Port License Changes Depending on Options

2015-05-21 Thread Reed A. Cartwright
I have submitted a patch to add a port: biology/bcftools. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199747 The port is dual licensed (MIT/GPL); however, If it is compiled with option GPL, then some features are enabled with require it to be licensed under GPL. I've solved this by choosi

Re: www/chromium : make[1]: stopped in /usr/ports/www/chromium

2015-05-21 Thread Christoph Moench-Tegeder
## Avinash Sonawane (root...@gmail.com): > Is anybody using FreeBSD 10.1-RELEASE able to build www/chromium on > his/her end? I'm still getting the same error. Yes. Both, chromium and firefox, compile and work just fine, here. As both fail in roughly the same way, I still suspect your python inst

Re: LogJam exploit can force TLS down to 512 bytes, does it affect us? ?

2015-05-21 Thread Royce Williams
On Thu, May 21, 2015 at 6:21 AM, Mark Felder wrote: > > > On Wed, May 20, 2015, at 17:48, Xin Li wrote: > ]> > > Well, currently OpenSSL do accept weak DH so _arguably_ it does affect > > FreeBSD, and it's likely to break existing applications if we enforce > > such restrictions (namely, Java 6).

Re: LogJam exploit can force TLS down to 512 bytes, does it affect us? ?

2015-05-21 Thread Mark Felder
On Wed, May 20, 2015, at 17:48, Xin Li wrote: ]> > Well, currently OpenSSL do accept weak DH so _arguably_ it does affect > FreeBSD, and it's likely to break existing applications if we enforce > such restrictions (namely, Java 6). > AFAIK, Java doesn't support >1024 DH key until Java 8. _

Re: USE_GITHUB and submodules

2015-05-21 Thread Jonathan Anderson
Ok, I've updated the port and it passes portlint (with one warning that I can't seem to fix without introducing more warnings). Is the next step to create a Phabricator review request via arcanist? If so, do I list the folks you replied to this thread as reviewers? :) I suppose I would also list pe

Re: www/firefox : Script "configure" failed unexpectedly

2015-05-21 Thread Avinash Sonawane
On Tue, May 19, 2015 at 7:57 PM, Avinash Sonawane wrote: > Hello! > > # uname -a > FreeBSD titanic.rootkea.me 10.1-RELEASE FreeBSD 10.1-RELEASE #0 > r274401: Tue Nov 11 21:02:49 UTC 2014 > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > When I tried to build www/firefox the co

Re: www/chromium : make[1]: stopped in /usr/ports/www/chromium

2015-05-21 Thread Avinash Sonawane
On Tue, May 19, 2015 at 8:01 PM, Avinash Sonawane wrote: > Hello! > > # uname -a > FreeBSD titanic.rootkea.me 10.1-RELEASE FreeBSD 10.1-RELEASE #0 > r274401: Tue Nov 11 21:02:49 UTC 2014 > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > When I tried to build www/chromium the c

Re: Webcam not working

2015-05-21 Thread Kubilay Kocak
On 21/05/2015 2:45 AM, sergio de Almeida Lenzi wrote: > For me the solution is in the PR > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194345 > > an explanation is there and a patch that solved for me... > > Thanks for prodding Sergio. I have moved the issue from In Progress (incorrect) t

Re: LogJam exploit can force TLS down to 512 bytes, does it affect us? ?

2015-05-21 Thread Matthew Seaman
On 05/20/15 23:48, Xin Li wrote: > The document at https://weakdh.org/sysadmin.html gives additional > information for individual daemons, including Apache (mod_ssl), nginx, > lighttpd, Tomcat, postfix, sendmail, dovecot and HAProxy. The part of that https://weakdh.org/ site that concerns me most

Re: LogJam exploit can force TLS down to 512 bytes, does it affect us? ?

2015-05-21 Thread Winfried Neessen
Hi, > The document at https://weakdh.org/sysadmin.html gives additional > information for individual daemons, including Apache (mod_ssl), nginx, > lighttpd, Tomcat, postfix, sendmail, dovecot and HAProxy. > Unfortunately the documentation does only offer guidance for Apache 2.4. As Apache 2.2 do