Re: make makepatch

On 27.10.2016 07:50, Franco Fichtner wrote: > Hi Jochen, > >> On 27 Oct 2016, at 7:47 AM, Jochen Neumeister wrote: >> >> what am i doing wrong? > Doesn't makepatch already place the new patches in files/? > No, make makepatch delete the patches into /files and: # make

Re: make makepatch

Hi Jochen, > On 27 Oct 2016, at 7:47 AM, Jochen Neumeister wrote: > > what am i doing wrong? Doesn't makepatch already place the new patches in files/? Cheers, Franco ___ freebsd-ports@freebsd.org mailing list

make makepatch

I will update the net/wpa_gui. # portlint WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. 0 fatal errors and 1

Re: Portmaster still be dissin' jive,bros

On Wed, Oct 26, 2016 at 1:48 PM, Matthias Andree wrote: > Am 24.10.2016 um 21:42 schrieb Louis Epstein: > > The technical issue persists that I can not update via portmaster because > > I installed misc/jive out of sheer curiosity over its unprecedented MOVED > > message.

Problem with gcc5 std library when building ports

Have spent a couple of days trying to build around 800 ports with gcc5. This one has me stumped! Can anyone help regarding the apparant absence of snprintf from std? Am I missing something, perhaps LDCONFIG or? I've looked in /usr/ports/Mk/ bsd.gcc.mk and /usr/ports/Mk/bsd.port.mk but this is

Re: Jive prejudices

Am 23.10.2016 um 18:49 schrieb Louis Epstein: > > On Sun, 23 Oct 2016, Alphons van Werven wrote: > >> Louis Epstein wrote: >> >>> In any event,portmaster -a -i updates now abort because misc/jive is >>> detected on my system. >>> >>> This goes beyond "We will no longer provide this application" to

Re: Portmaster still be dissin' jive,bros

Am 24.10.2016 um 21:42 schrieb Louis Epstein: > The technical issue persists that I can not update via portmaster because > I installed misc/jive out of sheer curiosity over its unprecedented MOVED > message. workarounds wirth trying - but untested (alternative): 1. pkg delete -fy jive 2. run

RE: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

> -Original Message- > From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd- > po...@freebsd.org] On Behalf Of Mark Linimon > Sent: 26 October 2016 21:27 > To: Joe Holden > Cc: 'Christian Weisgerber' ; freebsd- > po...@freebsd.org > Subject:

Re: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

On Wed, Oct 26, 2016 at 09:12:33PM +0100, Joe Holden wrote: > Yes, it is a ridiculous situation but since there appears to be zero > coordination between ports committers, probably expected. Thank you for making sure my motivation to work on fixing things stays at a nice, zero, level. You *do*

RE: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

> -Original Message- > From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd- > po...@freebsd.org] On Behalf Of Christian Weisgerber > Sent: 09 August 2016 15:18 > To: freebsd-ports@freebsd.org > Subject: Re: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?! > > On 2016-08-02, "Joe

Re: lighttpd does not pull OpenSSL dependency

2016-10-26 10:46 GMT+02:00 Mathieu Arnold : > Le 26/10/2016 à 00:14, Don Lewis a écrit : >> Then the question is, if DEFAULT_VERSIONS+=ssl=openssl is not in >> make.conf, then why is OpeSSL from ports installed? Nothing should >> be depending on it. > > Well, the problem is that

pkg query %q: abi vs. arch

pkg query doesn't work as expected: #pkg query -e '%q = freebsd:10:x86:64' '%o: %q' # pkg query -e '%q = FreeBSD:10:amd64' '%o: %q' dns/adns: freebsd:10:x86:64 ... It seems '%q' means abi for evaluations, but arch for queries. # pkg info -R adns ... abi = "FreeBSD:10:amd64"; arch =

WIP: lang/php71

Aloha, PHP 7.1 RC5 was released and it will hopefully not too far until the full release. Therefore i started some work on the new port. Sadly i haven't had much time in the last, so its not too much. Currently i just added lang/php71, pet portlint a little and test a little of the basics.

Re: Inconsistency? (was Re: misc/jive deleted)

On 10/26/2016 09:32 AM, Kurt Jaeger wrote: Hi! I think unless FreeBSD makes explicit antichrist statement, there is no problem having a daemon mascot. I have never heard any religious problem so far. Or then I missed something. Approx. 20 years ago (?), some FreeBSD developer with a old-style

FreeBSD ports you maintain which are out of date

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,

Re: lighttpd does not pull OpenSSL dependency

Le 26/10/2016 à 00:14, Don Lewis a écrit : > Then the question is, if DEFAULT_VERSIONS+=ssl=openssl is not in > make.conf, then why is OpeSSL from ports installed? Nothing should > be depending on it. Well, the problem is that many ports have WITH_OPENSSL_PORT defined, so, something could have

Re: Inconsistency? (was Re: misc/jive deleted)

On Wed, 26 Oct 2016 09:32:55 +0200 Kurt Jaeger wrote: > Hi! > > > I think unless FreeBSD makes explicit antichrist statement, there is > > no problem having a daemon mascot. I have never heard any religious > > problem so far. Or then I missed something. > > Approx. 20 years

Re: Inconsistency? (was Re: misc/jive deleted)

Hi! > I think unless FreeBSD makes explicit antichrist statement, there is > no problem having a daemon mascot. I have never heard any religious > problem so far. Or then I missed something. Approx. 20 years ago (?), some FreeBSD developer with a old-style logo on a t-shirt was asked to leave

Re: Inconsistency? (was Re: misc/jive deleted)

2016-10-25 22:57 GMT+02:00 Dave Horsfall : > Have you seen the FreeBSD home page? Well, I thought the OP was talking about the logo [0], not the home web page. Anyway, I think comparing religious and offensive content a bit offtopic. I think unless FreeBSD makes explicit