Re: make makepatch

[Jochen Neumeister]

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 makepatch
The previous patches have been placed here:
/usr/home/joneum/dev/ports/net/wpa_gui/work/.makepatch-tmp/archived-patches

Cheers
Jochen
___
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: make makepatch

[Franco Fichtner]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

make makepatch

[Jochen Neumeister]

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 warning found.

okay, i use "make makepatch", and copy the files from
"work/.makepatch-tmp/archived-patches" to the "/files" folder, and start
portlint. But, the same.

what am i doing wrong?


Cheers

Jochen

___
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: Portmaster still be dissin' jive,bros

[Kevin Oberman]

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.
> workarounds wirth trying - but untested (alternative):
>
> 1. pkg delete -fy jive
>
> 2. run portmaster with an explicit set of ports, for instance in bash
> (other shells may not grok the POSIX $(...) )
> portmaster -d $(pkg version -Ivl\<| cut -f1 -d\< | xargs pkg info -qo)
> or: bash -c 'portmaster -d $(pkg version -Ivl\<| cut -f1 -d\< | xargs
> pkg info -qo)'
>

I have tested this and it works. First, don;t delete anything you want to
keep.  It.s not relevant.
# make -C /usr/ports fetchindex (or get it in any ot the several other ways
including building from scratch (slow).)
# pkg version -vL=
I do these steps in periodic every night.
I also do 'svn up /usr/ports' in the periodic script, but you can also just
update the out-of-date ports with 'svn up /usr/ports/class/port' for the
ports listed as needing updating,
Then run portmaster with the list of ports from the pkg above marked with
'<' as needing update. Also note any marked '?' and take appropriate action.

I quit doing 'portmaster -a' because it took so long to scan through all
ports, but it also solves you problem. (portmaster may now be using the
index and -a may not take so long.)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"

Problem with gcc5 std library when building ports

[Dewayne Geraghty]

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 an area that I'm
unfamiliar, so nothing really stood out.

If I change the compiler from gcc5 to clang everything compiles and runs
correctly. I have in /etc/make.conf
USE_GCC=  5
and to use clang, I just comment out the above. So everything is constant,
on FreeBSD 10.3Stable (updated and rebuilt overnight)

For example: /usr/ports/devel/jsoncpp (but many share this problem)
g++5 -o buildscons/linux-gcc-FreeBSD/src/lib_json/json_reader.o -c -O2
-pipe -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3 -g0 -ggdb0 -DSTRIP_FBSDID
-UDEBUGGING -UDEBUG -march=c3-2 -mtune=c3-2 -Wl,-rpath=/usr/local/lib/gcc5
-fno-strict-aliasing --std=c++11 -Wl,-rpath=/usr/local/lib/gcc5 -Iinclude
src/lib_json/json_reader.cpp

src/lib_json/json_reader.cpp: In member function 'std::__cxx11::string
Json::Reader::getLocationLineAndColumn(Json::Reader::Location) const':
src/lib_json/json_reader.cpp:34:18: error: 'snprintf' is not a member of
'std'
 #define snprintf std::snprintf

And for completeness:
# ldconfig -r | grep -E "gcc|\+"
search directories:
/lib:/usr/lib:/usr/lib/compat:/usr/local/lib:/usr/local/lib/gcc5:/usr/local/lib/heimdal:/usr/local/lib/perl5/5.20/mach/CORE
35:-lgcc_s.1 => /lib/libgcc_s.so.1
38:-lc++.1 => /usr/lib/libc++.so.1
126:-lcc1.0 => /usr/local/lib/gcc5/libcc1.so.0
127:-lgcc_s.1 => /usr/local/lib/gcc5/libgcc_s.so.1
128:-lstdc++.6 => /usr/local/lib/gcc5/libstdc++.so.6
129:-lcilkrts.5 => /usr/local/lib/gcc5/libcilkrts.so.5
130:-lssp.0 => /usr/local/lib/gcc5/libssp.so.0
131:-lquadmath.0 => /usr/local/lib/gcc5/libquadmath.so.0
132:-lgfortran.3 => /usr/local/lib/gcc5/libgfortran.so.3
133:-lobjc.4 => /usr/local/lib/gcc5/libobjc.so.4
134:-lgomp.1 => /usr/local/lib/gcc5/libgomp.so.1
135:-lgomp-plugin-host_nonshm.1 =>
/usr/local/lib/gcc5/libgomp-plugin-host_nonshm.so.1
136:-litm.1 => /usr/local/lib/gcc5/libitm.so.1
137:-latomic.1 => /usr/local/lib/gcc5/libatomic.so.1

Regards, Dewayne
___
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: Jive prejudices

[Matthias Andree]

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
>>> "we will no longer let you upgrade your applications as long as you
>>> have this one installed".
>> To be fair, I strongly doubt this is deliberate policy.
>>
>> Portmaster itself is a port too. When pkg(7) hit the streets and other
>> sweeping changes were made to the ports infrastructure, Portmaster had to
>> be updated and that might still be an ongoing process. In any case, Port-
>> master needs *some* way of dealing with broken(*) ports and I can imagine
>> that this can get tricky when dependencies are involved. From the looks of
>> it, Portmaster just takes the easy way out and simply bails completely
>> when it encounters a broken port.
> Does it matter that I installed it with pkg rather than portmaster or make
> install?
Irrelevant. No matter how a port got installed, they all end up being
registered with and managed by pkg(7).

