Re: [package - main-i386-default][sysutils/env4801] Failed for env4801-0.3_1 in build

2021-01-12 Thread Patrick M. Hausen
Am 12.01.2021 um 15:36 schrieb Baptiste Daroussin :
> Note that I have fixed it in r561337 (with some cleanup)

Merci.

Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP


Re: Fwd: [package - main-i386-default][sysutils/env4801] Failed for env4801-0.3_1 in build

2021-01-12 Thread Baptiste Daroussin
On Tue, Jan 12, 2021 at 03:20:36PM +0100, Patrick M. Hausen wrote:
> Dear ports gurus,
> 
> what am I doing wrong that makes me still receive this message every couple 
> of days?
> 
> > Von: pkg-fall...@freebsd.org
> > Betreff: [package - main-i386-default][sysutils/env4801] Failed for 
> > env4801-0.3_1 in build
> > Datum: 12. Januar 2021 um 15:05:07 MEZ
> > An: p...@hausen.com
> > Kopie: pkg-fall...@freebsd.org
> > 
> > ===
> > ===>  Building for env4801-0.3_1
> > make[1]: "/usr/share/mk/bsd.opts.mk" line 110: "NO_MAN is defined, but 
> > deprecated. Please use MK_MAN=no instead."
> 
> The issue should be fixed since mid November:
> 
> https://svnweb.freebsd.org/ports/head/sysutils/env4801/Makefile?r1=418715=554829

What the error is saying is that the Makefile defines:
NO_MAN=sorry, which was something valid long ago, but not anymore (and its been
a while it is not valid anymore) in FreeBSD framework makefile.

Where it is misleading is that the framework (source one not ports) tells you to
use MK_MAN instead because it thinks you are trying to define a build option
which you are not

The right way to fix it is:
MAN=
instead of
NO_MAN= sorry

in the distfile makefile

Note that I have fixed it in r561337 (with some cleanup)

Best regards,
Bapt


signature.asc
Description: PGP signature


Re: [package - main-i386-default][sysutils/env4801] Failed for env4801-0.3_1 in build

2021-01-12 Thread Patrick M. Hausen
Hi!

> Am 12.01.2021 um 15:23 schrieb Kyle Evans :
> This failure in particular stems from line 5 of the Makefile inside the dist:
> 
> NO_MAN= sorry

Thanks! I completely missed that I was pulling a Makefile from phk.

> The MK_MAN in the port makefile should probably go away entirely, and
> this NO_MAN= sorry should be replaced with MK_MAN=no

I'd rather drop the dist Makefile completely and just compile the single static
binary from the port Makefile.

What do you think?
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP


Re: [package - main-i386-default][sysutils/env4801] Failed for env4801-0.3_1 in build

2021-01-12 Thread Kyle Evans
On Tue, Jan 12, 2021 at 8:20 AM Patrick M. Hausen  wrote:
>
> Dear ports gurus,
>
> what am I doing wrong that makes me still receive this message every couple 
> of days?
>
> > Von: pkg-fall...@freebsd.org
> > Betreff: [package - main-i386-default][sysutils/env4801] Failed for 
> > env4801-0.3_1 in build
> > Datum: 12. Januar 2021 um 15:05:07 MEZ
> > An: p...@hausen.com
> > Kopie: pkg-fall...@freebsd.org
> >
> > ===
> > ===>  Building for env4801-0.3_1
> > make[1]: "/usr/share/mk/bsd.opts.mk" line 110: "NO_MAN is defined, but 
> > deprecated. Please use MK_MAN=no instead."
>
> The issue should be fixed since mid November:
>
> https://svnweb.freebsd.org/ports/head/sysutils/env4801/Makefile?r1=418715=554829
>

This failure in particular stems from line 5 of the Makefile inside the dist:

NO_MAN= sorry

The MK_MAN in the port makefile should probably go away entirely, and
this NO_MAN= sorry should be replaced with MK_MAN=no
___
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"


Fwd: [package - main-i386-default][sysutils/env4801] Failed for env4801-0.3_1 in build

2021-01-12 Thread Patrick M. Hausen
Dear ports gurus,

what am I doing wrong that makes me still receive this message every couple of 
days?

> Von: pkg-fall...@freebsd.org
> Betreff: [package - main-i386-default][sysutils/env4801] Failed for 
> env4801-0.3_1 in build
> Datum: 12. Januar 2021 um 15:05:07 MEZ
> An: p...@hausen.com
> Kopie: pkg-fall...@freebsd.org
> 
> ===
> ===>  Building for env4801-0.3_1
> make[1]: "/usr/share/mk/bsd.opts.mk" line 110: "NO_MAN is defined, but 
> deprecated. Please use MK_MAN=no instead."

