Re: PHP56 and php56-filter

2017-01-15 Thread @lbutlr
Still haven't been able to fix this error. Any ideas? The only thing that I've found is one suggestion to install the php7 version of filter. On 11 Jan 2017, at 20:10, @lbutlr wrote: > I am getting errors in php pages saying > > Call to undefined function filter_var() > > But php56-filter-5.6.

Re: ATI, libdrm, gnome

2017-01-15 Thread Pavel Timofeev
2017-01-15 0:37 GMT+03:00 Stari Karp : > Hi! > > Today I update xf86-video-ati-7.8 and also libdrm 2.4.7,1. I am using > Synth on FreeBSD 11-RELEASE (amd64) and everything was okay except > thyat GNOME3 doesn't start anymore. It stopped o with black screen and > mouse curson. I did try Lumina deskt

Re: ATI, libdrm, gnome

2017-01-15 Thread Andriy Gapon
On 15/01/2017 00:42, Baptiste Daroussin wrote: > If you know how to use svn and are actually using svn for the ports tree can > you > try reverting the radeon upgrade (only that) (same with git :))? > I can confirm a similar kind of problem with KDE 4 after upgrading to the latest packages. I d

Re: PHP56 and php56-filter

2017-01-15 Thread Aleksandr Matveev
On 12/01/2017 06:10, @lbutlr wrote: > I am getting errors in php pages saying > > Call to undefined function filter_var() > > But php56-filter-5.6.29 is installed and filter is listed in php -m > > I reinstalled all of php this morning, but still getting the same error. > ext-20-filter.ini exists

Re: ATI, libdrm, gnome

2017-01-15 Thread Baptiste Daroussin
On Sun, Jan 15, 2017 at 01:13:41PM +0200, Andriy Gapon wrote: > On 15/01/2017 00:42, Baptiste Daroussin wrote: > > If you know how to use svn and are actually using svn for the ports tree > > can you > > try reverting the radeon upgrade (only that) (same with git :))? > > > > I can confirm a sim

Re: ATI, libdrm, gnome

2017-01-15 Thread Stari Karp
On Sun, 2017-01-15 at 11:32 +0300, Pavel Timofeev wrote: > 2017-01-15 0:37 GMT+03:00 Stari Karp : > > > > Hi! > > > > Today I update xf86-video-ati-7.8 and also libdrm 2.4.7,1. I am > > using > > Synth on FreeBSD 11-RELEASE (amd64) and everything was okay except > > thyat GNOME3 doesn't start any

Re: ATI, libdrm, gnome

2017-01-15 Thread Danilo G. Baio (dbaio)
On Sun, Jan 15, 2017 at 01:13:41PM +0200, Andriy Gapon wrote: > On 15/01/2017 00:42, Baptiste Daroussin wrote: > > If you know how to use svn and are actually using svn for the ports tree > > can you > > try reverting the radeon upgrade (only that) (same with git :))? > > > > I can confirm a sim

Re: ATI, libdrm, gnome

2017-01-15 Thread Stari Karp
On Sun, 2017-01-15 at 12:27 +0100, Baptiste Daroussin wrote: > On Sun, Jan 15, 2017 at 01:13:41PM +0200, Andriy Gapon wrote: > > > > On 15/01/2017 00:42, Baptiste Daroussin wrote: > > > > > > If you know how to use svn and are actually using svn for the > > > ports tree can you > > > try revertin

recent change to vim defaults?

2017-01-15 Thread Julian Elischer
I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/lis

Re: recent change to vim defaults?

2017-01-15 Thread Adam Weinberger
> On 15 Jan, 2017, at 9:03, Julian Elischer wrote: > > I noticed that suddenly vim is grabbing mouse movements, which makes life > really hard. > > Was there a specific revision that brought in this change, and can it be > removed? Which patchlevel are you running? # Adam -- Adam Weinberg

Re: recent change to vim defaults?

2017-01-15 Thread Kyle Evans
On Jan 15, 2017 10:03, "Julian Elischer" wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? ___ freebsd-curr...@freebsd.org ma

Re: ATI, libdrm, gnome

2017-01-15 Thread Andriy Gapon
On 15/01/2017 15:40, Danilo G. Baio (dbaio) wrote: > On Sun, Jan 15, 2017 at 01:13:41PM +0200, Andriy Gapon wrote: >> On 15/01/2017 00:42, Baptiste Daroussin wrote: >>> If you know how to use svn and are actually using svn for the ports tree >>> can you >>> try reverting the radeon upgrade (only t

Re: recent change to vim defaults?

2017-01-15 Thread Ngie Cooper
> On Jan 15, 2017, at 08:03, Julian Elischer wrote: > > I noticed that suddenly vim is grabbing mouse movements, which makes life > really hard. > > Was there a specific revision that brought in this change, and can it be > removed? "set mouse=" will disable the feature you're describing. -N

Aw: recent change to vim defaults?

2017-01-15 Thread Carsten Kunze
Julian Elischer wrote: > I noticed that suddenly vim is grabbing mouse movements, which makes > life really hard. > > Was there a specific revision that brought in this change, and can it > be removed? Of course this behavior can be disabled as suggested by others--or you give it a try. IMH

Re: recent change to vim defaults?

2017-01-15 Thread Benjamin Kaduk
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 in this change, and can it > be removed? I remember seeing something go by during an upgrade

call for a port committer

2017-01-15 Thread Loïc BLOT
Hello, Searx was updated recently, i sent the diff on bugzilla : https://bugs. freebsd.org/bugzilla/show_bug.cgi?id=216007 can someone commit the update? Thanks -- Best regards, Loïc BLOT, UNIX systems, security and network engineer http://www.unix-experience.fr _

pending PRs

2017-01-15 Thread Franco Fichtner
Hi, Please have a look at either one of: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215313 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215900 Thanks, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/list

Re: Aw: recent change to vim defaults?

2017-01-15 Thread Julian Elischer
On 16/01/2017 4:04 AM, Carsten Kunze wrote: Julian Elischer wrote: I noticed that suddenly vim is grabbing mouse movements, which makes life really hard. Was there a specific revision that brought in this change, and can it be removed? Of course this behavior can be disabled as suggested by