___
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: Portmaster still be dissin' jive,bros

[Matthias Andree]

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 portmaster with an explicit set of ports, for instance in bash
(other shells may not grok the POSIX $(...) )
portmaster -d $(pkg version -Ivl\<| cut -f1 -d\< | xargs pkg info -qo)
or: bash -c 'portmaster -d $(pkg version -Ivl\<| cut -f1 -d\< | xargs
pkg info -qo)'
___
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: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

[Joe Holden]

> -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.
>
Sorry, bad phrasing and much generalisation - most people are sensible.

> You *do* know it is harder to fix things and coordinate with people
> rather than just bitch, correct?
>
Quite,  unfortunately easier said than done when any spare time that could
be used to try and fix stuff is spent patching up existing things to make
them work.

> mcl
> ___
> 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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

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

[Mark Linimon]

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* know it is harder to fix things and coordinate with people
rather than just bitch, correct?

mcl
___
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: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

[Joe Holden]

> -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 Holden"  wrote:
>
> > That is not a fix since it breaks at least nginx in the official repo,
> > because nginx depends on openssl and openntpd depends on libre.
> >
> > Either the entire tree should move to a library supported by everything,
or
> > the openntpd port gets split into meta packages so that we don't need to
> > return to a stage where everyone is building ports.
> >
> > Was this not even considered or tested?
>
> I put the blame on the people who thought it a good idea to have
> FIVE only partially compatible SSL libraries in the tree: OpenSSL
> in base, openssl, openssl-devel, libressl, libressl-devel.
>
Yes, it is a ridiculous situation but since there appears to be zero
coordination between ports committers, probably expected.

> Bernard Spil (brnrd) has worked hard on moving the entire tree to
> LibreSSL, but the political will is missing.
>
> Like other software coming out of OpenBSD, OpenNTPD now requires
> libtls for its https functionality.  That's a new library with a
> new API that doesn't exist in OpenSSL.  The constraints check is a
> standard feature of OpenNTPD.  If you run OpenNTPD, you expect it
> to be available.  I have no intention of disabling this by default
> and it requires libtls.
>
Breaking existing install bases because of an *optional* feature is really a
shitty attitude, it is not OpenBSD, therefore does not need feature parity -
it is a *port* of OpenNNTPD, by your logic I should be able to use rdomains
in software ported from OpenBSD yes?  While we're here, PF is from OpenBSD
so I expect it to be the same as 6.0.

> > (Cc naddy)
>
> Sorry, I somehow didn't get this.
>
> --
> Christian "naddy" Weisgerber  na...@mips.inka.de


___
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: lighttpd does not pull OpenSSL dependency

[David Demelier]

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 many ports have WITH_OPENSSL_PORT defined, so,
> something could have brought it along. I have a git branch changing it
> to WANT_OPENSSL_PORT that will mark the port IGNOREd if using base
> OpenSSL, I should commit it one day.
>
> Also, I'll change the default for ports from base to openssl, one day.

I can help if needed.

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

pkg query %q: abi vs. arch

[Stefan Ehmann]

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 = "freebsd:10:x86:64";
...

According to the man page it should be Architecture in both cases.
___
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"

WIP: lang/php71

[Torsten Zuehlsdorff]

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.


Of course all 60+ extensions are missing, but i centered my affords at 
the core. It should be relatively easy to add them.


If you want to test or participate you can use my ports-tree copy from 
GitLab:


$ git clone https://github.com/t-zuehlsdorff/freebsd-ports
$ git checkout php71

Feel free to add what you want and do a pull request!

Greetings,
Torsten
___
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: Inconsistency? (was Re: misc/jive deleted)

[David Demelier]

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
logo on a t-shirt was asked to leave some saloon in Texas
because the logo suggested that they worship the antichrist.

Brilliant ! :-)

There was a job (in rec.humor.funny?) about it 8-}

That's why this reference to the demon logo is made 8-}



___
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

[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
+-+
emulators/mame  | 0.166   | mame0179
+-+
emulators/mess  | 0.166   | mame0179
+-+
www/drupal7 | 7.50| 7.51
+-+


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: lighttpd does not pull OpenSSL dependency

[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 many ports have WITH_OPENSSL_PORT defined, so,
something could have brought it along. I have a git branch changing it
to WANT_OPENSSL_PORT that will mark the port IGNOREd if using base
OpenSSL, I should commit it one day.

Also, I'll change the default for ports from base to openssl, one day.

-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

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

[Bob Eager]

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 ago (?), some FreeBSD developer with a old-style
> logo on a t-shirt was asked to leave some saloon in Texas
> because the logo suggested that they worship the antichrist.
> 
> There was a job (in rec.humor.funny?) about it 8-}
> 
> That's why this reference to the demon logo is made 8-}
> 

http://www.milk.com/true-stories/unix_for_the_masses.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: Inconsistency? (was Re: misc/jive deleted)

[Kurt Jaeger]

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 some saloon in Texas
because the logo suggested that they worship the antichrist.

There was a job (in rec.humor.funny?) about it 8-}

That's why this reference to the demon logo is made 8-}

-- 
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: Inconsistency? (was Re: misc/jive deleted)

[David Demelier]

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 antichrist statement, there is
no problem having a daemon mascot. I have never heard any religious
problem so far. Or then I missed something.

Regards,

[0]: https://www.freebsd.org/fr/logo.html (why the english version
does not have them?)

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