Re: SF mastersites

2017-10-27 Thread blubee blubeeme 
I literally copy the entire url and add it to master_sites and it doesn't
work!

what does [:tl] even mean here? There's nothing about it on the whole page:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html

SF ${PORTNAME:tl}/${PORTNAME:tl}/${PORTVERSION}
MASTER_SITES= SF/spacenav/files/spacenav%20library%20%28SDK%29/
DISTNAME= libspnav-${PORTVERSION}

=> libspnav-0.2.3.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch
https://downloads.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz
fetch:
https://downloads.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz:
Not Found
=> Attempting to fetch
https://cytranet.dl.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz
fetch:
https://cytranet.dl.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz:
Not Found
=> Attempting to fetch
https://excellmedia.dl.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz

still giving me not found errors!


On Sat, Oct 28, 2017 at 1:06 PM, blubee blubeeme 
wrote:

> These SF mater_sites give me a real tough time trying to figure it out and
> try to find github mirrors whenever possible but I need to figure this out.
>
> I'm trying to download: https://sourceforge.net/projects/spacenav/
>
> PORTNAME= freespacenav
> PORTVERSION= 0.2.3
>
> MASTER_SITES= SF/spacenav
> DISTNAME= libspnav-${PORTVERSION}
>
> I would think the version above would work since it leads to:
> https://downloads.sourceforge.net/project/spacenav/libspnav-0.2.3.tar.gz
>
> but that doesn't work!
>
> The documentation on: https://www.freebsd.org/
> doc/en/books/porters-handbook/makefile-distfiles.html
> 5.4.2.2. Magic MASTER_SITES Macros
> also leaves me more confused that relieved.
>
> Can anyone help me sort this out?
>
___
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"

SF mastersites

2017-10-27 Thread blubee blubeeme 
These SF mater_sites give me a real tough time trying to figure it out and
try to find github mirrors whenever possible but I need to figure this out.

I'm trying to download: https://sourceforge.net/projects/spacenav/

PORTNAME= freespacenav
PORTVERSION= 0.2.3

MASTER_SITES= SF/spacenav
DISTNAME= libspnav-${PORTVERSION}

I would think the version above would work since it leads to:
https://downloads.sourceforge.net/project/spacenav/libspnav-0.2.3.tar.gz

but that doesn't work!

The documentation on:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html
5.4.2.2. Magic MASTER_SITES Macros
also leaves me more confused that relieved.

Can anyone help me sort this out?
___
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"

FreeBSD Port: samba46-4.6.8

2017-10-27 Thread Dutchman01 
Hello timor,

 

Would you please have a look and upgrade this port to 4.6.9 release please, 

it really has some nice bug fixes/patches.

 

Thanks for your contributions so far!

 

Regards,

Dutchman

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

Latest security/py-fail2ban (0.10.1_1) Broken Again.

2017-10-27 Thread Janky Jay, III 
Looks like the latest update broken more of the previously fixed issues.
Also, it appears that F2B 0.9.X is the latest stable and 0.10.X is
"experimental". Why is the default port experimental? Shouldn't this be
broken up into two ports?

Anywho, below is an example of the fail2ban.log output when an SSH
attempt should be banned (via PF):

