[HEADSUP] Default Perl changed to 5.24.

2016-11-06 Thread Mark Millard
Stefan Ehmann shoesoft at gmx.net on Sun Nov 6 17:51:01 UTC 2016 wrote: > Sun Nov 6 17:51:01 UTC 2016On 06.11.2016 12:43, Andrey Chernov wrote: >> On 06.11.2016 12:34, Mathieu Arnold wrote: >>> Le 05/11/2016 à 16:00, Andrey Chernov a écrit : The instruction posted to UPDATING is a bit incompl

PR commit request

2016-11-06 Thread Yasuhiro KIMURA
Hello, Would someone please commit following 2 PRs with maintainer timeout? Bug 212898 - textproc/trang: update to 2015.11.27 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212898 Bug 212899 - textproc/jing: update to 2015.11.27 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212899 Best Re

lang/perl5.24 upgrade breaks munin-graph in sysutils/munin-master

2016-11-06 Thread Greg Rivers
After upgrading to perl 5.24, munin-graph now exits thusly: 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $dom in concatenation (.) or string at /usr/local/share/munin/munin-graph line 131, line 1. 2016/11/06 16:40:42 [PERL WARNING] Use of uninitialized value $host in concatena

Re: fresh CURRENT + qt5 ports = application bus error

2016-11-06 Thread Maciej Suszko
Boris Samorodov wrote: > Hi All, > > > I've refreshed my current system from a week-ago revision to: > % uname -a > FreeBSD apok.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #4 r308229: Thu > Nov 3 04:23:24 MSK 2016 > bsam@apok.bsnet:/usr/obj/usr/src/sys/APOK64X amd64 > > And pkg upgrade gave me qt

Re: [poudriere]: lang/php56 is unwilling to build with ZTS

2016-11-06 Thread O. Hartmann
Am Thu, 3 Nov 2016 12:03:55 +1000 Dima Panov schrieb: > 01.11.16 20:49, O. Hartmann пишет: > > Obviously I ran into a problem with recent poudriere on CURRENT building > > ports > > in a CURRENT jail. > > > > Building threaded www/apache24 requires lang/php56 having option ZTS set. I > > did >

Re: mail/{neo,}mutt: why not packaged with gpgme?

2016-11-06 Thread Adam Weinberger
> On 6 Nov, 2016, at 12:20, Derek Schrock wrote: > > On Sat, Nov 05, 2016 at 07:14:52AM EDT, Baptiste Daroussin wrote: >> On Wed, Nov 02, 2016 at 09:45:51PM +0100, Niklaas Baudet von Gersdorff wrote: >>> Hello, >>> >>> While talking about an issue I have with mail/{neo,}mutt and >>> security/gnu

Re: mail/{neo,}mutt: why not packaged with gpgme?

2016-11-06 Thread Derek Schrock
On Sat, Nov 05, 2016 at 07:14:52AM EDT, Baptiste Daroussin wrote: > On Wed, Nov 02, 2016 at 09:45:51PM +0100, Niklaas Baudet von Gersdorff wrote: > > Hello, > > > > While talking about an issue I have with mail/{neo,}mutt and > > security/gnupg on #gnupg on freenode I was advised to use > > securi

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-06 Thread Stefan Ehmann
On 06.11.2016 12:43, Andrey Chernov wrote: > On 06.11.2016 12:34, Mathieu Arnold wrote: >> Le 05/11/2016 à 16:00, Andrey Chernov a écrit : >>> The instruction posted to UPDATING is a bit incomplete. >>> Additionlly >>> portupgrade -f "p5-*" >>> should run to move all ports still sitting in 5.20 dir

Re: Unable to build "imapsync"

2016-11-06 Thread Gerard Seibert
On Sun, 6 Nov 2016 16:02:13 +0100, Kurt Jaeger stated: >Hi! > >> I am unable to get the "/mail/imapsync" port to build. It ends with >> this error message: >> >>  ^ ~~~ >> ndbm_wrap.c:208:22: error: too few >> argumen

Re: Unable to build "imapsync"

2016-11-06 Thread Kurt Jaeger
Hi! > I am unable to get the "/mail/imapsync" port to build. It ends with > this error message: > >  ^ ~~~ > ndbm_wrap.c:208:22: error: too few > arguments to function call, expected 5, have 4 > &key, &value, myfl

Unable to build "imapsync"

2016-11-06 Thread Gerard Seibert
I am unable to get the "/mail/imapsync" port to build. It ends with this error message:  ^ ~~~ ndbm_wrap.c:208:22: error: too few arguments to function call, expected 5, have 4 &key, &value, myflags); 

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-06 Thread Andrey Chernov
On 06.11.2016 12:34, Mathieu Arnold wrote: > Le 05/11/2016 à 16:00, Andrey Chernov a écrit : >> The instruction posted to UPDATING is a bit incomplete. >> Additionlly >> portupgrade -f "p5-*" >> should run to move all ports still sitting in 5.20 directory, even if >> they are not depending on perl

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-06 Thread Mark Dixon
Hi, audio/logitechmediaserver is really not fine with 5.24. How to I set it to use a previous version in the mean time? Thanks, Mark ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, se

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-06 Thread Andrea Venturoli
On 11/05/16 08:12, Piotr Szafarczyk wrote: It looks like the same problem I encountered with 5.20 under 10.3 (just one box). Links are not created during port building (with other than perl too). With perl, two links are missing under /usr/local/bin. Creating them manually allows for a successfu

Re: checking dependency tree ia portmaster

2016-11-06 Thread shun . fbsd . pr . ml
On Sat, Nov 05, 2016 at 01:23:04PM -0600, @lbutlr wrote: > given a port that is listed in postmaster -l as a Branch port, how do I see > its dependancies and what it depends on? > > For example, I have libX11 listed as a Branch port and would like to see all > the “upsteream: and “downstream” po

Re: [HEADSUP] Default Perl changed to 5.24.

2016-11-06 Thread Mathieu Arnold
Le 05/11/2016 à 16:00, Andrey Chernov a écrit : > The instruction posted to UPDATING is a bit incomplete. > Additionlly > portupgrade -f "p5-*" > should run to move all ports still sitting in 5.20 directory, even if > they are not depending on perl lib. That should not happen, what ports are affec

FreeBSD ports you maintain which are out of date

2016-11-06 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

clang support for compiler:openmp

2016-11-06 Thread Marcus von Appen
Hi, is there a specific reason, why we do not (yet) have openmp support for clang via compiler:openmp? With devel/openmp in the ports tree, I'd expect compiler:openmp to set LIB_DEPENDS+= libomp.so:devel/openmp for compiler=clang. CFLAGS and LIBS/LDFLAGS might be tweaked on a per-port level.