FreeBSD ports you maintain which are out of date

[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
+-+
lang/sbcl   | 1.3.1   | 1.3.8
+-+
net/abills  | 0.59| 0.74
+-+
www/phpmustache | 2.10.0  | v2.11.1
+-+


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"

emulators/virtualbox-ose build failure

[Matthias Petermann (Business)]

Hello,

during the last build of my custom package repository I did experience a
strange issue. I am using Synth, the build host is running FreeBSD
10.3/amd64. For the last build run, I receive an error:

In file included from
/construction/xports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/recompiler/cpu-exec.c:30:
/construction/xports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/recompiler/target-i386/exec.h:41:30:
error: global register variables are not supported
register struct CPUX86State *env asm(AREG0);
 ^
(the full log is available in (1)). The closest I could find is stated
in a posting from 2012 (2) where a similiar issue from seems to occur
when Virtualbox is compiled with clang and not gcc. Not sure is this
still applies today but Makefile seems still to refer --with-gcc.

Some observations:
* the build issue started when I included multimedia/kdenlive to the
to-be-built port list
* both ports (kdenlive and virtualbox-ose) share the Qt4 dependency
* synth is building each port in a clean chroot, builds dependencies
first and does a pkg install for them in the clean chroot where
virtualbox-ose is built
* kdenlive is built in order before virtualbox-ose, so Qt4 dependency
build seems to be triggered from kdenlive

Has anyone on this list an idea what is going wrong here?

Thanks in advance & best regards,
Matthias


(1) https://dev.petermann-it.de/nextcloud/index.php/s/RpnDYYiyYSCjenb
(2) http://osdir.com/ml/freebsd-emulation/2012-04/msg00108.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: emulators/virtualbox-ose build failure

[Bernhard Fröhlich]

On Mon, Aug 1, 2016 at 1:47 PM, Matthias Petermann (Business)
 wrote:
> Hello,
>
> during the last build of my custom package repository I did experience a
> strange issue. I am using Synth, the build host is running FreeBSD
> 10.3/amd64. For the last build run, I receive an error:
>
> In file included from
> /construction/xports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/recompiler/cpu-exec.c:30:
> /construction/xports/emulators/virtualbox-ose/work/VirtualBox-5.0.26/src/recompiler/target-i386/exec.h:41:30:
> error: global register variables are not supported
> register struct CPUX86State *env asm(AREG0);
>  ^
> (the full log is available in (1)). The closest I could find is stated
> in a posting from 2012 (2) where a similiar issue from seems to occur
> when Virtualbox is compiled with clang and not gcc. Not sure is this
> still applies today but Makefile seems still to refer --with-gcc.
>
> Some observations:
> * the build issue started when I included multimedia/kdenlive to the
> to-be-built port list
> * both ports (kdenlive and virtualbox-ose) share the Qt4 dependency
> * synth is building each port in a clean chroot, builds dependencies
> first and does a pkg install for them in the clean chroot where
> virtualbox-ose is built
> * kdenlive is built in order before virtualbox-ose, so Qt4 dependency
> build seems to be triggered from kdenlive
>
> Has anyone on this list an idea what is going wrong here?
>
> Thanks in advance & best regards,
> Matthias
>
>
> (1) https://dev.petermann-it.de/nextcloud/index.php/s/RpnDYYiyYSCjenb
> (2) http://osdir.com/ml/freebsd-emulation/2012-04/msg00108.html

The automated FreeBSD package building with poudriere produced the same error
last night for FreeBSD 10.3.

Since about a year the port uses a mixture of clang and gcc because clang does
not support global register variables. On the other side building all
ports with clang
but only vbox with gcc created issues in KDE.

The result are a couple of patches from jkim which are not supported
at all but use
both compilers in a mix. Might be they need to be fixed after the
update to vbox 5.0.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
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"

security/openvpn build failure on 12-CURRENT/amd64

[Shawn Webb]

Hey All,

It looks like security/openvpn fails to build on 12-CURRENT/amd64 on
both FreeBSD's and HardenedBSD's build infrastructure. I've verified
that it builds fine on latest 11-STABLE/amd64. Would this be a
regression in 12-CURRENT?

Log file from FreeBSD's build:
http://beefy4.nyi.freebsd.org/data/head-amd64-default/p419204_s303419/logs/errors/openvpn-2.3.11.log

Thanks,

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature

Re: security/openvpn build failure on 12-CURRENT/amd64

[Shawn Webb]

On Mon, Aug 01, 2016 at 02:26:39PM +, Matthias Andree wrote:
> Hi Shawn,
> 
> The compilation attempt was done on an invalid configuration and has zero 
> relevance whatsoever. As the log says:
> 
> !!! Jail is newer than host. (Jail: 121, Host: 1100116) !!! 
> !!! This is not supported. !!! 
> !!! Host kernel must be same or newer than jail. !!! 
> !!! Expect build failures. !!!
> 
> I wish the builders would stop even trying to build a package on a kernel 
> that is too old, it's just confusing and wasteful.
> 

Hey Matthias,

HardenedBSD's kernel and world matched and still had the very same
build error.

Here's the build log: http://pastebin.com/TEBih1Sx

Thanks,

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

GPG Key ID:  0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE


signature.asc
Description: PGP signature

Re: security/openvpn build failure on 12-CURRENT/amd64

[Matthias Andree]

Hi Shawn,

The compilation attempt was done on an invalid configuration and has zero 
relevance whatsoever. As the log says:

!!! Jail is newer than host. (Jail: 121, Host: 1100116) !!! 
!!! This is not supported. !!! 
!!! Host kernel must be same or newer than jail. !!! 
!!! Expect build failures. !!!

I wish the builders would stop even trying to build a package on a kernel that 
is too old, it's just confusing and wasteful.

Am 1. August 2016 16:08:04 MESZ, schrieb Shawn Webb 
:
>Hey All,
>
>It looks like security/openvpn fails to build on 12-CURRENT/amd64 on
>both FreeBSD's and HardenedBSD's build infrastructure. I've verified
>that it builds fine on latest 11-STABLE/amd64. Would this be a
>regression in 12-CURRENT?
>
>Log file from FreeBSD's build:
>http://beefy4.nyi.freebsd.org/data/head-amd64-default/p419204_s303419/logs/errors/openvpn-2.3.11.log
>
>Thanks,
>
>-- 
>Shawn Webb
>Cofounder and Security Engineer
>HardenedBSD
>
>GPG Key ID:  0x6A84658F52456EEE
>GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE
___
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: security/openvpn build failure on 12-CURRENT/amd64

[Ngie Cooper]

On Mon, Aug 1, 2016 at 7:31 AM, Shawn Webb  wrote:

...

> HardenedBSD's kernel and world matched and still had the very same
> build error.
>
> Here's the build log: http://pastebin.com/TEBih1Sx

Confirmed -- why's it looking for tcp6local/udp6local though (this
isn't a valid protocol, and for some odd reason it's being picked up
from the sample config file..?)? Looks like a port bug...
Thanks,
-Ngie