2017-10-27 16:02:40,016 fail2ban.filter [17083]: INFO   
[bsd-ssh-pf] Found 174.135.101.80 - 2017-10-27 16:02:39
2017-10-27 16:02:42,286 fail2ban.filter [17083]: INFO   
[bsd-ssh-pf] Found 174.135.101.80 - 2017-10-27 16:02:41
2017-10-27 16:02:42,497 fail2ban.actions    [17083]: NOTICE 
[bsd-ssh-pf] Ban 174.135.101.80
2017-10-27 16:02:42,520 fail2ban.utils  [17083]: Level 39
8020c31c0 -- exec: pfctl -a f2b/ssh -sr | grep -q f2b-ssh
2017-10-27 16:02:42,521 fail2ban.utils  [17083]: ERROR  
8020c31c0 -- returned 1
2017-10-27 16:02:42,521 fail2ban.CommandAction  [17083]: ERROR  
Invariant check failed. Trying to restore a sane environment
2017-10-27 16:02:42,566 fail2ban.utils  [17083]: Level 39
8020b0870 -- exec: echo "table  persist counters" | pfctl -a
f2b/ssh -f-
echo "block quick proto tcp from  to any port {{3}}" |
pfctl -a f2b/ssh -f-
2017-10-27 16:02:42,567 fail2ban.utils  [17083]: ERROR  
8020b0870 -- stderr: 'stdin:1: syntax error'
2017-10-27 16:02:42,567 fail2ban.utils  [17083]: ERROR  
8020b0870 -- stderr: 'pfctl: Syntax error in config file: pf rules not
loaded'
2017-10-27 16:02:42,567 fail2ban.utils  [17083]: ERROR  
8020b0870 -- returned 1
2017-10-27 16:02:42,568 fail2ban.actions    [17083]: ERROR   Failed
to execute ban jail 'bsd-ssh-pf' action 'pf' info
'ActionInfo({'ipfailures': 42, 'ip-rev': '80.101.135.174.', 'family':
'inet4', 'ipmatches': 'FTP Server [12354] domain.org
[19/May/2016:20:02:35 -0600] "PASS (hidden)" 530\nFTP Server [12354]
domain.org [19/May/2016:20:02:54 -0600] "PASS (hidden)" 530\nFTP Server
[12354] domain.org [19/May/2016:20:02:35 -0600] "PASS (hidden)" 530\nFTP
Server [12354] domain.org [19/May/2016:20:02:54 -0600] "PASS (hidden)"
530\nFTP Server [12673] domain.org [19/May/2016:20:07:42 -0600] "PASS
(hidden)" 530\nFTP Server [12354] domain.org [19/May/2016:20:02:35
-0600] "PASS (hidden)" 530\nFTP Server [12354] domain.org
[19/May/2016:20:02:54 -0600] "PASS (hidden)" 530\nFTP Server [12673]
domain.org [19/May/2016:20:07:42 -0600] "PASS (hidden)" 530\nFTP Server
[12673] domain.org [19/May/2016:20:07:45 -0600] "PASS (hidden)" 530\nFTP
Server [12694] domain.org [19/May/2016:20:08:08 -0600] "PASS (hidden)"
530\nFTP Server [12694] domain.org [19/May/2016:20:08:14 -0600] "PASS
(hidden)" 530\nFTP Server [12673] domain.org [19/May/2016:20:07:45
-0600] "PASS (hidden)" 530\nFTP Server [12694] domain.org
[19/May/2016:20:08:08 -0600] "PASS (hidden)" 530\nFTP Server [12694]
domain.org [19/May/2016:20:08:14 -0600] "PASS (hidden)" 530\nFTP Server
[12869] domain.org [19/May/2016:20:14:01 -0600] "PASS (hidden)" 530\nFTP
Server [12869] domain.org [19/May/2016:20:14:06 -0600] "PASS (hidden)"
530\nFTP Server [12673] domain.org [19/May/2016:20:07:42 -0600] "PASS
(hidden)" 530\nFTP Server [12673] domain.org [19/May/2016:20:07:45
-0600] "PASS (hidden)" 530\nFTP Server [12694] domain.org
[19/May/2016:20:08:08 -0600] "PASS (hidden)" 530\nFTP Server [12694]
domain.org [19/May/2016:20:08:14 -0600] "PASS (hidden)" 530\nFTP Server
[12869] domain.org [19/May/2016:20:14:01 -0600] "PASS (hidden)" 530\nFTP
Server [12869] domain.org [19/May/2016:20:14:06 -0600] "PASS (hidden)"
530\nFTP Server [12881] domain.org [19/May/2016:20:14:30 -0600] "PASS
(hidden)" 530\nFTP Server [12881] domain.org [19/May/2016:20:14:38
-0600] "PASS (hidden)" 530\nFTP Server [12881] domain.org
[19/May/2016:20:14:30 -0600] "PASS (hidden)" 530\nFTP Server [12881]
domain.org [19/May/2016:20:14:38 -0600] "PASS (hidden)" 530\nFTP Server
[13000] domain.org [19/May/2016:20:17:14 -0600] "PASS (hidden)" 530\nFTP
Server [13000] domain.org [19/May/2016:20:17:22 -0600] "PASS (hidden)"
530\n2017-10-15 16:45:11,363 server1.domain-dos.org proftpd[48705]
server1 (domain.org[174.135.101.80]): USER user dick: no such user found
from domain.org [174.135.101.80] to 51.244.130.111:21\nFTP Server
[48705] domain.org [15/Oct/2017:16:45:11 +] "PASS (hidden)"
530\n2017-10-15 16:45:11,363 server1.domain-dos.org proftpd[48705]
server1 (domain.org[174.135.101.80]): USER user dick: no such user found
from domain.org [174.135.101.80] to 51.244.130.111:21\n2017-10-15
16:51:10,946 server1.domain-dos.org proftpd[48907] server1
(mail.domain.org[174.135.101.80]): USER derp: no such user found from
mail.domain.org [174.135.101.80] to 51.244.130.111:21\n2017-10-15
16:51:14,626 server1.domain-dos.org proftpd[48907] server1
(mail.domain.org[174.135.101.80]): USER dick: no such user found from
mail.domain.org [174.135.101.80] to 51.244.130.111:21\nOct 15 16:53:27
server1 sshd[48984]: Invalid user turd from 174.135.101.80\nOct 15
16:53:30 server1

