FreeBSD ports you maintain which are out of date

2018-03-19 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 can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
multimedia/vdr  | 1.7.29  | 2.3.9
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Mattermost needs a commiter

2018-03-19 Thread Loïc BLOT
Hello,
i just published Mattermost 4.8 upgrade.
Can someone push the fix ?

Thanks

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226716

-- 
Best regards,
Loïc BLOT, 
UNIX systems, security and network engineer
http://www.unix-experience.fr

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


"converters/php72-mbstring" build failure

2018-03-19 Thread Carmel NY
FreeBSD-11.1-RELEASE-p8

I am attempting to update the "converters/php72-mbstring" port. The older
version build fine. The newest version fails with this error message:

/usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
php_mb_re_pattern_buffer' struct re_pattern_buffer;
   ^
./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
#define re_pattern_buffer   php_mb_re_pattern_buffer
^
/construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:41:
error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if (!rc
|| rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
/usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
php_mb_re_pattern_buffer' struct re_pattern_buffer;
   ^
./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
#define re_pattern_buffer   php_mb_re_pattern_buffer
^
/construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:59:
error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if (!rc
|| rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
/usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
php_mb_re_pattern_buffer' struct re_pattern_buffer;
   ^
./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
#define re_pattern_buffer   php_mb_re_pattern_buffer
^
3 errors generated.
*** [php_mbregex.lo] Error code 1

make[1]: stopped
in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
1 error

make[1]: stopped
in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and
rebuild before reporting the failure to the maintainer.
*** Error code 1

Stop.
make: stopped in /xports/converters/php72-mbstring


The complete build log file is available here:
https://www.seibercom.net/converters___php72-mbstring.log

I routinely use "synth" to build my ports, if it makes any difference.

-- 
Carmel
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: "converters/php72-mbstring" build failure

2018-03-19 Thread Kubilay Kocak
On 19/03/2018 9:22 pm, Carmel NY wrote:
> FreeBSD-11.1-RELEASE-p8
> 
> I am attempting to update the "converters/php72-mbstring" port. The older
> version build fine. The newest version fails with this error message:
> 
> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>^
> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
> #define re_pattern_buffer   php_mb_re_pattern_buffer
> ^
> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:41:
> error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if (!rc
> || rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>^
> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
> #define re_pattern_buffer   php_mb_re_pattern_buffer
> ^
> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:59:
> error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if (!rc
> || rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>^
> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
> #define re_pattern_buffer   php_mb_re_pattern_buffer
> ^
> 3 errors generated.
> *** [php_mbregex.lo] Error code 1
> 
> make[1]: stopped
> in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
> 1 error
> 
> make[1]: stopped
> in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
> ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and
> rebuild before reporting the failure to the maintainer.
> *** Error code 1
> 
> Stop.
> make: stopped in /xports/converters/php72-mbstring
> 
> 
> The complete build log file is available here:
> https://www.seibercom.net/converters___php72-mbstring.log
> 
> I routinely use "synth" to build my ports, if it makes any difference.
> 

Hi Carmel,

The issue was picked up in this thread:
https://lists.freebsd.org/pipermail/svn-ports-all/2018-March/177869.html


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: "converters/php72-mbstring" build failure

2018-03-19 Thread Kubilay Kocak
On 19/03/2018 9:33 pm, Kubilay Kocak wrote:
> On 19/03/2018 9:22 pm, Carmel NY wrote:
>> FreeBSD-11.1-RELEASE-p8
>>
>> I am attempting to update the "converters/php72-mbstring" port. The older
>> version build fine. The newest version fails with this error message:
>>
>> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
>> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>>^
>> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
>> #define re_pattern_buffer   php_mb_re_pattern_buffer
>> ^
>> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:41:
>> error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if 
>> (!rc
>> || rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
>> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
>> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>>^
>> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
>> #define re_pattern_buffer   php_mb_re_pattern_buffer
>> ^
>> /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring/php_mbregex.c:452:59:
>> error: incomplete definition of type 'struct php_mb_re_pattern_buffer' if 
>> (!rc
>> || rc->options != options || rc->enc != enc || rc->syntax != syntax) { ~~^
>> /usr/local/include/oniguruma.h:673:8: note: forward declaration of 'struct
>> php_mb_re_pattern_buffer' struct re_pattern_buffer;
>>^
>> ./php_onig_compat.h:4:37: note: expanded from macro 're_pattern_buffer'
>> #define re_pattern_buffer   php_mb_re_pattern_buffer
>> ^
>> 3 errors generated.
>> *** [php_mbregex.lo] Error code 1
>>
>> make[1]: stopped
>> in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
>> 1 error
>>
>> make[1]: stopped
>> in /construction/xports/converters/php72-mbstring/work/php-7.2.3/ext/mbstring
>> ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and
>> rebuild before reporting the failure to the maintainer.
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /xports/converters/php72-mbstring
>>
>>
>> The complete build log file is available here:
>> https://www.seibercom.net/converters___php72-mbstring.log
>>
>> I routinely use "synth" to build my ports, if it makes any difference.
>>
> 
> Hi Carmel,
> 
> The issue was picked up in this thread:
> https://lists.freebsd.org/pipermail/svn-ports-all/2018-March/177869.html
> 
> 

Also now here (with patch):

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226717
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


how to get autoconf to run

2018-03-19 Thread Gary Aitken

Hate to return so soon, but what is required in Makefile to get
autoconf to do its thing?

According the the porter's handbook, adding

USE_AUTOTOOLS=  autoheader aclocal

should get autoconf to do its thing.
It doesn't mention
  GNU_CONFIGURE=  yes
but I assume that is also required.
In any case, I've tried it both ways.
without GNU_CONFIGURE, make config succeeds but does nothing;
in particular, no "configure" file is created.

with GNU_CONFIGURE:

$ make configure
===>  Configuring for ufraw-devel-g20161113
env: ./configure: No such file or directory
===>  Script "configure" failed unexpectedly.

I've tried running as root as well as regular user with the same results.
There are no new files in the working directories.
My search for clues turned up nothing.

Thanks for any pointers,

Gary
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Committer needed for new port (databases/go-carbon)

2018-03-19 Thread Andreas Andersson
Can someone take a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226732 suggestions for
improvements are welcome.

/Andreas
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: how to get autoconf to run

2018-03-19 Thread Kurt Jaeger
Hi!

> Hate to return so soon, but what is required in Makefile to get
> autoconf to do its thing?

Look at /usr/ports/Mk/Uses/autoreconf.mk, and read through the comment
block at the beginning. It explains the general idea.

USES=   autoreconf

or, maybe:

USES=   autoreconf:autoconf

should do the right thing.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: FreeBSD 11.1-RELEASE - mail/milter-manager broken

2018-03-19 Thread Leander Schäfer
Alright, but how am I going to tell my poudriere to build this specific port 
‘mail/milter-manager‘ with the specific ‘lang/ruby25‘ without forcing all the 
other ports to be built with ‘lang/ruby25‘. This far I‘m only aware of using

DEFAULT_VERSIONS+=ruby=2.5

in the /usr/local/etc/poudriere.d/repo-make.conf

unfortunately enforcing it this the global way, ruby 2.5 will break other ports 
being built in this repo and not harmonize as desired. I was hoping for 
something oldschool like in poudrier's 
/usr/local/etc/poudriere.d/repo-make.conf:

.if ${CURDIR:M*/ports/mail/milter-manager}
DEFAULT_VERSIONS+=ruby=2.5
.endif

Any clue how this is done with poudriere?

Best regards,
Leander


Am 19.03.18 um 02:07 schrieb Kenji Okimoto:
> You cannot use milter-manager with Ruby 2.4.3.
> It's known issue. It has been fixed in Ruby 2.5.0 and 
> https://github.com/ruby/ruby/tree/ruby_2_4
> If you want to cherry-pick the patch see 
> https://github.com/ruby/ruby/commit/3d4a397354fd8d27c5eb91ca5c3bd7afe9b11af0#diff-7875e170ada1a2b62a8c8798729afa11
>
>
> ---
>
> ** [bugs:#7] Segmentation fault (core dumped)**
>
> **Status:** open
> **Group:** v1.0_(example)
> **Created:** Sun Mar 18, 2018 10:30 AM UTC by Leander Schäfer
> **Last Updated:** Sun Mar 18, 2018 11:21 AM UTC
> **Owner:** nobody
>
>
> Execution of milter-manager binary results in a Segmentation fault (core 
> dumped).
> OS: FreeBSD 11.1-RELEASE
>
> pkg info milter-manager
> milter-manager-2.0.7_1
> Name   : milter-manager
> Version: 2.0.7_1
> Installed on   : Sun Mar 18 11:12:56 2018 CET
> Origin : mail/milter-manager
> Architecture   : FreeBSD:11:amd64
> Prefix : /usr/local
> Categories : ruby mail
> Licenses   : GPLv3, LGPL3, GFDL, AGPLv3
> Maintainer : po...@freebsd.org
> WWW: http://milter-manager.sourceforge.net/
> Comment: Super milter that can invoke several milters selectively
> Options:
>   DOCS   : on
>   EXAMPLES   : on
> Shared Libs required:
>   libintl.so.8
>   libglib-2.0.so.0
>   libgobject-2.0.so.0
>   libgmodule-2.0.so.0
>   libruby24.so.24
>   libgthread-2.0.so.0
>   libev.so.4
>   libunwind.so.8
> Shared Libs provided:
>   libmilter-core.so.0
>   libmilter-server.so.0
>   libmilter-client.so.0
>   libmilter-manager.so.0
>   libmilter.so.1
> Annotations:
>   repo_type  : binary
>   repository : FreeBSD
> Flat size  : 4.66MiB
> Description:
> milter manager protects you from spam mails and virus mails effectively
> with milter. milter manager has embedded Ruby interpreter to control
> milters flexibly.
>
> WWW: http://milter-manager.sourceforge.net/
>
>
>
> ---
>
> Sent from sourceforge.net because you indicated interest in 
> 
>
>
>
> To unsubscribe from further messages, please visit 
> 


Am 19.03.18 um 08:35 schrieb Kurt Jaeger:

Hi!

> I'm most certain you did, but just to be safe: are you sure you used the
> updated version 2.1.1 / patch from Yasuhiro? Cause the changes of
> Yasuhiro did not reflect for my poudriere when it pulled the latest
> ports tree. If you applied the changes manually to your poudriere, how
> did you do this?

I have a svn checkout of the ports, updated that version, then
copied the milter files to the poudriere ports tree I use
to do testbuilds.

The build version was used to upgrade a testbox:

pkg info  | grep milter
milter-manager-2.1.1   Super milter that can invoke several milters selectively

-- p...@opsec.eu +49 171 3101372 2 years to go !

Am 19.03.18 um 00:07 schrieb Yasuhiro KIMURA:

From: Leander Schäfer 
Subject: Re: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Date: Sun, 18 Mar 2018 17:41:06 +0200

> I was trying to re-build my poudriere package server. Unfortunately it
> did not reflect your changes after I updated the ports. Instead the
> current ports tree still holds milter-manager version 2.0.7. Is it
> commited yet?

No, It is not committed yet. So if you try tha patch you need to
manually download and apply it to your ports tree.

Best Regards.

---
Yasuhiro KIMURA




Am 19.03.18 um 00:03 schrieb Matthew D. Fuller:
> On Sun, Mar 18, 2018 at 08:10:14PM +0100 I heard the voice of
> Kurt Jaeger, and lo! it spake thus:
>> Tested it, seems to still dump core.
>>
>> Backtrace is at
>>
>> http://people.freebsd.org/~pi/logs/milter-backtrace.txt
> I recall trying to build it on ruby 2.4 on a server some time back
> (early last year?  It's been a while...) and it failed to even start
> up.  Went back to 2.3 and it's been solid since.  So I'd guess it's
> ruby version dependent.
>
>

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: FreeBSD 11.1-RELEASE - mail/milter-manager broken

2018-03-19 Thread Kurt Jaeger
Hi!

> unfortunately enforcing it this the global way, ruby 2.5 will break other 
> ports being built in this repo and not harmonize as desired. I was hoping for 
> something oldschool like in poudrier's 
> /usr/local/etc/poudriere.d/repo-make.conf:
> 
> .if ${CURDIR:M*/ports/mail/milter-manager}
> DEFAULT_VERSIONS+=ruby=2.5
> .endif

That looks almost correct.

If I had a repo for version, say 11.1 amd64, named 111, and
a default ports tree, I would create a ports tree for milter to test,
like this:

poudriere ports -p milt -c

Then I can create a

111-milt-make.conf

with this:

.if ${.CURDIR:M*/mail/milter-manager}
DEFAULT_VERSIONS+=ruby=2.5
.endif

and testbuild using:

poudriere bulk -T -p milt -j 111 mail/milter-manager

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


committer needed for new port sysutils/tmux23

2018-03-19 Thread Miroslav Lachman

I submitted this port 2017-11-15.
Can somebody commit it please?

sysutils/tmux23
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223685

We are using it on all our machines.

Kind regards
Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Committer needed for new port (databases/go-carbon)

2018-03-19 Thread Kurt Jaeger
Hi!

> Can someone take a look at
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226732 suggestions for
> improvements are welcome.

Done.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"