$ sudo make -C /usr/ports/security/openvpn build
...
PASS: t_lpback.sh
The following test will take about two minutes.
If the addresses are in use, this test will retry up to two times.
Options error: Bad protocol: 'udp6local'.  Allowed protocols with
--proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client]
[tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6]
Use --help for more information.
Options error: Bad protocol: 'udp6local'.  Allowed protocols with
--proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client]
[tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6]
Use --help for more information.
FAIL: t_cltsrv.sh

1 of 2 tests failed
(1 test was not run)
Please report to openvpn-us...@lists.sourceforge.net

*** [check-TESTS] Error code 1
$ grep -r udp6local work/
work/openvpn-2.3.11/sample/sample-config-files/loopback-client.test:proto
udp6local ::1
work/openvpn-2.3.11/sample/sample-config-files/loopback-server.test:proto
udp6local ::1
___
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: security/openvpn build failure on 12-CURRENT/amd64

[Michael Butler]

On 08/01/16 16:53, Ngie Cooper wrote:
> On Mon, Aug 1, 2016 at 7:31 AM, Shawn Webb  wrote:
> 
>> HardenedBSD's kernel and world matched and still had the very same
>> build error.
>>
>> Here's the build log: http://pastebin.com/TEBih1Sx
> 
> Confirmed -- why's it looking for tcp6local/udp6local though (this
> isn't a valid protocol, and for some odd reason it's being picked up
> from the sample config file..?)? Looks like a port bug...
> Thanks,
> -Ngie

Built just fine for me today on AMD64 "FreeBSD 12.0-CURRENT #165
r303601: Sun Jul 31 20:34:50 EDT 2016",

imb

___
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: skkinput3 failed in gcc

[KIRIYAMA Kazuhiko]

At Thu, 28 Jul 2016 07:05:32 +0200,
Jan Beich wrote:
> 
> KIRIYAMA Kazuhiko  writes:
> 
> > japanese/skkinput3 failed in gcc[1] with environments:
> [...]
> > In file included from 
> > /var/ports/basejail/usr/ports/lang/gcc/work/gcc-4.8.5/gcc/gencheck.c:23:
> > In file included from ./tm.h:16:
> > ./options.h:4293:3: error: redefinition of enumerator 'OPT_C'
> >   OPT_C = 129,   /* -C */
> >   ^
> > ./options.h:4290:3: note: previous definition is here
> >   OPT_C = 126,   /* -C */
> >   ^
> > ./options.h:4301:3: error: redefinition of enumerator 'OPT_d'
> >   OPT_d = 137,   /* -d */
> >   ^
> [...]
> > gmake[5]: *** [Makefile:3840: build/gencheck.o] エラー 1
> > gmake[5]: *** 未完了のジョブを待っています
> 
> See workaround in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210122

