net/samba-libsmbclient depends on complete outdated samba36

2016-06-16 Thread Matthias Fechner
Dear all, I just testing the www/nextcloud port that was commited yesterday, thanks a lot for this! There I saw that samba36 will be installed (in addition to samba43). I think the problem is located in port net/samba-libsmbclient which refers to: SAMBA_PORT= samba36 SAMBA_SUBPORT=

Re: openssl-1.0.2.13

2016-06-16 Thread Dirk Meyer
Hallo Gerard Seibert, > I have a question regarding "openssl-1.0.2.13". Since the port is > marked as "vulnerable", I was wondering if there is any idea when a > corrected port will be released? openssl-1.0.2.13 is the fixed port. > Also, according to the documentation on > https://vuxml.FreeBSD

Weird error from pkg-fallout

2016-06-16 Thread Montgomery-Smith, Stephen
I am getting messages from pkg-fallout saying that the port cad/gmsh does not build. See here: http://beefy3.nyi.freebsd.org/data/head-i386-default/p416942_s301941/logs/gmsh-2.12.0.log The main error it seems to report is this: *** Bad machine code: Using an undefined physical register *** Does

Re: USES=compiler:c++14-lang still adds -std=c++11 to CXXFLAGS

2016-06-16 Thread Yuri
On 06/16/2016 15:09, Mathieu Arnold wrote: Nothing in compiler.mk sets CXXSTD or CSTD, so it must be your software doing it. qmake is doing it. Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-port

Checking integrity... done (2 conflicting) when installing x11-wm/xfce4

2016-06-16 Thread Otacílio
Dears When I try install x11-wm/xfce4 on a FreeBSD11-ALPHA3 machine I get this error message: root@squitch:/usr/home/ota # pkg install x11-wm/xfce4 Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking integrity... done (2 conflict

Re: USES=compiler:c++14-lang still adds -std=c++11 to CXXFLAGS

2016-06-16 Thread Mathieu Arnold
+--On 16 juin 2016 10:20:22 -0700 Yuri wrote: | On 06/16/2016 08:57, Yuri wrote: |>> |>> Mmmm, maybe USE_CXXSTD=c++14. |> |> |> No, none of these helped. | | | Actually, USE_CXXSTD=c++14 does add -std=c++14, but it is cleared by the | subsequent -std=c++11 added by compiler:c++14-lang. |

Re: USES=compiler:c++14-lang still adds -std=c++11 to CXXFLAGS

2016-06-16 Thread Yuri
On 06/16/2016 08:57, Yuri wrote: Mmmm, maybe USE_CXXSTD=c++14. No, none of these helped. Actually, USE_CXXSTD=c++14 does add -std=c++14, but it is cleared by the subsequent -std=c++11 added by compiler:c++14-lang. So this is definitely a bug. https://bugs.freebsd.org/bugzilla/show_bug

Re: USES=compiler:c++14-lang still adds -std=c++11 to CXXFLAGS

2016-06-16 Thread Yuri
On 06/16/2016 05:25, Mathieu Arnold wrote: || What is wrong? I think this is a bug in /usr/ports/Mk/Uses/compiler.mk | | As far as I can see, you need to add USE_CSTD=c++14 to your port Makefile. Mmmm, maybe USE_CXXSTD=c++14. No, none of these helped. Yuri _

Some reproducible builds notes

2016-06-16 Thread Ed Maste
I recently presented on "Reproducible Builds in FreeBSD" at BSDCan. For anyone unfamiliar with the topic, from https://reproducible-builds.org/ "Reproducible builds are a set of software development practices which create a verifiable path from human readable source code to the binary code used by

Re: USES=compiler:c++14-lang still adds -std=c++11 to CXXFLAGS

2016-06-16 Thread Mathieu Arnold
+--On 16 juin 2016 14:10:41 +0200 Mathieu Arnold wrote: | | | +--On 15 juin 2016 11:26:57 -0700 Yuri wrote: || I have a port that needs c++14. USES statements are like this: || || USES=compiler:c++14-lang gmake qmake || USE_QT5= core gui network || || Yet, compiler command lines sti

Re: USES=compiler:c++14-lang still adds -std=c++11 to CXXFLAGS

2016-06-16 Thread Mathieu Arnold
+--On 15 juin 2016 11:26:57 -0700 Yuri wrote: | I have a port that needs c++14. USES statements are like this: | | USES=compiler:c++14-lang gmake qmake | USE_QT5= core gui network | | Yet, compiler command lines still have -std=c++11, and build fails | because of the lack of c++14 supp

Re: pkg(8) conflicts when install gnome3 - what are they?

2016-06-16 Thread Ben Woods
On Thu, Jun 16, 2016 at 01:58:31AM -0700, Don Lewis wrote: > >> On Wed, Jun 15, 2016 at 2:45 PM, Ben Woods wrote: > >> > >> > How can I determine what the conflicts are? Is there a way to tell pkg to > >> > be verbose and explain the conflict? > > It definitely would be nice if pkg was more help

FreeBSD ports you maintain which are out of date

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

Re: pkg(8) conflicts when install gnome3 - what are they?

2016-06-16 Thread Don Lewis
On 16 Jun, Ben Woods wrote: > On Wed, Jun 15, 2016 at 02:53:25PM -0700, Freddie Cash wrote: >> On Wed, Jun 15, 2016 at 2:45 PM, Ben Woods wrote: >> >> > Hi everyone, >> > >> > I have build gnome3 with my local poudriere instance, but when I try to >> > install it pkg complains of conflicts. >> >

Re: pkg(8) conflicts when install gnome3 - what are they?

2016-06-16 Thread Ben Woods
On Wed, Jun 15, 2016 at 02:53:25PM -0700, Freddie Cash wrote: > On Wed, Jun 15, 2016 at 2:45 PM, Ben Woods wrote: > > > Hi everyone, > > > > I have build gnome3 with my local poudriere instance, but when I try to > > install it pkg complains of conflicts. > > > > # pkg install gnome3 > >