Re: Committer needed for PR 208029

2016-04-05 Thread Michelle Sullivan
Kurt Jaeger wrote: Hi! Actually, I just noticed (when compiling the port), that the Makefile now says: WITH_OPENSSL_PORT=yes Yes, sorry, my fault. Fixed, and as suggested by mat: It is now as IGNORE with a message explaining how to do it for 9.x. Not sure about the IGNORE vs BROKEN but looks

Re: Committer needed for PR 208029

2016-04-05 Thread Kurt Jaeger
Hi! > Actually, I just noticed (when compiling the port), that the Makefile now > says: > > WITH_OPENSSL_PORT=yes Yes, sorry, my fault. Fixed, and as suggested by mat: It is now as IGNORE with a message explaining how to do it for 9.x. -- p...@opsec.eu+49 171 3101372

[Bug 198293] dns/bind99: bind UDP dnssec failing

2016-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198293 Jason Unovitch changed: What|Removed |Added CC||junovi...@freebsd.org,

Re: gentoo's package.provided equivalent?

2016-04-05 Thread Anatoly
В Mon, 4 Apr 2016 09:01:44 +0100 Matthew Seaman wrote: > I could be wrong though -- the only example I know of creating ad-hoc > packages outside the ports, is by Dag-Erling: > > https://blog.des.no/2013/08/creating-pkgng-packages-without-ports/ > https://blog.des.no/2013/08/pkgng-without-ports-

Re: Committer needed for PR 208029

2016-04-05 Thread Michelle Sullivan
Martin Waschbüsch wrote: Umm probably a really bad idea... consider this or something more creative/descriptive: .if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 && ${WITH_OPENSSL_PORT} != "yes" BROKEN= You must set WITH_OPENSSL_PORT=yes in /etc/make.conf on Pre 10.x .endif ... the

Re: Committer needed for PR 208029

2016-04-05 Thread Martin Waschbüsch
> Umm probably a really bad idea... consider this or something more > creative/descriptive: > > .if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 && ${WITH_OPENSSL_PORT} != > "yes" > BROKEN= You must set WITH_OPENSSL_PORT=yes in /etc/make.conf on > Pre 10.x > .endif > > > ...

Re: Committer needed for PR 208029

2016-04-05 Thread Michelle Sullivan
Kurt Jaeger wrote: Hi! I'm testbuilding those ports right now and find that they fail on 9.3amd64 with: With this in the -server Makefile, all is fine. .if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 WITH_OPENSSL_PORT=yes .endif Umm probably a really bad idea... consider this or something

Re: Committer needed for PR 208029

2016-04-05 Thread Michelle Sullivan
Kurt Jaeger wrote: Hi! Could someone please have a look at this one. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029 All patches got approval from the maintainer. For all I can see this should be ready to be committed. If I overlooked anything or more information is needed, please le

Re: Committer needed for PR 208029

2016-04-05 Thread Martin Waschbüsch
> Am 05.04.2016 um 22:15 schrieb Kurt Jaeger : > > Hi! > >> Could someone please have a look at this one. >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029 >> >> All patches got approval from the maintainer. >> For all I can see this should be ready to be committed. > > Done. Thanks

Re: Committer needed for PR 208029

2016-04-05 Thread Kurt Jaeger
Hi! > Could someone please have a look at this one. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029 > > All patches got approval from the maintainer. > For all I can see this should be ready to be committed. Done. -- p...@opsec.eu+49 171 3101372 4

Re: Committer needed for PR 208029

2016-04-05 Thread Kurt Jaeger
Hi! > I'm testbuilding those ports right now and find that > they fail on 9.3amd64 with: With this in the -server Makefile, all is fine. .if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 WITH_OPENSSL_PORT=yes .endif -- p...@opsec.eu+49 171 3101372 4 years to

Re: Committer needed for PR 208029

2016-04-05 Thread Kurt Jaeger
Hi! > I'm testbuilding those ports right now and find that > they fail on 9.3amd64 with: > > checking for OpenSSL support... yes > configure: error: OpenSSL library version requirement not met (>= 1.0.1) > > So it seems that OpenSSL and 9.3amd64 do not build ? Should the > default for 9.3 probab

Re: Committer needed for PR 208029

2016-04-05 Thread Kurt Jaeger
Hi! > Could someone please have a look at this one. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029 > > All patches got approval from the maintainer. > For all I can see this should be ready to be committed. > > If I overlooked anything or more information is needed, > please let me k

Committer needed for PR 208029

2016-04-05 Thread Martin Waschbüsch
Hi all, Could someone please have a look at this one. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029 All patches got approval from the maintainer. For all I can see this should be ready to be committed. If I overlooked anything or more information is needed, please let me know and I'll

Re: pipelight and playonbsd

2016-04-05 Thread Stefan Esser
Am 04.04.2016 um 20:46 schrieb Grzegorz Junka: > Port playonbsd depends on i386-wine-devel and pipelight depends on > i386-wine-staging. So when I want to install pipelight pkg asks me to > uninstall playonbsd. Does it mean playonbsd is incompatible with > pipelight? Are two versions of wine really

pipelight and playonbsd

2016-04-05 Thread Grzegorz Junka
Port playonbsd depends on i386-wine-devel and pipelight depends on i386-wine-staging. So when I want to install pipelight pkg asks me to uninstall playonbsd. Does it mean playonbsd is incompatible with pipelight? Are two versions of wine really necessary? Wouldn't it be better if ports were dep

FreeBSD ports you maintain which are out of date

2016-04-05 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