FreeBSD ports you maintain which are out of date

2017-01-18 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

Re: standard settings for ports.

2017-01-18 Thread Trond Endrestøl
On Thu, 19 Jan 2017 11:13+0800, Julian Elischer wrote: > On 19/01/2017 1:28 AM, Trond Endrestøl wrote: > > On Thu, 19 Jan 2017 01:25+0800, Julian Elischer wrote: > > > > > pointers appreciated... > > Try something like this in /etc/make.conf: > > > > DEFAULT_VERSIONS=apache=2.4 bdb=6 firebird=2.

jdk7 broken in some way?

2017-01-18 Thread Julian Elischer
last night I had poudriere try build jdk8 but that required jdk7 which didn't build. I think itwanted jdk6 or maybe bootstrap-openjdk. whatever it needed (it said it couldn't make a java vm) it didn't do it. I thought poudriere would set up everything needed.. Is there anything special need

Re: poudriere: devel/llvm39: runaway_process

2017-01-18 Thread mokhi
On 1/19/17, Craig Leres wrote: > My poudriere build servers have been unable to build devel/llvm39 ever > since some ports changed from llvm37 (January 17th?) The error is > runaway_process and this happens during the package phase. It looks like > pkg-static spins for one hour at which point poud

Re: poudriere: devel/llvm39: runaway_process

2017-01-18 Thread Julian Elischer
On 19/01/2017 5:49 AM, Craig Leres wrote: My poudriere build servers have been unable to build devel/llvm39 ever since some ports changed from llvm37 (January 17th?) The error is runaway_process and this happens during the package phase. It looks like pkg-static spins for one hour at which poin

Re: poudriere: devel/llvm39: runaway_process

2017-01-18 Thread Julian Elischer
On 19/01/2017 5:49 AM, Craig Leres wrote: My poudriere build servers have been unable to build devel/llvm39 ever since some ports changed from llvm37 (January 17th?) The error is runaway_process and this happens during the package phase. It looks like pkg-static spins for one hour at which poin

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 19/01/2017 11:18 AM, Julian Elischer wrote: On 19/01/2017 1:37 AM, Adam Weinberger wrote: On 18 Jan, 2017, at 10:35, Julian Elischer wrote: On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 19/01/2017 1:37 AM, Adam Weinberger wrote: On 18 Jan, 2017, at 10:35, Julian Elischer wrote: On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is g

Re: standard settings for ports.

2017-01-18 Thread Julian Elischer
On 19/01/2017 1:28 AM, Trond Endrestøl wrote: On Thu, 19 Jan 2017 01:25+0800, Julian Elischer wrote: pointers appreciated... Try something like this in /etc/make.conf: DEFAULT_VERSIONS=apache=2.4 bdb=6 firebird=2.5 gcc=4.9 ghostscript=9 lua=5.2 mysql=5.7 perl5=5.22 php=5.6 pgsql=9.5 python=2

poudriere: devel/llvm39: runaway_process

2017-01-18 Thread Craig Leres
My poudriere build servers have been unable to build devel/llvm39 ever since some ports changed from llvm37 (January 17th?) The error is runaway_process and this happens during the package phase. It looks like pkg-static spins for one hour at which point poudriere gives up on it. Yesterday I ra

FreeBSD Port: relayd-5.5.20140810_2

2017-01-18 Thread Albert Gabàs | Astabis IRM
Dear Martin, Are you still maintaining the relayd port? If yes, could you please sync the port to the latest OpenBSD version?? In the meantime, thank you so much for your work and attention. Kind regards Albert Gabàs ___ freebsd-ports@freeb

Re: recent change to vim defaults?

2017-01-18 Thread Steven Hartland
mouse=n ? On 18/01/2017 18:01, Julian Elischer wrote: On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really work for me. vim is still taking mouse events ___ freebsd-ports@free

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 18/01/2017 5:03 PM, Raimund Sacherer wrote: I have to put mouse=v to get the behavior I am used to. Best doesn't really work for me. vim is still taking mouse events ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/l

Re: recent change to vim defaults?

2017-01-18 Thread Baptiste Daroussin
On Wed, Jan 18, 2017 at 10:37:32AM -0700, Adam Weinberger wrote: > > On 18 Jan, 2017, at 10:35, Julian Elischer wrote: > > > > On 17/01/2017 1:23 AM, Adam Weinberger wrote: > >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: > >>> > >>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Eli

Re: recent change to vim defaults?

2017-01-18 Thread Adam Weinberger
> On 18 Jan, 2017, at 10:35, Julian Elischer wrote: > > On 17/01/2017 1:23 AM, Adam Weinberger wrote: >>> On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: >>> >>> On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, wh

Re: recent change to vim defaults?

2017-01-18 Thread Julian Elischer
On 17/01/2017 1:23 AM, Adam Weinberger wrote: On 16 Jan, 2017, at 9:25, Baptiste Daroussin wrote: On Mon, Jan 16, 2017 at 12:03:08AM +0800, Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought

Re: standard settings for ports.

2017-01-18 Thread Trond Endrestøl
On Thu, 19 Jan 2017 01:25+0800, Julian Elischer wrote: > pointers appreciated... Try something like this in /etc/make.conf: DEFAULT_VERSIONS=apache=2.4 bdb=6 firebird=2.5 gcc=4.9 ghostscript=9 lua=5.2 mysql=5.7 perl5=5.22 php=5.6 pgsql=9.5 python=2.7 python2=2.7 python3=3.5 ruby=2.2 ssl=openss

standard settings for ports.

2017-01-18 Thread Julian Elischer
I know there are some standard setting one can set.. make ports shows 8 but I know there are many more. like what version of perl you want to use throughout your system or whether you want to use openssl from ports or system or what version of python.. or whether to use some version of gcc

Re: net/boinc-client: make LINUX option a default or Slave port?

2017-01-18 Thread Larry Rosenman
On 2017-01-18 09:57, Torfinn Ingolfsen wrote: On Tue, Jan 17, 2017 at 11:41 PM, Larry Rosenman wrote: On 2017-01-17 16:31, Manfred Antar wrote: I've been running a freebsd compiled seti version 8 here for months. I think someone needs to update the port. i put the precomiled binaries on my

Re: Any plans to update Mythtv port to 0.28?

2017-01-18 Thread Walter Schwarzenfeld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216237 please, try this update patch (and tell me if something not working as expected). ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscri

Re: net/boinc-client: make LINUX option a default or Slave port?

2017-01-18 Thread Torfinn Ingolfsen
On Tue, Jan 17, 2017 at 11:41 PM, Larry Rosenman wrote: > On 2017-01-17 16:31, Manfred Antar wrote: > >> >> I've been running a freebsd compiled seti version 8 here for months. >> I think someone needs to update the port. >> >> i put the precomiled binaries on my website at : >> >> www.pozo.com/se

Re: recent change to vim defaults?

2017-01-18 Thread Raimund Sacherer
I have to put mouse=v to get the behavior I am used to. Best⁣ Sent from TypeApp ​ On Jan 18, 2017, 08:46, at 08:46, Julian Elischer wrote: >On 17/01/2017 12:07 AM, ohauer wrote: >> I suspect you mean the /usr/local/etc/vim/vimrc and gvimrc files. >> That was the first place I've tried to overwr

FreeBSD ports you maintain which are out of date

2017-01-18 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