The issue should be fixed since mid November:

https://svnweb.freebsd.org/ports/head/sysutils/env4801/Makefile?r1=418715=554829

Thanks and kind regards,
Patrick
--
punkt.de GmbH
Patrick M. Hausen
.infrastructure

Kaiserallee 13a
76133 Karlsruhe

Tel. +49 721 9109500

https://infrastructure.punkt.de
i...@punkt.de

AG Mannheim 108285
Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein



signature.asc
Description: Message signed with OpenPGP


Re: mail/milter-greylist aborts

2021-01-12 Thread DutchDaemon - FreeBSD Forums Administrator

On 12/01/2021 11:42, DutchDaemon - FreeBSD Forums Administrator wrote:

On 11/01/2021 22:39, Greg Rivers via freebsd-ports wrote:
since the update from 4.6.2 to 4.6.3 today. It starts, but as soon as 
the MTA writes to the listening socket, it aborts, e.g.:


pid 54733 (milter-greylist), jid 0, uid 26: exited on signal 6

resulting in:
sm-mta[54648]: 10BKxX7b054648: Milter (greylist): error connecting to 
filter: Connection refused by /var/milter-greylist/milter-greylist.sock

sm-mta[54648]: 10BKxX7b054648: Milter (greylist): to error state
sm-mta[54648]: 10BKxX7b054648: Milter: initialization failed, temp 
failing commands


Is anyone else seeing this?


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252516 - patch 
available




A quick fix is to rebuild the port with GeoIP2 toggled to off.



OpenPGP_signature
Description: OpenPGP digital signature


Re: mail/milter-greylist aborts

2021-01-12 Thread DutchDaemon - FreeBSD Forums Administrator

On 11/01/2021 22:39, Greg Rivers via freebsd-ports wrote:

since the update from 4.6.2 to 4.6.3 today. It starts, but as soon as the MTA 
writes to the listening socket, it aborts, e.g.:

pid 54733 (milter-greylist), jid 0, uid 26: exited on signal 6

resulting in:
sm-mta[54648]: 10BKxX7b054648: Milter (greylist): error connecting to filter: 
Connection refused by /var/milter-greylist/milter-greylist.sock
sm-mta[54648]: 10BKxX7b054648: Milter (greylist): to error state
sm-mta[54648]: 10BKxX7b054648: Milter: initialization failed, temp failing 
commands

Is anyone else seeing this?


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252516 - patch available



OpenPGP_signature
Description: OpenPGP digital signature


Occasional saslauthd LDAP failure

2021-01-12 Thread Andrea Venturoli

Hello.

I've got several services authenticating against a Samba AD DC via 
"saslauthd -a ldap"

This works perfectly from the users' point of view.

However I often find failures in the logs:

saslauthd[89676]: ldap_simple_bind() failed -1 (Can't contact LDAP server).
saslauthd[89676]: Retrying authentication


This happens hundreds of times a day.
Almost surely retrying succeeds, as no user ever complained.

I tried getting some logs from Samba, but was not able to.
I ran saslauthd in debug mode and, when the above happens, this is what 
I see:

TLS certificate verification: Error, unable to get local issuer certificate
TLS certificate verification: Error, unable to verify the first certificate


Any hint?
Why would either saslauthd or the openldap client library fail occasionally?



Since I'm using a stateful firewall, I though perhaps connections time 
out, but disabling it did not help.




My saslauthd.conf:

ldap_servers: ldap://x.x.x.x/
ldap_bind_dn: cn=xxx,cn=Users,dc=xxx,dc=xxx,dc=xxx
ldap_password: 
ldap_start_tls: yes
ldap_search_base: cn=Users,dc=xxx,dc=xxx,dc=xxx
ldap_tls_cert: /.../cert.pem
ldap_tls_key: /.../key.pem
ldap_filter: (sAMAccountName=%u)
ldap_scope: sub
ldap_debug: 100
ldap_verbose: on
ldap_tls_check_peer: no



My ldap.conf:

TLS_CACERT /.../cert.pem
TLS_CERT /.../key.pem
TLS_REQCERT allow
ssl_check_cert off


 bye & Thanks
av.
___
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

2021-01-12 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
+-+
science/afni| 21.0.00 | afni_21.0.02
+-+


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

Reported by:portscout!
___
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"