Re: FreeBSD Port: sudo-1.8.21p2 - 1.8.21p2 SegFaults

2017-10-27 Thread Ryder Dain 
Can report tonight, also segfaults out-of-the-box in the vagrant vmdk provided 
at https://app.vagrantup.com/freebsd/boxes/FreeBSD-11.1-RELEASE.

```
root@:~ # uname -a ; pkg query "%v" sudo ; sudo -i
FreeBSD  11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug  9 11:55:48 
UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  
amd64
1.8.21p2
Segmentation fault
```

> On 10 Oct 2017, at 23:20, David P. Discher  wrote:
> 
> I’m going forward with 11.1-stable, and the 1.8.21p2 packages on 
> pkg.freebsd.org  also segfaults on bare metal.
> 
> --
> David P. Discher • d...@ixsystems.com
> Director, Information Technology
> iXsystems, Inc.
> Office: 408.943.4100 x150
> Mobile: 408.368.3725
> 
> 
>> On Oct 1, 2017, at 2:34 PM, David P. Discher  wrote:
>> 
>> Hi Renato & ports :
>> 
>> I was just stumble over this, with 12.0-CURRENT r323934, sudo 1.8.21p2 
>> SegFaults when run in a bhyve VM - however, seemly on bare metal, its fine.
>> 
>> sudo-1.8.20p2_3 runs just fine in bhyve VM.  There are all my own builds of 
>> 12- and ports (via poudriere).  I recompiled sudo on the Bhyve, and still 
>> had the same issue.
>> 
>> 
>> --
>> David P. Discher • d...@ixsystems.com
>> Director, Information Technology
>> iXsystems, Inc.
>> Office: 408.943.4100 x150
>> Mobile: 408.368.3725
>> 
>> 
> 

ºº–º––ºº–––ººº
Ryder Dain • Email rt...@columbia.edu



signature.asc
Description: Message signed with OpenPGP

Re: Upgrading www/gitea to 1.2.0

2017-10-27 Thread Stefan Bethke 
Am 15.10.2017 um 09:52 schrieb Stefan Bethke :
> 
> If you’r using the Gitea port, the update to 1.2.0 will require you to add a 
> new INTERNAL_TOKEN key to the security section. See 
> /usr/local/etc/gitea/conf/app.ini.sample for details. Gitea will not start 
> until this key is added to the configuration.
> 
> Gitea will try to add this key itself, but will fail if the app.ini file is 
> not writable by the gitea user, which is the default after installation.