Thankx! `make LC_COLLATE=C install' done no problems, but 

kiri@smtp:~[1026]% skkinput3 -server 192.168.2.1
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Value in failed request:  0x40
  Serial number of failed request:  36
  Current serial number in output stream:  37
kiri@smtp:~[1027]%  

This may be my graphic card specific problems?

---
KIRIYAMA Kazuhiko
___
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: security/openvpn build failure on 12-CURRENT/amd64

[Matthias Andree]

Hi Ngie,

Quite possibly an incompatibility between the port or the upstream software 
build/self-test rigging with the rather new FreeBSD 12-CURRENT. Since I do not 
have the latter, I am soliciting patches (through Bugzilla).

I am staring at 

 ff. and it does not make sense to me that or why it is failing. I am wondering 
if it is something specific to 12-CURRENT that does additional patching, or if 
sed(1) behaves in a different way. Insights welcome.

Cheers,
Matthias 

Am 1. August 2016 22:53:47 MESZ, schrieb Ngie Cooper :
>On Mon, Aug 1, 2016 at 7:31 AM, Shawn Webb 
>wrote:
>
>...
>
>> HardenedBSD's kernel and world matched and still had the very same
>> build error.
>>
>> Here's the build log: http://pastebin.com/TEBih1Sx
>
>Confirmed -- why's it looking for tcp6local/udp6local though (this
>isn't a valid protocol, and for some odd reason it's being picked up
>from the sample config file..?)? Looks like a port bug...
>Thanks,
>-Ngie
>
>$ sudo make -C /usr/ports/security/openvpn build
>...
>PASS: t_lpback.sh
>The following test will take about two minutes.
>If the addresses are in use, this test will retry up to two times.
>Options error: Bad protocol: 'udp6local'.  Allowed protocols with
>--proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client]
>[tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6]
>Use --help for more information.
>Options error: Bad protocol: 'udp6local'.  Allowed protocols with
>--proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client]
>[tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6]
>Use --help for more information.
>FAIL: t_cltsrv.sh
>
>1 of 2 tests failed
>(1 test was not run)
>Please report to openvpn-us...@lists.sourceforge.net
>
>*** [check-TESTS] Error code 1
>$ grep -r udp6local work/
>work/openvpn-2.3.11/sample/sample-config-files/loopback-client.test:proto
>udp6local ::1
>work/openvpn-2.3.11/sample/sample-config-files/loopback-server.test:proto
>udp6local ::1
___
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: [SOLVED] Segfault in OpenSSL even though ports GnuTLS demanded (irssi and loudmouth)

[Julian Elischer]

On 2/08/2016 5:16 AM, Bertram Scharpf wrote:

On Thursday, 28. Jul 2016, 17:56:46 -0400, Jung-uk Kim wrote:

On 07/28/16 05:37 PM, Bertram Scharpf wrote:

On Thursday, 28. Jul 2016, 15:37:00 -0400, Jung-uk Kim wrote:

On 07/28/16 02:02 PM, Bertram Scharpf wrote:

   Program received signal SIGSEGV, Segmentation fault.
   [Switching to Thread 29403080 (LWP 101275/mcabber)]
   0x285c1245 in OPENSSL_ia32_cpuid () from /usr/local/lib/libcrypto.so.8

Try "ldd /usr/local/lib/libloudmouth-1.so.0.1.0".  It looks like a
Kerberos issue.

So, how could I resolve this?

You may ask its maintainer (gn...@freebsd.org) to add USES+=gssapi and
add an option to select GSS-API from ports.

I looked at the other 4(!) projects that set something like
USES+=gssapi and copied that to loudmouth, and I even had to
copy it to irssi. Now the segfault has gone away.

The patch is below.

I will not write a problem report as long as my running
problem reports aren't deemed worthy of an answer.what Are your current reports?


hmmm  do I sense frustration? :-/

Please DO at least drop it into a bug report..
what are your other bug reports?  I find the best way to get bug 
reports handled is to look in the history of the module concerned,

e.g. https://svnweb.freebsd.org/ports/head/irc/irssi/
 or 
https://svnweb.freebsd.org/ports/head/net-im/loudmouth/Makefile?view=log


and see who has been working on it recently and email them directly 
with a pointer to the bug


The bad part of how the project works is that there is no "manager" 
correlating bugs with people directly, so it's really easy to miss bug 
reports that you should be aware of.


In this case I've cc'd the people who may best be able to evaluate 
your patch, and since it is simple and you've done he work one hopes 
that one of them  will be able to comment and maybe even commit.


Julian



Bertram




diff --git a/irc/irssi/Makefile b/irc/irssi/Makefile
index d9a89fe..f7f9e45 100644
--- a/irc/irssi/Makefile
+++ b/irc/irssi/Makefile
@@ -43,6 +43,7 @@ TRUECOLOR_CONFIGURE_ENABLE=   true-color
  CONFIGURE_ARGS+=   --disable-ssl
  .else
  USE_OPENSSL=   yes
+USES+=gssapi:base,flags
  .endif

  post-patch:
diff --git a/net-im/loudmouth/Makefile b/net-im/loudmouth/Makefile
index ead1d4e..0a86d13 100644
--- a/net-im/loudmouth/Makefile
+++ b/net-im/loudmouth/Makefile
@@ -29,6 +29,8 @@ OPTIONS_DEFAULT=GNUTLS
  OPTIONS_RADIO= SSL
  OPTIONS_RADIO_SSL= GNUTLS OPENSSL

+USES+=gssapi:base,flags
+
  .include 

  .if ${PORT_OPTIONS:MGNUTLS}




___
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: blender and cycles engine

[Shane Ambler]

On 31/07/2016 09:12, Stari Karp wrote:

Hi!

The new Blender 2.77a is in the ports which has many improvement
related to the Cycles engine but  on my system FreeBSD 10.3-RELEASE
(amd64) is still not possible to run Blender with Cycles option on. It
build but Blender doesn't start:
blender
Assertion failed: (findOption(Name) == Values.size() && "Option already
exists!"), function addLiteralOption, file
/construction/xports/devel/llvm37/work/llvm-
3.7.1.src/include/llvm/Support/CommandLine.h, line 698.
Abort (core dumped)


What do you have installed that uses llvm37?

When blender is built using CYCLESOSL it uses llvm34 which could be the
reason for the conflict.

If you are building with CYCLES and not CYCLESOSL then it shouldn't
need llvm34 but you may have two ports that blender depends on that
have been built using different llvm versions.

What ports are listed with -
pkg info -rx 'llvm3[47]'


--
FreeBSD - the place to B...Software Developing

Shane Ambler

___
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"

Fwd: ipfw divert filter for IPv4 geo-blocking (port?)

[Julian Elischer]

Is there a ports committer who could take this in?
Since this announcement, he's made several fixes and enhancements, 
including the ability

to directly populate ipfw tables with country ranges etc.

Very useful, and we should have it in ports, probably in net-mgmt/
I've kicked the tires and it performs as advertised .

The Makefiles work well for installing on FreeBSD-current and 11 but 
someone who knows ports makefiles better than I could probably knock 
up a port for it in about 3 minutes flat.


I'm not sure what name he would like it to go under..  the geoip 
program (which I find more interesting) came later,

but as a better name I think.
Can we import directly from github?  do we keep a copy in our cache if 
we do? (I guess we could get the zip file..)



Julian

 Forwarded Message 

I have written a ipfw divert filter daemon for IPv4 geo-blocking. It is working 
flawlessly on two server installations since a week.

Anyway, I am still in doubt whether I do the blocking in the correct way. Once 
the filter receives a packet from the respective divert socket it looks up the 
country code of the source IP in the IP-Ranges database, and if the country 
code shall be allowed then it returns the unaltered packet via said socket, 
otherwise, the filter does no further processing, so the packet is effectively 
gone, lost, dropped, discarded, or whatever would be the correct terminology. 
Is this the really the correct way of denying a packet, or is it necessary to 
inform ipfw somehow about the circumstances, so it can run a proper dropping 
procedure?

I uploaded the filter + accompanying tools to GitHub

   https://github.com/cyclaero/ipdb

Many thnaks for any advices in advance.

Best regards

Rolf

 
___

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

___
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: Fwd: ipfw divert filter for IPv4 geo-blocking (port?)

[Kurt Jaeger]

Hi!

> Is there a ports committer who could take this in?

If someone prepares a PR with a port, I can have a look at it.

-- 
p...@opsec.eu+49 171 3101372 4 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: Fwd: ipfw divert filter for IPv4 geo-blocking (port?)

[Kurt Jaeger]

Hi!

> Is there a ports committer who could take this in?

Btw, any chance to extend it to IPv6, as well ?

-- 
p...@opsec.eu+49 171 3101372 4 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"