Since a couple of people have run into this problem, here’s a bit more info:

Gitea has no daemon mode itself, so the port is using daemon(8) to run gitea as 
a daemon.  Also, gitea writes a lot of stuff to stdout while it’s running, even 
when you have configured logging through app.ini.  Up to and including version 
1.2.1 of the port, stdout and stderr are thrown away by daemon(8).

If gitea fails to start up using the port (i. e. you’re running 'service gitea 
start‘ and it’s not running afterwards), and there’s no log output in 
/var/log/gitea, you need to start it in the foreground.  You can use this 
command line:

# /usr/bin/env -i 'GITEA_WORK_DIR=/usr/local/share/gitea' 
'GITEA_CUSTOM=/usr/local/etc/gitea' 'HOME=/usr/local/git' 
'PATH=/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin' 'USER=git' 
/usr/local/sbin/gitea web

(as a single line)

This should produce error messages.  If the error message says that Gitea 
cannot write the config file, it is trying to add variables to the config file; 
the only known instance so far is the new INTERNAL_TOKEN variable.  Either 
allow Gitea to write the config file, or use app.ini.sample as a guide on where 
to add the INTERNAL_TOKEN variable, and how to produce the token value.

I’ve just submitted port version 1.2.2 to Bugzilla (#223283).  The rc script 
there will log Giteas output to syslog.  In a default configuration, the output 
should show up in /var/log/debug.log.


HTH,
Stefan

--
Stefan Bethke    Fon +49 151 14070811




signature.asc
Description: Message signed with OpenPGP

Re: Strange compiler error

2017-10-27 Thread blubee blubeeme 
Apologies, for forwarding the email to both lists.

I am trying to compile FreeCAD.

It seems FreeCAD uses a version of the SMESH framework but they bundle
their own and make changes to it, changes that cause the linker to go nuts
[for me] and won't link the program, so I get those strange errors.

The FreeCAD forum seems 'meh' when it comes to solving problems for any OS
other than Debian/Ubuntu, so i asked here hoping that some of the more
experienced members could assist.

On Fri, Oct 27, 2017 at 9:55 PM, Rares Aioanei  wrote:

> What *exactly* are you trying to do, what are the complete and precise
> steps and what are the errors? Not CC-ing freebsd-current@ as this
> looks like a ports issue.
>
> On Fri, Oct 27, 2017 at 3:08 PM, blubee blubeeme 
> wrote:
> > CMAKE_ARGS= -DFREECAD_USE_EXTERNAL_PIVY:BOOL=ON \
> > -DBUILD_QT5_WEBKIT:BOOL=OFF \
> > -DCMAKE_CXX_COMPILER=${LOCALBASE}/bin/mpicxx \
> >
> > BUILD_DEPENDS= pyside-rcc:devel/pyside-tools \
> > swig:devel/swig13 \
> > ${LOCALBASE}/libdata/pkgconfig/eigen3.pc:math/eigen3 \
> > ${LOCALBASE}/bin/mpicc:net/mpich2
> >
> > I've tried this but still no go, any ideas?
> > ___
> > freebsd-curr...@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@
> 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: Strange compiler error

2017-10-27 Thread Rares Aioanei 
What *exactly* are you trying to do, what are the complete and precise
steps and what are the errors? Not CC-ing freebsd-current@ as this
looks like a ports issue.

On Fri, Oct 27, 2017 at 3:08 PM, blubee blubeeme  wrote:
> CMAKE_ARGS= -DFREECAD_USE_EXTERNAL_PIVY:BOOL=ON \
> -DBUILD_QT5_WEBKIT:BOOL=OFF \
> -DCMAKE_CXX_COMPILER=${LOCALBASE}/bin/mpicxx \
>
> BUILD_DEPENDS= pyside-rcc:devel/pyside-tools \
> swig:devel/swig13 \
> ${LOCALBASE}/libdata/pkgconfig/eigen3.pc:math/eigen3 \
> ${LOCALBASE}/bin/mpicc:net/mpich2
>
> I've tried this but still no go, any ideas?
> ___
> freebsd-curr...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-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: FreeBSD Port: opensmtpd-5.9.2p1_3,1

2017-10-27 Thread Adam Weinberger 
> On 27 Oct, 2017, at 0:58, Herbert J. Skuhra  wrote:
> 
> On Fri, Oct 27, 2017 at 08:13:34AM +0200, Piotr Byliński wrote:
>> Hi,
>> Are there any plans or schedule to update Opensmtpd port to 6.0.2 version ?
>> Is it stable on FreeBSD for production ?
>> Thank you!
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213442

Thanks, Herbert.

OpenSMTPd broke all the filters in the 6.x line, and they've been
under a major project to rewrite the API. They anticipate having the
new interface ready by about the end of the year, or sometime after
that. Until then, updating will break a lot of ports.

Dima, it might be worth considering forking off mail/opensmtpd to
mail/opensmtpd5 and making the filters depend on that version instead.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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"

FreeBSD ports you maintain which are out of date

2017-10-27 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
+-+
devel/aws-sdk-cpp   | 1.2.16  | 1.2.25
+-+


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"

Re: Spam on -ports

2017-10-27 Thread Adam Weinberger 
> On 26 Oct, 2017, at 16:32, Dave Horsfall  wrote:
> 
> On Thu, 26 Oct 2017, Adam Weinberger wrote:
> 
>> You can opt out of spam by sending "unsubscribe" to 
>> freebsd-ports-unsubscr...@freebsd.org.
> 
> So were you born a jerk, or did you have to work at it?

That about sums that up.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.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: strage compile error [with attachments]

2017-10-27 Thread blubee blubeeme 
The header file includes these headers:
//  SMESH SMESH : implementaion of SMESH idl descriptions
//  File   : SMESH_Algo.cxx
//  Author : Paul RASCLE, EDF
//  Module : SMESH

#include "SMESH_Algo.hxx"

#include "SMDS_EdgePosition.hxx"
#include "SMDS_FacePosition.hxx"
#include "SMDS_MeshElement.hxx"
#include "SMDS_MeshNode.hxx"
#include "SMDS_VolumeTool.hxx"
#include "SMESHDS_Mesh.hxx"
#include "SMESHDS_SubMesh.hxx"
#include "SMESH_Comment.hxx"
#include "SMESH_Gen.hxx"
#include "SMESH_HypoFilter.hxx"
#include "SMESH_Mesh.hxx"
#include "SMESH_MeshAlgos.hxx"
#include "SMESH_TypeDefs.hxx"
#include "SMESH_subMesh.hxx"

#include 

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 

#include "utilities.h"

#include 
#include 
#include "SMESH_ProxyMesh.hxx"
#include "SMESH_MesherHelper.hxx"
#include 
using namespace std;

I don't really see anything that would cause such errors..

On Fri, Oct 27, 2017 at 8:24 PM, blubee blubeeme 
wrote:

> error:
> FAILED: lib/libSMESH.so
> : && /usr/bin/c++  -fPIC -Wall -Wextra -Wno-write-strings -O2 -pipe
> -fstack-protector -isystem /usr/local/include -fno-strict-aliasing
>  -isystem /usr/local/include -std=c++11 -Wno-undefined-var-template
> -D_OCC64 -Wno-sign-compare -Wno-reorder -Wno-switch -Wno-unused-variable
> -Wno-unused-private-field -Wno-unused-function -Wno-sometimes-uninitialized
> -Wno-overloaded-virtual -Wno-dynamic-class-memaccess -Wno-comment
> -Wno-unused-parameter -Wno-self-assign -Wno-reorder -Wno-switch-enum
> -Wno-unknown-pragmas -Wno-logical-op-parentheses -Wno-unused-variable
> -Wno-unused-function -Wno-overloaded-virtual -O2 -pipe -fstack-protector
> -isystem /usr/local/include -fno-strict-aliasing  -isystem
> /usr/local/include  -Wl,--no-undefined -shared -Wl,-soname,libSMESH.so -o
> lib/libSMESH.so 
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/libmesh.c.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverGMF.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverGMF_Read.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverGMF_Write.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverMED_Family.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/
> SMESH/DriverMED_R_SMESHDS_Mesh.cpp.o src/3rdParty/salomesmesh/
> CMakeFiles/SMESH.dir/src/SMESH/DriverMED_W_Field.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/
> SMESH/DriverMED_W_SMESHDS_Mesh.cpp.o src/3rdParty/salomesmesh/
> CMakeFiles/SMESH.dir/src/SMESH/GEOMUtils.cpp.o src/3rdParty/salomesmesh/
> CMakeFiles/SMESH.dir/src/SMESH/MED_Algorithm.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_CoordUtils.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Factory.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_GaussDef.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_GaussUtils.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Structures.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Utilities.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_V2_2_Wrapper.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Wrapper.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Algo.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Block.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Exception.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Gen.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Group.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_HypoFilter.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Hypothesis.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Mesh.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MeshAlgos.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MeshEditor.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MeshVSLink.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MesherHelper.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Octree.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_OctreeNode.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Pattern.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_ProxyMesh.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_TryCatch.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_subMesh.cpp.o
> src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/
> SMESH/Utils_ExceptHandlers.cpp.o src/3rdParty/salomesmesh/
> CMakeFiles/SMESH.dir/src/Controls/SMESH_Controls.cpp.o
>

strage compile error [with attachments]

2017-10-27 Thread blubee blubeeme 
error:
FAILED: lib/libSMESH.so
: && /usr/bin/c++  -fPIC -Wall -Wextra -Wno-write-strings -O2 -pipe
-fstack-protector -isystem /usr/local/include -fno-strict-aliasing
 -isystem /usr/local/include -std=c++11 -Wno-undefined-var-template
-D_OCC64 -Wno-sign-compare -Wno-reorder -Wno-switch -Wno-unused-variable
-Wno-unused-private-field -Wno-unused-function -Wno-sometimes-uninitialized
-Wno-overloaded-virtual -Wno-dynamic-class-memaccess -Wno-comment
-Wno-unused-parameter -Wno-self-assign -Wno-reorder -Wno-switch-enum
-Wno-unknown-pragmas -Wno-logical-op-parentheses -Wno-unused-variable
-Wno-unused-function -Wno-overloaded-virtual -O2 -pipe -fstack-protector
-isystem /usr/local/include -fno-strict-aliasing  -isystem
/usr/local/include  -Wl,--no-undefined -shared -Wl,-soname,libSMESH.so -o
lib/libSMESH.so
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/libmesh.c.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverGMF.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverGMF_Read.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverGMF_Write.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverMED_Family.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverMED_R_SMESHDS_Mesh.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverMED_W_Field.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/DriverMED_W_SMESHDS_Mesh.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/GEOMUtils.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Algorithm.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_CoordUtils.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Factory.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_GaussDef.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_GaussUtils.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Structures.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Utilities.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_V2_2_Wrapper.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/MED_Wrapper.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Algo.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Block.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Exception.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Gen.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Group.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_HypoFilter.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Hypothesis.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Mesh.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MeshAlgos.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MeshEditor.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MeshVSLink.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_MesherHelper.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Octree.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_OctreeNode.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_Pattern.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_ProxyMesh.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_TryCatch.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/SMESH_subMesh.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/SMESH/Utils_ExceptHandlers.cpp.o
src/3rdParty/salomesmesh/CMakeFiles/SMESH.dir/src/Controls/SMESH_Controls.cpp.o
 
-Wl,-rpath,/usr/ports/cad/Freecad/work/.build/lib:/usr/local/lib:/usr/local/lib/vtk-6.2:
lib/libDriverSTL.so lib/libDriverDAT.so lib/libDriverUNV.so
/usr/local/lib/libmedC.so /usr/local/lib/libmed.so -lz
/usr/local/lib/libexpat.so lib/libSMESHDS.so lib/libSMDS.so
/usr/local/lib/vtk-6.2/libvtkFiltersVerdict-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkverdict-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkIOXML-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkIOGeometry-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkjsoncpp-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkIOXMLParser-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkIOLegacy-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkIOCore-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkFiltersExtraction-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkFiltersStatistics-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkImagingFourier-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkImagingCore-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkalglib-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkFiltersSources-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkFiltersGeneral-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkCommonComputationalGeometry-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkFiltersGeometry-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkFiltersCore-6.2.so.1
/usr/local/lib/vtk-6.2/libvtkCommonExecutionModel-6.2.so.1

Re: Spam on -ports

2017-10-27 Thread Matthias Apitz 
Every now and then some single SPAM is passing through freebsd-* lists and
always the mails generated and folks moaning are a lot more than just
this single SPAM mail. Why people can not juster filter those mails
away, for example with SpamAssassin (as I do), or just silently hit the
DEL or whatever button is in your MUA for this purpose.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8. Mai 1945: Wer nicht feiert hat den Krieg verloren.
8 de mayo de 1945: Quien no festeja perdió la Guerra.
May 8, 1945: Who does not celebrate lost the War.


signature.asc
Description: PGP signature

Strange compiler error

2017-10-27 Thread blubee blubeeme 
CMAKE_ARGS= -DFREECAD_USE_EXTERNAL_PIVY:BOOL=ON \
-DBUILD_QT5_WEBKIT:BOOL=OFF \
-DCMAKE_CXX_COMPILER=${LOCALBASE}/bin/mpicxx \

BUILD_DEPENDS= pyside-rcc:devel/pyside-tools \
swig:devel/swig13 \
${LOCALBASE}/libdata/pkgconfig/eigen3.pc:math/eigen3 \
${LOCALBASE}/bin/mpicc:net/mpich2

I've tried this but still no go, any ideas?
___
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"

science/udunits2: Seg faults while deinstall and install

2017-10-27 Thread Rainer Hurling 
I tried to rebuild and reinstall science/udunits2 on a box with recent 
HEAD amd64 and it gives me some errors while deinstalling and reinstalling:



#make deinstall
===>  Deinstalling for udunits
===>   Deinstalling udunits-2.2.25
Updating database digests format: 100%
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 
packages in the universe):


Installed packages to be REMOVED:
udunits-2.2.25

Number of packages to be removed: 1
[1/1] Deinstalling udunits-2.2.25...
[1/1] Deleting files for udunits-2.2.25: 100%
Segmentation fault
Segmentation fault



#make reinstall
===>  Installing for udunits-2.2.25
===>   udunits-2.2.25 depends on executable: indexinfo - found
===>   udunits-2.2.25 depends on shared library: libexpat.so - found 
(/usr/local/lib/libexpat.so)

===>   Registering installation for udunits-2.2.25
Installing udunits-2.2.25...
Segmentation fault
Segmentation fault


Is this a known issue? Any ideas and/or help would be really 
appreciated. Thanks in advance.


Best wishes,
Rainer Hurling
___
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"

Commit request: www/madsonic: Update to 6.2.9040 (Latest stable release)

2017-10-27 Thread Hiroki Tagato 

Hi ports committers,

Could someone pick up the following PR to commit to the tree?

Bug 223181 - www/madsonic: Update to 6.2.9040 (Latest stable release)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223181

Changes are:
- A patch to update www/madsonic to 6.2.9040 (latest stable release)
- Replace exec/unexec with postexec/postunexec

Already got an approval from the maintainer.

Thanks,
Hiroki Tagato
___
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: Spam on -ports

2017-10-27 Thread David Wolfskill 
On Fri, Oct 27, 2017 at 11:13:20AM +0200, Jan Bramkamp wrote:
> ...
> I would like to help fighting the spam problem on the FreeBSD.org 
> mailing lists. Can you put me in contact with the right people?
> 
> -- Jan Bramkamp

 would be the appropriate email address -- both
for offers of help and pointing out perceived issues (whether it's the
existence of spam, problems sending mail to a list, or just about
anything involving the email infrastructure at FreeBSD.org).

Peace,
david   (who has worn that hat, but is handing it off to others)
-- 
David H. Wolfskill  da...@catwhisker.org
Unsubstantiated claims of "Fake News" are evidence that the claimant lies again.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Spam on -ports

2017-10-27 Thread Jan Bramkamp 

On 27.10.17 01:24, Mark Linimon wrote:

On Fri, Oct 27, 2017 at 07:50:40AM +1100, Dave Horsfall wrote:

Is it official FreeBSD policy to allow spammers free reign on this
list, or is the list owner merely incompetent?

or is it 3) spam is a never-ending arms race, and the volunteers are
struggling to keep up?
It is and low latency human moderation of all mailinglists is an 
unrealistic expectation.

Honestly, I do not understand why people make posts like this.
Most precise low maintenance spam filtering works on meta that gets 
mangled too badly by mailing lists to be usable afterwards. From the 
point of view of spam filters the messages relayed by the mailing list 
originate in from a valid MX of freebsd.org. Combining a strict postfix 
setup with postscreen and postgrey solved the spam problem for my 
domains with one exception: the FreeBSD mailing lists. To keep the 
signal to noise ratio on those acceptable I had to deploy a content 
based spam filter and have not yet found a good enough configuration for 
it. While not fair it is very tempting to blame the operators and I'm 
surprised how some spam campaigns manage to get unchanged content 
relayed through the FreeBSD mailing lists for months.

Speaking as someone who, behind the scenes, helps people try to stay
motivated, all you're doing is make other people's lives miserable --
including mine.
I would like to help fighting the spam problem on the FreeBSD.org 
mailing lists. Can you put me in contact with the right people?


-- Jan Bramkamp
___
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: Spam on -ports

2017-10-27 Thread Sijmen J. Mulder 

Hi all,

Op 27-10-2017 om 08:56 schreef Thomas Mueller:

I believe spam is filtered by software, a spam-suspicious message is sent to 
the moderator.

Spam filters should not filter out good messages, thus some spam gets through.

But freebsd-questions seems to get the most spam of all FreeBSD emailing lists, 
much more than freebsd-ports..


I do mind the spam here and especially on -questions but I just wanted 
to say that I really appreciate the work of the volunteers behind these 
lists.


Sijmen
___
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: Spam on -ports

2017-10-27 Thread Thomas Mueller 
> On 26 Oct, 2017, at 14:50, Dave Horsfall  wrote:

> Is it official FreeBSD policy to allow spammers free reign on this list, or 
> is the list owner merely incompetent?

I believe spam is filtered by software, a spam-suspicious message is sent to 
the moderator. 

Spam filters should not filter out good messages, thus some spam gets through.

But freebsd-questions seems to get the most spam of all FreeBSD emailing lists, 
much more than freebsd-ports..

Tom

___
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 Port: opensmtpd-5.9.2p1_3,1

2017-10-27 Thread Herbert J. Skuhra 
On Fri, Oct 27, 2017 at 08:13:34AM +0200, Piotr Byliński wrote:
> Hi,
> Are there any plans or schedule to update Opensmtpd port to 6.0.2 version ?
> Is it stable on FreeBSD for production ?
> Thank you!

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

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

FreeBSD Port: opensmtpd-5.9.2p1_3,1

2017-10-27 Thread Piotr Byliński 
Hi,
Are there any plans or schedule to update Opensmtpd port to 6.0.2 version ?
Is it stable on FreeBSD for production ?
Thank you!


Best regads,
Piotr Byliński



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